build-isometric-arpg

Start with one playable loop: title screen, character choice, movement, one encounter, a reward, and progression. Then deliver vertical slices in order—movement and camera, one combat verb, one enemy, one reward, one zone transition—each with tests and a stable save path.

Build movement, camera, collision, and target selection first, then a single combat verb with damage and death, then one enemy with telegraphs, then rewards and progression, then zone transitions. Avoid adding a second system until the previous slice has gameplay proof and automated coverage.

Yes, the workflow targets Three.js, React, or similar web technologies. The principles of deterministic state, data-driven content contracts, and vertical slices apply regardless of the specific rendering framework.

Keep simulation state deterministic and serializable, and make save migration, equipment, and reset flows atomic and idempotent. Provide review fixtures for difficult states like interrupted actions and save migrations, and verify fresh starts plus saved continuation before release.

Duplicating combat clocks across components causes desynchronized damage, cooldown, and posture behavior. Centralizing timing, damage, and content values in one place keeps combat outcomes consistent and makes the simulation easier to test and serialize.