Purpose:
To ensure that the rules for a game in development are always current, clear, and testable—so that internal teams, play-testers, and future editors can rely on them to accurately reflect the game’s state.
What this means:
Developers are responsible for maintaining a written, up-to-date version of the rules throughout development. This living document is critical for enabling self-guided play-tests, improving feedback quality, and making the final rules writing process far easier when the game is ready for publication. The document needs to be functional, but not necessarily written in the way that final rules might.
RACI Roles Defined:
- Accountable The developer is accountable for ensuring the rules document reflects the current version of the game and is kept accessible for testing.
- Responsible The developer updates the rules as the game evolves, especially when core systems or terminology change.
- Consulted Play-testers, rules editors, and project leads may be consulted for feedback on clarity, structure, and player comprehension.
Key Guidance:
- Rules should be updated immediately after major gameplay changes
- Keep the format readable—this doesn’t need to be pretty, but it must be usable
- Use shared docs (e.g., Google Docs) for easy commenting and team visibility
- Use consistent terminology to avoid confusion across versions and components
Action Items:
- Create and maintain a central rules document in your project folder
- Update the rules with every major iteration or new mechanic
- Include the link in all play-test kits or TTS mod descriptions
- Review and revise regularly so the draft becomes closer to final over time
Reminder: Your future self—and your rules editor—will thank you if you keep this clean and current from the start.
