How jbetala7/warriorz works
Project type and purpose
• This is a Unity‐based 2D platformer game (“Warriorz”) composed of multiple Scenes (StartMenu, Tutorial, Level-1, Level-2), Player and Enemy behaviours, Traps, Pickups, and UI menus.
• It uses Unity’s Monobehaviour/component architecture: all game logic lives in C# scripts under Assets/Scripts, assets in corresponding folders, and the Unity Engine drives Scene loading, rendering, physics, audio, input, etc.
File structure
• Top-level “Assets” folder subdivides into:
• Animations (Animator controllers + .anim files)
• Prefabs (blueprints for Enemies, Player, Traps, UI, Weapons, Power-ups)
• Scenes (Unity .unity files for each level/menu)
• Scripts (grouped by feature: Camera, Enemy, Health, Level, Menus, Player, Sound, Traps)
• Sound & Sprites (raw assets)
• “Packages” and “ProjectSettings” contain engine/dependency configs. There is also a LoadingSystem.cs for Scene transitions.
README for additional insights
• The README confirms the game flow: StartMenu → Tutorial → Level-1 → Level-2 → Win/GameOver.
• Key gameplay features: two Enemy AIs (patrol & shooting), five Trap types, two pickups, three in-game UI menus.
• Tech stack: Unity 2021.1.0f1, standard 2D pipeline, no external servers or microservices.
Detail without overthinking
• Major folders as components (Scripts, Prefabs, Scenes, Audio, Animations).
• Drill down one level: show how Scripts map to subsystems and Prefabs.
• Don’t stray into minor utility scripts; focus on the systems that drive game flow, player/enemy behavior, and UI.