ODM is built in-house — it is now the schedule's biggest risk, so it starts in Month 5 and gets three protections. One: every phase is prototyped in an empty test place, never the district. Two: each phase is timeboxed to ~2 weeks — if a phase overruns twice, the polished single-hook grapple from Phase 1 becomes launch ODM and the full system ships post-launch as live content. Three: the 100–150€ freed from the old commission plan goes to art commissions instead — titan models & animations and combat/ODM animations are exactly where bought art buys the most quality, and they fit your art-and-UI-only commissioning rule.
Titans follow ODM. ODM at launch without anything to fight makes no sense, so basic titan AI is now in Month 7. Keep them outside the walls only; a breach is a staff-run story event, never an automatic system.
The bandit AI is secretly your titan AI. Build its state machine (patrol → aggro → attack) cleanly in Month 5; Month 7 mostly re-skins and re-scales it.
Feature freeze is Month 9, week 1. After Alpha 1, only bugs get fixed. Every "one more feature" idea goes into your v2 list.
Never be the only person who can run the game. Staff trained on the event suite by Month 8 or the launch date slips — treat that as a real milestone, not a hope.
Data trust is everything in permadeath RP. One wiped character from a bug and your community's trust dies with it. Session-locking, save tests, and a staff restore command are not optional tasks.
Months 2 and 6 are the motivation cliffs (invisible framework work; ODM integration frustration). The Discord RP events exist to carry you through them.
IP caution: custom name and continuity everywhere public, no monetisation, systems generic enough to reskin.