Repository navigation
[M0] The game runs on a preview URL and art flows into it #21
Description
Outcome
Anyone on the team clones the repo, runs npm run dev in game/ and sees the 1280×720 pixel-art canvas; every PR gets a Vercel preview; a sprite board becomes a Phaser atlas with one command; and the issue board, forms and PR checks work the same way as in THD Room Finder and Voyager.
Scope
| In this milestone | Not in this milestone |
|---|---|
Phaser 3 + TypeScript + Vite scaffold in game/ |
Gameplay (M1+) |
| Vercel previews and the production URL | Sprite sheets themselves (each milestone owns its sheets) |
| CI: build, docs, art checks | Regions 2–5 |
export_atlas.py and loading chunks + atlases |
|
| Layer split for any region (Hidden Garden needs it) | |
| Team workflow, issue forms, board automation | |
| Organiser rules (AI art, submission) |
Sequence
S1 scaffold → S2 Vercel and S3 CI in parallel. S4 export_atlas can start now and feeds S5 loading. S6 layer split starts now (M3 needs it). S9 → S10 → S11 are one stacked PR series. S12 is a question to ask in person, today.
Completion criteria
-
git clone→cd game && npm install && npm run devshows the canvas on a laptop that has never run it - A PR shows a working Vercel preview link
- The hero sheet exports to an atlas the game loads
- All sub-issues closed.
References
Proposal · Game design · World and levels · Asset manifest · Jam plan · Decisions · Tech stack · Team workflow
Activity
[-]Epic: Game scaffold and deploy[/-][+][M0] The game runs on a preview URL and art flows into it[/+]