Gameplay Programming 2D

Build gameplay as explicit, testable simulation rules with engine code at the boundary.

Start from project evidence

1. Read the nearest repository instructions and existing gameplay code.
2. Detect the engine, exact installed version, language, physics backend, target platforms, and test setup.
3. Identify the current ownership of input, simulation, presentation, collision, and persistence.
4. Preserve established conventions unless they cause the reported problem.
5. Define the requested behavior with measurable states, transitions, timing, and failure cases.

Load only relevant references