The core game loop separates logic and physics updates into discrete, fixed time steps using an accumulator pattern. This guarantees deterministic physics behavior and simulation stability across variable hardware refresh rates, while the graphics pipeline smoothly interpolates transforms between ticks. 

Enemy bots utilize a modular Finite State Machine (Move, Shoot, Stun, Die). The navigation loop continuously evaluates waypoint vectors, checks dynamic line-of-sight and range thresholds against defensive targets (Gates, Nexus, Player), and seamlessly coordinates FMOD movement audio fading before transitioning into active combat.

To script cinematic sequences and win states without hardcoding timelines in C++, I engineered a custom cutscene event sequencer. Leveraging the engine's existing YAML parser, I built a runtime system that reads sequential data to execute timed actions such as camera lerping, screen fades, audio triggers, and UI text displays.

The Solution:

I built a modular Finite State Machine using the State Pattern: a single AIComponent holds one polymorphic AIState* pointer, and behaviors like Move, Shoot, Stun, and Die are self-contained state objects that plug in per enemy type. State transitions are centralized in a single ChangeState() call that calls Exit(), frees the old state memory, and triggers Enter() on the incoming state. This ensures interrupting a grunt mid-chase to stun or destroy it never leaks memory, even under rapid transitions.  

For performance, all AI updates execute through a centralized AIManager that iterates over a contiguous std::vector<AIComponent> every frame rather than performing scattered per-object lookups. This cache-friendly traversal keeps orientation matrix calculations, waypoint tracking, and burst-fire timers running at a stable 60 FPS across active wave spawns.

Gameplay Teaser & Feature Overview