Files
chemo-sim/docs/STEAM_RELEASE_CHECKLIST.md

57 lines
1.7 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Steam Release Checklist
Chemo-Sim — Everything needed before hitting "Publish."
## Pre-Launch (Phase 4)
- [ ] Steamworks account created
- [ ] App ID reserved ($100 fee paid)
- [ ] Bank/tax info filled in Steamworks
- [ ] Build depots configured (Win x64, Linux)
- [ ] GodotSteam plugin integrated and tested
- [ ] Achievements defined and implemented
- [ ] Cloud saves configured (if using)
## Store Page (Phase 45)
- [ ] Short description (≤300 chars)
- [ ] Full description (formatting, GIFs, feature bullets)
- [ ] Content warnings set (mature themes, medical situations, dark humor)
- [ ] Tags: Indie, Simulation, First-Person, Dark Humor, Singleplayer, Story Rich
- [ ] Genre: Simulation, Indie
- [ ] Screenshots (min 5, showing gameplay variety)
- [ ] Trailer (3090 sec, captures tone)
- [ ] Capsule images:
- Header capsule (460x215)
- Small capsule (231x87)
- Main capsule (616x353)
- Vertical capsule (374x448)
- [ ] Library assets:
- Library capsule (600x900)
- Library hero (3840x1240)
- Library logo (1280x720)
## Build Verification (Phase 5)
- [ ] Fresh install from Steam on Windows
- [ ] Fresh install from Steam on Linux
- [ ] Achievements unlock correctly
- [ ] Save/load works across sessions
- [ ] Controller works (if supported)
- [ ] No crash in 1-hour playthrough
- [ ] Steam overlay works (Shift+Tab)
## Launch Day
- [ ] Set release date in Steamworks
- [ ] Flip store page from "Coming Soon" to "Early Access"
- [ ] Post announcement on Discord/Twitter/TikTok
- [ ] Monitor Steam forums and Discord for first-hour bugs
- [ ] Hotfix branch ready, CI warmed up
## Post-Launch
- [ ] First patch within 48 hours (critical fixes only)
- [ ] Weekly community roundup posts
- [ ] Plan first content update based on feedback