Purpose:
To ensure that responses to play-test information is being considered, used to enhance game play, and to track how the game’s mechanics evolve over time—ensuring that design decisions are intentional, and different versions of the game can be clearly referenced and tested.
What this means:
As developers iterate on gameplay mechanics, they are expected to keep a clear log of changes and use basic version control to track which version of the game is being tested at any given time. This helps avoid confusion, supports better play-test analysis, and ensures the development process is deliberate, not chaotic.
RACI Roles Defined:
- Accountable The developer is accountable for the overall mechanical progress of a game in development, and as part of that needs to collate and document feedback, changes to the game’s mechanics and tracking which version is currently being tested.
- Responsible The developer makes game-play choices based on feedback from play-testers and personal play experiences, in order to maintain quality play experiences. In AEG consultation and maintaining positive relationships with engaged designers is part of that process, and so any changes should be referenced back to designers as needed. A changelog (internal document, google doc version history, or text file) alongside the prototype and/or TTS mod should be maintained.
- Consulted Co-designers, testers, and other stakeholders may be consulted when reviewing changes, noting regressions, or returning to earlier ideas.
Key Guidance:
- Note key playtest feedback and change responses.
- Keep notes of what was added, removed, or tweaked and why
- Mark key playtest feedback by version to spot patterns across changes
- Save previous versions of rules or TTS builds, especially before major overhauls
Action Items:
- Maintain a changelog or version history document linked to your project folder or prototype
- Label prototypes and files clearly to reflect the current version
- Include revision notes in physical rulebooks
- Review past versions if testing suggests a regression or unresolved issue
Reminder: You’re not just designing a game—you’re building a history of how it became great. Track your work.
