Purpose:
To support remote testing, faster iteration, and collaborative development through a well-maintained Tabletop Simulator (TTS) mod—used regularly for internal testing and broader playtest coverage.
What this means:
Developers are responsible for creating and maintaining a functional TTS mod for their game. This mod should be updated regularly to reflect the current version of the game and used to schedule recurring digital playtests, including internal AEG staff sessions.
A strong TTS testing rhythm allows us to test gameplay mechanics, balance, and flow efficiently—even when physical play isn't possible.
RACI Roles Defined:
- Accountable The developer is accountable for maintaining a testable, updated TTS mod throughout development.
- Responsible The developer schedules playtest sessions and ensures participants have access and clear setup instructions.
- Consulted Other AEG team members may be consulted for internal playtest participation, rules feedback, or observation.
Key Guidance:
- Keep the mod current—update art, rules, components, and layout as the game evolves.
- Test the mod before each session to ensure functionality (scripting, shuffling, tokens, etc.)
- Schedule regular internal playtests, at least monthly, involving AEG staff when possible.
- Use external TTS testers to catch edge cases, challenge balance, or stress-test systems.
Action Items:
- Create or commission an initial TTS mod as soon as the game is test-ready
- Update the mod with each major rules or component change
- Schedule recurring playtest sessions using AEG’s internal calendar or Slack channels
- Record and summarize feedback from each session
- Ensure that the mod is accessible to all expected participants before each test
Reminder: Your TTS mod is a living prototype—keep it sharp, usable, and ready for feedback at any time.
