Collaborate, playtest and prepare a release

Return to game management

1. Use Games to return to My games, then select the game.
2. Use Edit game for manuscript changes; the tabs below the game title handle team access, testing, publishing and results.

Team: choose collaborators deliberately

1. Open Team → Add collaborator.
2. Search for the intended author by the identifiers supported in the dialog, then verify the selected account.
3. Check Access level and any notes before adding. Confirm that the intended person appears in the team list. Editing access is different from being a playtest participant.

Playtests: submit an independent test version

A playtest version is created from the current draft. Later draft edits should not be assumed to update the version participants are testing.

1. Save the draft and check player chapters, public details, delivery configuration and GM instructions.
2. Open Playtests → Submit for playtesting. Read the current requirements and declarations before deciding to submit.
3. Check the returned review status; invite participants through the permitted workflow after approval.
4. Record which version was tested and a few concrete questions, such as who waits longest or which clue is missed.

Enlarge image

Publishing: check review and release separately

1. Open Publishing and inspect Version history before submitting another version.
2. Use Submit new version when the intended draft and public details are ready. Review the current rights, declarations and release requirements.
3. After submitting, check the review result and current live version. Submission alone does not replace the live version or establish player access.

Data: turn actual feedback into revisions

Data shows available completed sessions, venue records and submitted player or GM feedback. Use its views and filters to find the relevant record, then record an observation and a proposed revision.

1. Open Data and choose Feedback, Sessions or Venues for the record you need.
2. Use the available source, venue and date filters. Session dates refer to actual start times; filtering the records does not change the overview summary.
3. Open the feedback details and record what happened, which version it concerns and the next change to test.

• Completed-session figures exclude reservations, ongoing rooms and cancelled sessions.
• Loaded records and filtered views are not necessarily a complete platform total. Read partial-data or loading notices.
• Workspace → Playtest feedback supports returning from chapter feedback to the source text; distinguish this writing feedback from session feedback.

Marketing: currently in development

The Marketing tab currently displays an in-development notice. It does not yet provide a usable campaign-management workflow. Prepare spoiler-free public game and character information in the existing editors.

Earnings: review settled records

Earnings shows the game’s loaded settled income and settled-session count. Refresh the data when needed; the account link opens the financial area for account-level information.

• Check currency, status and the current agreement when reviewing records.
• A completed session is not automatically proof of settled income. A missing record or loading error is not confirmed zero income.
• The per-session usage-fee model does not establish a universal author payout rate or settlement schedule.

A practical revision cycle

1. Test a specific version and write down what happened.
2. Edit the affected chapter, material or delivery assignment and verify saving.
3. Test the changed part, then submit the intended release version when ready.