Migrates existing GDD and engine design notes from HacknPlan into a new Obsidian vault. This establishes a centralized, version-controlled knowledge base covering engine architecture, game constraints, design decisions, and open questions.
1.4 KiB
1.4 KiB
tags
| tags | ||
|---|---|---|
|
Game Constraints
These answers about the game drive the engine design. If one changes, re-check the notes linked from it.
| Question | Answer | Engine consequence |
|---|---|---|
| How does a round play out in time? | Phased: plan (paused, play cards, place towers), then a real-time wave | Two clocks; the simulation can be paused and sped up. See Main Loop and Time |
| Reproducibility? | Seeded map and deck generation only. Combat does not need to replay bit-exactly | Named RNG streams and our own distributions. Floats are fine in the simulation. See Randomness |
| Placement and pathing | Tile grid with fixed enemy lanes. Towers block nothing | No flow fields or re-pathing. Lane following is a spline or waypoint walk |
| Presentation | Rigid-part 3D | SDL_GPU renderer; the simulation stays 2D on the ground plane. See Rendering, Rigid-Part Animation |
| Content | Data plus scripting | Scripts run on events only. See Scripting |
Consequences in one line each
- The simulation is 2D. Gameplay positions are
glm::vec2on the world X/Z plane. Height (projectile arcs, flyers, muzzle offsets) is visual only. - The planning phase is simply
SimClockspeed = 0. The engine has no concept of "phases"; the game owns that state machine. - Run state (deck, relics, gold, map) is plain C++ data owned by the game, not ECS data.