Field manual
How the game
works in Slack.
Learn how to install, start, join, vote, and administer Trustactic without confusing Slack gameplay with browser administration.
Product boundary
Slack gameplay
The game lives in Slack.
Commands, prompts, votes, night actions, and reveals all happen in team chat. The browser is not the play surface.
Browser administration
The webapp handles setup and control.
Install, billing, workspace defaults, usage, history, recaps, and support all belong here instead.
Quick start
Use this order for a first game.
The fastest safe path is install first, channel second, lobby third, and browser administration only after the Slack side is live.
First game path
Install the Slack app
Start from the Slack install flow so the workspace is connected to the installer browser session.
Add the app to a Slack channel
Choose the room where the game will actually unfold.
Open the lobby
Run the first setup command in that channel.
/trustactic newLet players join
Each player joins from the same Slack channel.
/trustactic joinBegin the game
Start role dealing and the first live game once the room is ready.
/trustactic beginField note
Use the right reference next.
Once the room can open cleanly in Slack, use the deeper references below.
Install in Slack
Authorize the app and hand the browser session to the workspace installer.
Set up your first game
Follow the linear first-game path from channel install to `/trustactic begin`.
Understand the player flow
See how the lobby, discussion, banishment, night, and finale play out in Slack.
Read trust and legal
Privacy, terms, cancellation, and security boundaries for the hosted service.
Game flow
What the room experiences.
This is the public game rhythm customers need to understand before they install or host. It explains the flow without exposing hidden role state.
Field note
Lobby
A workspace user opens a lobby in a Slack channel with `/trustactic new`. Players join from that same channel with `/trustactic join`.
Field note
Role dealing
When someone runs `/trustactic begin`, the Game Master deals roles and private prompts in Slack. Players do not move into the browser.
Field note
Discussion / Round Table
The channel debates in public. The Game Master tracks the phase and opens the vote inside Slack.
Field note
Banishment
Players cast banishment votes in Slack. The Game Master announces the result and handles the reveal flow according to the phase.
Field note
Night
Traitors act in private Slack surfaces. Missions, shields, and special prompts can also appear when the current template uses them.
Field note
Breakfast and finale
The next day begins in Slack. If the game reaches the finale, the room continues through final banishment and end-vote steps until the game closes.
Command reference
Public Slack commands only.
This field manual keeps the top-level command list focused on first-game setup and safe operational checks. Internal recovery tools and deeper phase-specific prompts are intentionally excluded from the public site.
Setup commands
These are the normal workspace commands used to open and start a game in Slack.
/trustactic newOpen a new game lobby in the current Slack channel.
If the workspace hits the free-plan gate, the response can include an upgrade path instead of creating a lobby.
/trustactic joinJoin the current lobby in that channel.
/trustactic beginBegin the game once enough players have joined the lobby.
This starts role dealing and the opening flow in Slack.
/trustactic statusCheck the current game phase and safe progress information.
This is operationally useful without revealing hidden roles or private actions.
Console
What the browser is for.
Workspace admins use the console for configuration, billing, usage, history, and support. Players do not need web accounts to play.
Field note
Console for workspace admins
The console exists for the customer/operator path, not for gameplay.
No browser gameplay
Players stay in Slack.
The browser is not where votes, night actions, or player chat happen. That separation is part of the product design and privacy boundary.
Troubleshooting
First things to check when the room goes wrong.
These are the common issues a workspace organizer hits during install and the first live game.
Field note
Common issues
Trust and legal
Read the service boundaries before you install.
The legal/trust surfaces should be easy to reach and easy to read. They explain how the hosted service handles data, billing, cancellation, and support.
Field note
Frequently asked before install
These are the practical questions most teams need answered before they invite the app into a workspace.
FAQ
Is the game played in Slack or the browser?
Slack. The browser is for install, setup, billing, history, recaps, and workspace administration.
Do players need web accounts?
No. Players can join and play through Slack alone. The browser is mainly for the workspace admin path.
What does the Slack app need access to?
Enough Slack access to post public announcements, send private prompts, handle commands, and operate the Game Master flow cleanly.
How do plans affect games?
Free is for a first ritual in one workspace. Paid plans expand recurring access, history, and advanced hosted support.
Who can access the console?
The installer browser session and authorized workspace admin paths. Players do not need console access to play.
Why are debug commands missing here?
Public docs only describe supported customer-facing Slack commands. Internal recovery and operator tools do not belong on the public docs surface.
Field note
Trust pages and contact path
Read the service boundaries in plain language, then use the support route if a workspace-specific question remains.