Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Take a game from concept to SHIPPED — the discipline most aspiring devs skip. Deliver a complete, polished small game with: a tight core gameplay loop designed for fun (state your mechanics and intended player experience, MDA-style); solid game feel/juice; a real menu/HUD with controller support and at least basic accessibility (remappable controls or scalable text); performance that holds the frame budget on the target platform (profile and show it); and an actual BUILD/RELEASE — exported and published to an accessible platform (e.g. itch.io for web/WebGL, or a store page) with screenshots and a short devlog. Optionally include simple networked multiplayer with client-side prediction. The deliverable is a link to a finished, playable game.
A complete, polished game actually exported and published (e.g. itch.io) and playable via a link; scope kept achievable and DONE.
A coherent core loop with stated mechanics/intended experience; strong juice/polish; playtested for fun.
Holds the frame budget on target hardware (profiled); menu/HUD with controller support + basic accessibility.
Release page with screenshots/devlog; clean build; optional multiplayer uses prediction/authoritative server correctly.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A polished, shipped game (jam-style, finished) ## Goal Take a game from concept to SHIPPED — the discipline most aspiring devs skip. Deliver a complete, polished small game with: a tight core gameplay loop designed for fun (state your mechanics and intended player experience, MDA-style); solid game feel/juice; a real menu/HUD with controller support and at least basic accessibility (remappable controls or scalable text); performance that holds the frame budget on the target platform (profile and show it); and an actual BUILD/RELEASE — exported and published to an accessible platform (e.g. itch.io for web/WebGL, or a store page) with screenshots and a short devlog. Optionally include simple networked multiplayer with client-side prediction. The deliverable is a link to a finished, playable game. ## Acceptance criteria - [ ] Finished & shipped: A complete, polished game actually exported and published (e.g. itch.io) and playable via a link; scope kept achievable and DONE. - [ ] Design & feel: A coherent core loop with stated mechanics/intended experience; strong juice/polish; playtested for fun. - [ ] Performance & UX: Holds the frame budget on target hardware (profiled); menu/HUD with controller support + basic accessibility. - [ ] Craft: Release page with screenshots/devlog; clean build; optional multiplayer uses prediction/authoritative server correctly. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.