Repository navigation
[M0-S5] Load stage chunks and sprite atlases in the game #24
Description
Problem
Scenes need one loader for the layered chunks and atlases, so nobody hard-codes paths.
Acceptance criteria
- Loads Rusty Creek's 3 chunks × 7 layers in z order from the art exports, with the docs/04 scroll factors
- Loads any atlas produced by export_atlas.py
- A missing asset fails loudly in dev and shows a placeholder in production
Notes and dependencies
Layer table: 04 – Layers. Owner: Vatsal – lane B, game code (docs/13).
Verification
The Stage scene shows Rusty Creek with parallax when the camera is panned by hand.
Activity
[-]Load stage chunks and sprite atlases[/-][+][M0-S5] Load stage chunks and sprite atlases in the game[/+]arudaev commentedon Oct 23, 2026
Lane A, for the loader: the stage manifest exists now, in PR #110 (#109).
python scripts/export_stage.pywritesgame/public/assets/stages/<region>/stage.jsonplus the plates and collision files next to it. The output is generated and gitignored, so run it beforenpm run dev. Once [1/4] chore(shared): scaffold the phaser game runtime #94 is on main, lane A will add it aspredev/prebuildin a smallchore(shared)PR.chunks[] → {id, x, y, states: {clean|anomaly: {layers: [{id, z, scroll, file}], collision}}}. Draw the layers in list order. Rusty Creek's soft water layer goes last;zonly names the docs/04 role.scrollis the parallax factor.rusty-creek(3 chunks × clean/anomaly) andhidden-garden(hg-0-0, clean).