STEP 67 OF 67 · YOU ARE THE PUBLISHER
Release and maintain it
Watch crash reports and feedback, fix by priority, test each patch, keep old saves working, and back up both the released build and the exact project that made it.
How to do it
- Publish to itch.io or Steam.
- Watch crashes and feedback.
- Test patches before publishing; keep saves compatible.
- Back up the release and its project.
How AI speeds this up
Duke pushes builds to itch.io automatically and keeps every build downloadable.
Example from a sample game
Ashfall: launched on itch.io, patch 1.0.1 a week later.
Before you move on
In Duke Forger, this step's gate checks:
- You confirm itThe game is published
- You confirm itReleased build and its project are backed up
Words to know
- Patch
- An update that fixes bugs or adds content after release.
Do step 67 on your own game
Start freeIncluded in Creator, Academy and Studio. Duke drafts it with you and checks it before step 67 opens.