How gdap-2023/prog50016-lab5 works
Project type and purpose
• This is a native C++ game engine (in Engine/) plus a client game project (in GameProject/) that uses the engine. It relies on SDL (under External-Libs/) for windowing, input, audio and rendering.
• The engine provides core systems (rendering, audio, collision, input, scene management, asset management, etc.). The game (“Taco Warrior Reborn III”) implements gameplay logic (entities like Player, Ghoul, Zombie, scenes like GameOver) by calling into engine APIs.
File structure
• Top-level:
• .github, .gitignore, Doxyfile – repository configuration and docs
• Engine/Engine.sln – Visual Studio solution for engine
• External-Libs/SDL – third-party library source + headers + binaries
• GameProject/GameProject.sln – Visual Studio solution for the game
• GameProject/Build/Assets – game asset metadata (JSON) and built assets (.wav.asset)
• Engine/Engine:
• Core engine class (Engine, GameEngine, EngineCore, EngineTime, EngineMath)
• Subsystems: AudioSystem, InputSystem, RenderSystem, CollisionSystem, SceneManager, AssetManager
• Runtime components: Entity, Component, Transform, Renderable, Sprite, AnimatedSprite, BoxCollider/CircleCollider
• Asset classes: Asset, TextureAsset, MusicAsset, SoundAsset, FontAsset
• Utilities: JSON parser, random number generator (mersenne)
• GameProject/GameProject:
• main.cpp – program entry point
• Game_Register.cpp – registers game objects with engine reflection or factory
• GameCore.h – game initialization logic
• Scene classes: GameOver
• Entity implementations: Ghoul, Zombie, Player
README for additional insights
• The README is a marketing blurb. It does not document architecture. All architectural hints come from the file tree.