codebase-systems

What problem does it solve?

Provides a single, actionable reference for the responsibilities, event handling, and extension points of all core game systems so developers can safely add or modify gameplay mechanics without breaking invariants or regressions.

Core Features & Use Cases

• CombatSystem: Melee and ranged attack flows, damage calculation points, death handling, XP and loot triggers; use when adding new weapons or combat rules.
• AiSystem: Behavior registry pattern and built-in behaviors with A* pathfinding; use when adding or tuning enemy behaviors and cover/retreat mechanics.
• MovementSystem: Bump-resolution priorities, tile effect triggers, and pickup logic; use when changing movement rules, interactables, or tile reactions.
• Loot & Quest Systems: Reactive event-driven loot spawning and quest progression handlers; use when introducing new loot tables or quest event hooks.
• StatusEffectSystem & StormSystem: Turn-based status ticking and complex storm-driven map edits and spawns; use when designing per-turn effects, adaptation thresholds, or environmental transformations.
• Integration & Testing: Lists required GameEvent additions, where to register new systems, and recommends writing DES scenarios for deterministic automated tests.

Quick Start

Ask the skill to produce a concrete plan to add or modify a specific system (for example: a ranged-support AI behavior), including file locations, event changes, registry updates, and a DES test scenario.