How tonyjdev/indiespainjam23 works
Project Type and Purpose
• This is a Unity-based 2D game prototype for the “IndieSpainJam23” game jam.
• It uses the Universal Render Pipeline (URP), the new Input System, and various asset packs (animations, audio, tiles, prefabs) under “Assets/Undead Survivor.”
• The core gameplay logic lives in “Assets/Scripts/Game,” e.g. PlayerMovement.cs, and is tied together in “Assets/Scenes/Game.unity.”
File-Structure Analysis
• Top-level folders:
• Assets – all game code, scenes, input actions, graphics, audio, templates.
• Packages – Unity package manifests for dependencies.
• ProjectSettings – engine configuration (Rendering, Physics2D, Audio, Input, URP settings).
• Docs – any plain-text documentation (tasks.md).
• Inside Assets:
• Input – InputAction asset for mapping user controls.
• Scenes – contains Game.unity (the main scene).
• Scripts/Game – MonoBehaviour scripts for Player, future enemies, managers.
• Settings – custom URP Scene templates and pipeline assets.
• Sprites/Undead Survivor – imported sprite sheets, animation controllers, audio clips, demo scene.
• Key engine/config files: Packages/manifest.json, ProjectSettings/URPProjectSettings.asset, InputManager.asset, Physics2DSettings.asset.
README Insights
• README.md only names the jam; no architecture details.
• We infer a single-scene game, using Unity’s core subsystems with custom game logic layered on top.
a. Main Components
‑ Core Loop (Update, FixedUpdate)
‑ Rendering Subsystem (URP)
‑ Physics2D Engine
‑ AudioManager
‑ Input System
2. Game-Specific Layer:
‑ Scene Manager (loads/unloads Game.unity, Demo.unity)
‑ Game Controllers (PlayerMovement, enemy controllers)
‑ UI Layer (if any HUD, menus)
3. Asset Pipeline:
‑ Sprites & Animations (Animator Controllers, .anim files)
‑ Audio Clips (WAVs for BGM, effects)
‑ Tile Assets / Prefabs (Tiles/RanTile.asset, Pal.prefab)
4. Configuration & Build:
‑ Packages (manifest.json)
‑ ProjectSettings (URP settings, Input mappings, Quality settings)
b. Relationships and Interactions
• User Input flows into the Input System → triggers PlayerMovement script → updates Transform & Rigidbody2D → Physics engine resolves collisions.
• PlayerMovement changes Animator state → URP renders sprites & animations.
• Game scripts call AudioManager to play SFX/BGM.
• Scene Manager initializes game objects & UI on scene load.
• Asset Pipeline feeds sprites/audio into engine at runtime.
• ProjectSettings and Packages define engine behavior & build dependencies.
c. Architectural Patterns / Principles
• Layered architecture:
• Engine core at bottom
• Shared subsystems (Rendering, Physics, Audio, Input)
• Game logic scripts on top
• Separation of concerns:
• Input assets separate from code
• Rendering templates (URP) separate from game logic
• Assets (animations, audio) decoupled from scripts
• Data-driven assets: use ScriptableObjects / .asset files for templates.
d. Key Technologies / Frameworks
• Unity 2021+ with Universal Render Pipeline
• Unity Input System (.inputactions)
• 2D Physics (Rigidbody2D, Collider2D)
• Animator Controllers & Override Controllers
• Scriptable pipeline assets (Lit2DSceneTemplate, URP2DSceneTemplate)
Final Advice
• Do not over-break: group all ProjectSettings under one “Configuration” node.
• Keep it simple, but include each major folder or system.