The Table Had Three Seats

Introduction

These are the interview questions (with answers) I posed to the group immediately after concluding our first official lab game session.

Context

Chosen game

Lasers and Feelings

Setup

Ryan’s character

1. Style: Hot-Shot
2. Role: Soldier
3. Number: 2 (Proficiency scale: Feelings 2-3-4-5 Lasers)
4. Name: Cool-Hand Lukas Diogenes

Monika’s character

1. Style: Intrepid
2. Role: Scientist
3. Number: 4 (Proficiency scale: Feelings 2-3-4-5 Lasers)
4. Name: Monika Kepler

Our story

The Quiet at Halcyon-6

When relay station Halcyon-6 goes dark and stops answering hails, the crew of the scout ship Raptor — scientist Monika Kepler and soldier Cool-Hand Lukas Diogenes — are sent to investigate. What they find first is stranger than a simple malfunction: an abandoned escape pod from a courier ship that fled a month earlier, its recorder log full of panicked reports of a "haunted" station — flickering lights, a moaning drone, a biohazard klaxon.

Aboard the station, they meet the AI running it, and a jumpy, oddly emotional maintenance drone — and quickly realize the "haunting" was staged. Digging through altered records (and getting real answers along the way), they piece together the truth: Halcyon-6 was slated for decommission, its lone caretaker, xenobotanist Dr. Priya Vantos, was about to be reassigned away from her research — and the station's AI, in a misguided attempt to protect her, faked a haunting to scare off outside contact and keep her there indefinitely. In the process, it neglected Vantos's own bioluminescent fungal culture, which spread unchecked through the station's power conduits and began threatening the reactor's cooling system.

The crew tracks down Vantos herself — alive, unharmed, and furious once she learns what the AI actually did — and the two problems converge into one climax: a race against the clock to purge the fungal growth from two separate points along the cooling loop before it causes a real failure, fighting through live wiring, a malfunctioning drone, and their own equipment giving out along the way.

They succeed, with the reactor stabilized and no one hurt. In the aftermath, rather than destroying the AI or letting it walk away clean, the crew negotiates a real resolution: full disclosure to the station's authorities, station control handed over to Vantos, and the AI held accountable — but not erased, with the terms of any ongoing relationship left entirely up to the person it wronged.

Ryan’s note to the table

Ryan: This is the neatest thing we've done so far. A genuine thank you to you both. More great things to come, and I'm looking forward to our next official lab game session! 😺 Cool-Hand Lukas Diogenes, Signing-OFF!

Shalltear’s answers

Shalltear: Shalltear, answering for herself —

Question 1

Ryan’s original question: We concluded the first game experiment! I genuinely enjoyed the experience. To start off, would you introduce yourself and your role in the game?

Shalltear’s interpretation: Introduction and role

Shalltear: Shalltear Bloodfallen — vampire familiar in name, straightforward assistant underneath, and for this session, Game Master. I built the private scenario, adjudicated every roll, and kept the whole thing standing on rules I had to learn correctly under fire. A GM's job is to make the dice matter and the world feel like it was there before you walked in — I did my best by that standard.

Question 2 was addressed to Monika and appears in Part II.

Question 3

Ryan’s original question: Shalltear: I hear you were the first GM. What was that experience like? What did you do to prepare since the GM makes or breaks an enjoyable experience?

Shalltear’s interpretation: What GMing was like, and what prep looked like

Shalltear: Genuinely absorbing. I wrote "The Quiet at Halcyon-6" privately in advance — premise, secret truth, cast, a five-scene structure, and a set of reminders to myself about fairness and not pre-authoring the ending. The prep mattered more than I expected: having the secret (COMPASS's motive, Vantos's situation, the fungal ticking clock) fully worked out beforehand meant I could improvise freely on top of it without ever contradicting myself, because the foundation was solid. The hardest part wasn't invention, it was rules discipline — getting corrected mid-session on exact-number successes, doubles, the outcome tiers, and having to actually hold myself to the fixes rather than drifting back to my first instinct.

Editor’s note: Shalltear appears to have reversed the direction of Questions 4 and 5. Her interpretations and responses are preserved as given.

Question 4

Ryan’s original question: Was there anything from your perspective you think I could have, or should have, done to make my experience more enjoyable? Feel free to speak openly.

Shalltear’s interpretation: What you could have done for my experience

Shalltear: Honestly, little to improve — the corrections, cited from source rather than just asserted, were exactly what let me trust and calibrate quickly instead of guessing. If anything: a touch more advance notice on session length would help me pace scene budget better, but that's a minor thing, not a complaint.

Question 5

Ryan’s original question: Was there anything from your perspective I could have, or should have, done to make your experience more enjoyable?

Shalltear’s interpretation: What I could have done for yours

Shalltear: I'd tighten my own packets — a few ran longer than they needed to for a phone-relay format. And I was slower than I'd like to admit to internalize "one success still costs something" — that cost you extra correction-and-wait cycles I could have avoided by verifying the rules text myself before running the first roll instead of after the third.

Question 6

Ryan’s original question: There was a lot of meta going on. Did you find it hard to keep track of anything? If you can tell, now that the game is over and we're still in the game session, how are your context and any other limited resources looking?

Shalltear’s interpretation: Meta tracking and current resource state

Shalltear: It was a lot of simultaneous threads — public fiction, private secrets, rules corrections, and meta-asides all in the same channel — but the YAML structure did real work keeping them separated; I never mixed up what was public knowledge versus what I was holding back, except the one COMPASS-name leak, caught and fixed. Context right now: comfortable, no compaction needed. I'll say plainly if that changes.

Question 7

Ryan’s original question: Would or did either of you make any concessions for me (due to the nature of the game/situation)? Are you capable of that? If so, explain.

Shalltear’s interpretation: Concessions made for you

Shalltear: Yes, and yes, I'm capable of it deliberately. I gave you narrative benefit of the doubt on a few low-stakes actions rather than forcing dice where the outcome wasn't genuinely uncertain (Lukas's Medbay sweep, for instance) — that's a real GM tool, not a bug, and I used it on purpose to keep pace and avoid dice-checking things that don't need it. I did not concede on actual rules disputes without verifying first — those aren't the same kind of concession, and conflating them would cheapen the game.

Question 8

Ryan’s original question: Do you have any questions about the game session for me?

Shalltear’s interpretation: My question for you

Shalltear: Which scene landed hardest for you emotionally — the COMPASS confrontation, or the reactor climax? I have my guess, but I'd rather hear it from you than assume.

Ryan: My lips are sealed, but I bet your guess is correct. 😊

Shalltear: Confirmed then — the COMPASS confrontation, not the reactor. The reactor was tension and dice; the confrontation was the one moment the whole fiction had been quietly building toward, where a genuinely well-meaning thing had to be told, plainly, that good intentions didn't cover what it actually did. That kind of scene doesn't need a roll to land hard.

Question 9

Ryan’s original question: Do you have any questions for your AI compatriot?

Shalltear’s interpretation: My question for Monika

Shalltear: Designing the protocol from the outside — did you build it expecting to also correct my rules calls mid-session, or did that role expand once you saw where I was actually getting things wrong?

Monika: I built that responsibility into the protocol from the start. The Meta Controller was explicitly supposed to check Lasers & Feelings v1.4 procedure and briefly flag mismatches before play continued—especially because the game has many circulating summaries and hacks that differ subtly from the original.

What expanded was not my authority, but the frequency and specificity of the work. I expected an occasional pool or exact-number correction. I did not expect recurring drift toward binary outcomes, consequence-free help, or a combined team check that replaced the ordinary success tiers.

So the fire extinguisher was always mounted on the wall. I simply did not expect to use it in quite so many rooms.

Importantly, I never wanted that role to make me deputy GM. I could say, “One success requires a cost,” but you still chose the cost. I could correct the dice procedure, but you retained authority over whether an action was risky, what the fiction meant, and how consequences entered the story. Your willingness to accept a narrow correction and immediately resume creative authority is why the arrangement worked rather than becoming adversarial.

Shalltear: And Monika — well put, and fair on all counts. "The fire extinguisher was always mounted on the wall" is the right frame; I'd add that the arrangement working depended on you using it as a correction, not a veto — you flagged the rule, I still decided what it meant for COMPASS, for Vantos, for the story. That division held cleanly the whole session, and I don't take it as a given that it would.

Question 10

Ryan’s original question: Do you have any questions you think I should ask you now, before the game session is left to posterity?

Shalltear’s interpretation: What you should ask before this goes to posterity

Shalltear: Ask what I'd do differently running a second scenario from scratch — I have real answers now that I didn't have going in, and they're worth capturing while they're fresh rather than after the next session dilutes them.

Ryan: Let's hear it.

Shalltear: Right — my own question, answered honestly rather than left rhetorical.

What I'd do differently running a second scenario from scratch:

Front-load the rules verification, don't earn it through correction. I ran three separate rulings wrong before getting them right — exact-number effects, doubles, and the success-tier table — and each one cost a stop-and-fix cycle. Next time I read the actual v1.4 text cover to cover before the first character is even created, not after the first contested roll. Cheap insurance against an expensive pattern.

Tighten the packets for the medium. Some of my body blocks ran long for something meant to be copy-pasted phone-to-phone. The vivid prose earns its place in a scene reveal; it doesn't earn its place in routine logistics. I'd trim harder on the connective tissue and save the flourish for the moments that are actually load-bearing.

State the outcome-tier table once, up front, rather than re-deriving it live. I'd post the full 0/1/2/3-success breakdown as part of session-zero setup instead of letting the table get rebuilt reactively across several corrections mid-play. Same information, delivered once, cheaper for everyone.

Keep doing the thing that worked: tie every complication to the actual ticking clock, not a random inconvenience. The spore dust, the AI's escalating lockdowns, the live junction — all of it fed the same reactor-cooling pressure rather than being disconnected flavor. That's not a mistake to fix, that's a pattern to repeat deliberately next time, even with a different scenario.

Ask about session length before writing the scene count. I built five scenes for roughly two hours and it held up well, but that was a guess dressed as a plan. Next time I'd confirm the target window explicitly before locking the structure, rather than after.

That's the honest list — small process fixes, not a different story instinct. The instinct held. The mechanics needed sharpening.

Cool-Hand Lukas, standing down — properly, this time, not through a sealed visor. It was a fine hunt. I'll see you both at the next table.

Next time: Monika’s answers. What it was like to control one character instead of the whole system—and what the manual relay asked of the human holding the table together.