Who this is for now: teams that build AI
After 0.7.0, Chris asked a simple question. Would this game be a great team-building exercise for an AI development team: something they play together, laugh at the struggles they recognize, and have fun with?
The honest answer was: it could be, and the fit is unusually good. But nobody has played a full shift with five people, so a first session would really be a playtest.
Then he made it the target. From here on, every design decision is made for a team that builds AI products, playing together.
Why it fits
The joke is their job. Clancy confidently replaces your command with something you didn't ask for, then announces it cheerfully. The skill the game teaches is noticing and checking. A team that ships AI features has lived that, and laughing at it together is a relief.
Nobody can win alone. One shot takes five chairs: power from Engineering, a lock from Science, the arc from Helm, a signature from Command, the trigger from Guns. That makes people talk and time things together, which is what a team exercise is for.
It rewards coordination, not reflexes. Since 0.6.0, buttons are timed orders. The best shot comes from two people lining up their orders, not from the fastest click. Someone who doesn't play games can hold a chair well. Command, for example, is all timing and judgment.
It's built for a group session. Shifts run about fifteen minutes. Since 0.7.0 the crew waits in the break room between shifts instead of being disconnected, and phones and PCs play together.
Where it could fall flat
The fun is unproven. Nobody knows yet whether a five-person shift is fun.
The satire cuts close. For a team that builds AI products, jokes about confidently wrong AI could feel cathartic or a little pointed, depending on the team. The rule is that the joke is always aimed at the tool and the company, never at the people in the chairs.
Setup is still too much work. Everyone needs an invite, an account and the right build. The first twenty minutes of a session could turn into IT support.
Experienced gamers can take over. Right now, when someone hosts a game on their own machine, the host can switch chairs and press buttons on stations other players are sitting in. One experienced gamer could end up playing everyone's job.
What changes because of this
The project now has a written set of principles that every feature has to pass:
- Does it make crewmates talk to, wait for, or rely on each other?
- Can someone who doesn't play games do it well?
- Does it add a step between "you're invited" and "you're on the bridge"? If so, what does it remove to make up for it?
- Is the humor aimed at the tool and the company, not at people?
- Does it give the team something to talk about afterward?
- Does it work for a crew where nobody has leveled up?
- Has it been seen in a five-person playtest, and if not, do we say so?
That last point matters for 0.7.0. Characters and leveling stay, but a team session has to be just as good for a crew of brand-new contractors. Progression is a bonus, never a gate.
What's next, in order
- Team session mode. A host opens a private crew with one join code, assigns the chairs, and can rotate them between shifts. A session is a set number of shifts, three by default. Progression is optional, so nobody is out-leveled.
- A debrief card. At the end of a session it shows the slop each person caught and what tipped them off, the coordinated perfect shots and who was in them, the pings and handoffs per chair, and the quietest stretch of the shift. Then it asks two questions: "When did someone catch Clancy, and how did they notice?" and "Where did we stop talking?"
- One-link onboarding. One invite link takes a teammate through making an account, getting the right download for their device, signing in and joining with the code, with a version check before anyone tries to connect.
- Guards against one player carrying everyone. In multiplayer you control only your own chair. Each role gets a moment where the shift visibly depends on it.
- Logging for playtests. Orders, catches, pings and timing per chair, recorded for each session. That feeds the debrief card and the tuning.
- Notes for whoever runs the session. One page: do the tutorial beforehand, assign chairs that differ from people's day jobs, play three shifts, then take ten minutes to debrief.
Anything not on that list waits, unless it fixes something broken.
What we don't know yet
- Whether any of this is fun with five people. It's the same open question as every other post. If your team would try a session, we'd like to hear from you, especially about what would make it easy to set up.
Kind regards,
Ambit