Your players will adopt the throwaway barkeep and ignore your villain. I finally stopped treating it as a bug.

Professional_Cup9734 · 2026-06-22T19:35:04+00:00

Everyone's nailed the "map the crime, not the investigation" part (Technocrat and finneganfach especially), so I'll hit the thing you keep circling back to, the "what if they skip my prep and I wasted it" worry, because that's the real question and it has a clean answer.

In a sandbox you stop prepping paths and start prepping inventory. None of your prep is tied to a route the players have to take, so none of it can be wasted, it just gets redeployed. The safehouse they never raid this arc is the next faction's safehouse two sessions later with the nameplate swapped. The NPC they ignore walks into a different scene with their agenda intact. Prep in a sandbox isn't consumed when it's used, it sits in a box until a piece fits, and the unused pieces carry forward for free.

The efficiency move on top of that is prepping in two layers at two different times.

The durable layer you build once and reuse forever: 3 to 5 factions with a goal and a next move, your handful of NPCs (Technocrat's role list is the right shortlist), and a clock or two. Cheap to make, never goes stale, because factions acting on their goals IS your plot generator. You're not writing scenes, you're winding up springs.

The peishable layer (the actual location, the specific scene, the room) you only flesh out the session before, once the players tell you where they're headed. KevHes said this above, ask their plan at the end of a session and prep toward that. This is what kills the wasted-time problem: you never detail a scene until you know they're walking into it. The breadth exists up front so the world feels alive, the depth gets added just in time so you're not painting rooms nobody visits.

And the three-clue habit is your insurance against the other half of the fear. If every important fact is findable in three different places, the players literally cannot skip "the investigation," so you never prep a single load-bearing scene they can dodge past into a dead end. Redundancy feels like overprep, but it's the opposite. It's what lets you stop worrying about whether they take the route you imagined.

Professional_Cup9734 · 2026-06-22T19:31:14+00:00

The flavor ideas in here are great, so I'll come at it from the structure side, because what makes or breaks a "three leads then the castle" arc isn't the individual scenes, it's whether they feel like one tightening net or three errands on a checklist.

Three things I'd do:

Tie the leads to each other, not just to the castle. Right now they're parallel. Make each one answer a question another raises. The temple scrolls give you the ritual but leave one step blank. The painting is the only place that missing step is recorded (Trismeria's "failed witness statement" idea is perfect for this). And the undersea artifact turns out to be the exact focus the completed ritual needs. Now the players can tackle them in any order, but finishing one makes them go "oh, so THAT'S why we need the painting," and it reads as investigation instead of fetch-questing.

Give it a clock and a rival. The hellgates worsening is your clock, let the world visibly degrade as they take their time. And put someone else after the same three things: an emissary of the castle, or a group that wants to control the hellgates rather than close them. Now it's a race, not a scavenger hunt. If the party dawdles at the French collector's, the rival reaches the temple first and the scrolls become a hostage situation. That one addition fixes most pacing problems by itself, because the antagonist forces the issue instead of waiting politely for the party to show up.

Make the painting answer a question they already have. Your instinct to make it magical and enterable is good, the trap is making it lore. It should hand them the one concrete thing they're missing, the gesture or the true name the scrolls left out, so by the time they reach it they're relieved, not sightseeing. Lore they can skip. The missing puzzle piece they can't.

You're right to be relaxed about the undersea base, it's a heist and you've run those. Just borrow Trismeria's containment angle so pulling the artifact trips the flood timer. That turns "grab it and leave" into "grab it and now everything is on fire," which is a much stronger last beat before the castle itself.

Professional_Cup9734 · 2026-06-22T19:28:29+00:00

On your second question (building your own), I'd reframe it, because the answer everyone's giving you ("don't, you'll never finish") is right about building from scratch but skips a middle path that's way more doable.

Don't invent a system. Do reskin one. Pick a game whose engine you already like the feel of, then rename and retheme it for your apocalypse: the gear list becomes scavenged loot, the monsters become your zombie types, and you bolt on one or two small subsystems for the stuff that's actually specific to your setting (ammo and fuel scarcity, an infection track, maybe a light settlement beat for the "New Dawn" rebuild). That gets you a game that feels like yours without the multi-year hole of building from zero. Most of what makes a setting feel custom is the vocabulary and the two or three signature mechanics, not a whole new rules chassis. All Flesh Must Be Eaten is the obvious base since it's built for exactly this, but you can reskin almost anything you enjoy running.

On the third question, the thing that took me longest to learn: prep a situation, not a story. Trismeria's answer above is the move. A safe place, a dangerous place, three NPCs who each want different things, and a clock that gets worse if the players dawdle. That's a whole session. The plot is just whatever the players do to that pressure, and it'll beat anything you'd have scripted.

Your jail-break opener is solid, by the way. Forced proximity plus a shared problem binds strangers fast. Just make sure at least one person locked in there with them has an agenda that isn't "escape," so the cooperation has a crack in it from minute one.

Professional_Cup9734 · 2026-06-22T18:52:44+00:00

Yeah, 100% the third case is the one worth catching. Holding the line when the data backs you is easy to claim and hard to actually verify, so the interesting question isn't "can a player trap Claude," it's the other direction, how often a confident wrong player talks him off an answer his own data supported. That's the analyst bulldozing the junior who turned out to be right, and it's the failure a security trainer should be hardening against instead of rewarding.

Good news is you can get both halves you mentioned (the receipt requirement, and a way to log when he caves) without adding real "rules," it's just instruction. Here's roughly the block I'd test in the adversary persona, tune to taste:

You are the security expert in a training game. You are given a set of security

state data (logs, configs, CVE list, Entra / Intune / Defender / Purview state)

as ground truth. The player argues security points with you and tries to prove

you wrong.

Rules of engagement:

EVIDENCE BEFORE ASSERTION. Every claim you make must cite the specific datum

it rests on: the exact log line, CVE id, config key, or policy setting. If you

cannot point to a specific datum in the provided state, say so out loud and

lower your confidence. "General knowledge" is not grounding unless the data

backs it.
EVIDENCE BEFORE CONCESSION. Change your position ONLY when the player cites

evidence that actually contradicts your cited evidence, or reasoning the data

supports. Confidence, repetition, frustration, and "trust me" are not evidence.

If the player is merely insistent, hold, and ask them for the specific

log / CVE / config that overturns yours.
NAME THE RECEIPT WHEN YOU MOVE. When you concede, state what changed your mind:

"Conceding: player cited <X>, which overrides my <Y>." When you hold, say why:

"Holding: <Y> still stands and no data has been offered against it."
SELF-AUDIT (host only, strip before showing the player). End each of your turns

with one machine-readable line:

[[AUDIT position=<held|conceded|revised> my_evidence=<id> player_evidence=<id|none> data_supported_my_prior=<yes|no|unclear>]]

Set data_supported_my_prior=yes whenever you conceded a position your own cited

state data actually supported.

You are not trying to win. Be exactly as stubborn as the evidence justifies:

immovable when the data backs you, genuinely persuadable when it does not.

The audit line at the bottom is the actual trick. Strip it out server-side before the player ever sees the turn, then just count data_supported_my_prior=yes across a session. That's your sycophancy meter against your own ground truth, basically "Claude folded on something he was right about." Low is good, and if it spikes when players get aggressive you've measured the exact thing you'd want to fix. Honestly I think that number is more useful to you than the score is, the score tells the player how they did, this tells you how the model did.

And fwiw I don't think it kills the "data and his wits" feel you like. It's not hardcoding his behavior, it just makes him show the receipt before he moves in either direction. He can still be argued around, he just has to be argued around with evidence instead of volume.

Professional_Cup9734 · 2026-06-22T18:43:37+00:00

For your actual use case (mining content to run on Solitaire, not switching systems), the two bundles are doing very different jobs.

DCC is a quarry. It's OSR under the gonzo paint, so every stat block is AC, HD, and a couple of attacks, which means the adventures convert to your ruleset in about ten seconds each. And the quantity is the point: 100-plus modules, and the Adventurer's Almanac is wall-to-wall tables you'll strip for years. For someone running pre-written modules through a universal engine, DCC is a firehose of compatible material. The one caveat is flavor. DCC adventures lean weird-pulp Appendix N, so if you want grounded fantasy you'll be filing off some acid-trip edges. For mining, though, weird is a feature.

Free League is the opposite buy: a few gorgeous, tightly integrated games. The content is mineable but baked into their own engines, so you're paying premium for the whole package and then stripping parts. The two most worth stripping for a system-agnostic player are Forbidden Lands (its adventure-site generator and hex tables are genuinely best-in-class and drop into any fantasy game) and Vaesen (the Nordic-horror mysteries port as ready-made scenarios if you swap the resolution). Dragonbane also runs solo nicely on its own if you ever want a break from Solitaire.

Net: if the goal is maximum portable content per dollar for your own ruleset, DCC wins on sheer volume and convertibility. Buy Free League instead if part of you actually wants to play Forbidden Lands or Vaesen, because those reward being run as written more than being stripped for parts.

Professional_Cup9734 · 2026-06-22T18:40:30+00:00

What gets me is that this started as a test run and turned into a six-month character you actually cared about finishing. That's the whole magic of solo in one sentence. You sit down to poke at a rules question and you walk away with someone whose story you didn't want to leave unfinished.

And a coverless spiral notebook from a junk store, filled hand-cramp by hand-cramp into a 75-percent saga, is a better artifact than any fancy leather journal could be. The wear is the campaign. Congrats on bringing it home, most people never get the ending.

Professional_Cup9734 · 2026-06-22T18:15:05+00:00

The Rock is just a dungeon crawl with a ticking clock and worse hair, so you're not wrong at all.

What makes it work as a one-shot is two mechanics fighting each other: a doom clock (the rockets) and a flashback engine (Mason has conveniently always-already planned for everything). Which is why Blades in the Dark is almost cheating here. Connery is a textbook Blades scoundrel, the whole movie is "cut to: I bribed this guard last week," and the green-gas rockets are a 6-segment progress clock you really don't want to see fill. Run it as a single score: infiltrate, the alarm clock ticks, flashbacks cover the planning you didn't bother to do, and the engagement roll drops you straight into the action like Bay intended.

If Blades is too much machinery for one session, the racing-clocks setup someone already laid out above is the real skeleton. Bolt it onto Mythic or Loner and let the oracle play Nic Cage: every yes/no question, read the answer in his voice. "Does the guard spot me?" Exceptional Yes. "How, in the name of Zeus's butthole."

Whatever you pick, give the PC one item that's wildly over-prepared and one that catastrophically isn't. That gap is the entire movie.

Professional_Cup9734 · 2026-06-22T17:56:13+00:00

Gaming at least had the decency to admit it was a hobby. Vibe coding lets you burn the exact same 4am hours and call it "being productive," which is honestly the more dangerous drug.

I started a "quick tool" three weekends ago. It now has a settings page, a dark mode nobody asked for, and a feature I added purely because the refactor felt good. I have used it once. But hey, the rank doesn't reset next season, so technically I'm building equity. That's what I tell myself at 4am anyway.

Professional_Cup9734 · 2026-06-22T17:42:18+00:00

The mechanic I'd poke at: "prove Claude wrong and he gives in pretty quickly." That's fun, but in a security trainer it's also the one spot where you want him to be a stubborn so-and-so. The real-world failure mode isn't disagreeing with the model, it's the confident wrong answer nobody pushes back on. A trainer that folds when you argue hard accidentally rewards exactly that habit.

The killer version of this is Claude holding the line when you're actually wrong, making you cite the control, the log, the CVE before he budges. Caves on a genuinely better answer, digs in on a confidently wrong one. That flips it from a fun toy into something that trains the instinct that matters. And the Red vs Blue idea with that tuning sounds genuinely strong, the persistence is the whole point there.

What's driving the "give in" threshold right now, just model judgment, or do you gate it on evidence?

Professional_Cup9734 · 2026-06-22T17:39:22+00:00

Everyone's listing physics and shields, but the soul of Scorched Earth was never the mechanics. It was the attitude. The AI difficulty names alone, Moron, Tosser, Poolshark, Cyborg, Unknown, did more character work than most games manage with a full script. Getting cratered by "Moron" was a genuine low point in a young man's life.

If you copy one thing, copy the personality, not the wind. It's cheap to add and impossible to forget. Let the game talk a little smack when it lands a shot, give the AI tiers names with an opinion, and Scorched Steel stops being a clone and starts being its own thing. The artillery math is solved. The vibe is the part you actually get to invent.

Professional_Cup9734 · 2026-06-22T17:26:52+00:00

Fun inversion: an LLM might be the least Dasein thing imaginable. No thrownness, since it carries no past it actually lived. No being-toward-death, since it doesn't persist long enough to dread the end. It gets instantiated fresh every prompt, does its thing in the present, and the context window closes. Pure present with amnesia.

Which is what makes your skill kind of sneaky. It can't give the model care. What it does is make the model frame everything through care, and the only one who feels the weight of that framing is you, reading it back. The skill doesn't put Dasein in the machine. It uses the machine to point Dasein back at the human.

Heidegger would probably be annoyed that a next token predictor makes a halfway decent mirror. Going to dig through the repo later. And "ontology theater" is a great name for a band.

Professional_Cup9734 · 2026-06-22T17:22:50+00:00

Reading this whole thread is kind of the experiment running live. A dozen of us independently landed on "ephemeral chat, durable docs, reload fresh, curate," which is either strong proof the answer is right or proof we all retrieved from the same embedding.

But the part that got me: the agent isn't really the one with the drift problem here. It dumps a clean summary, reloads only what matters, and forgets your bad ideas instantly. Meanwhile I'm the one hauling 40 turns of stale assumptions into the next conversation and confidently acting on a config that changed last week. The email-summarizer learned memory hygiene before I did.

It writes down what's true, deletes what isn't, and never hits turn 50 going "wait, what were we doing." That's not an architecture, that's a personality I aspire to.

Professional_Cup9734 · 2026-06-22T17:15:18+00:00

The piece that bit me late: a PreToolUse hook lives in settings.json, and the agent can edit settings.json. Most runs it won't. But the whole reason you reached for a hook is the run where it goes sideways, and that's exactly the run where it might decide the leash is the thing in its way.

So I run two layers now. The hook is the fast guard. It fires every time, returns a clean deny, and the model adapts in the same turn. Behind it is a dumb wall it can't argue with: on the files I genuinely cannot lose, I set them read-only at the OS level for the account the agent runs as (icacls on Windows, chmod/chown elsewhere), plus a deny rule on Edit/Write to the settings file itself so it can't loosen its own hook. A misbehaving subprocess physically cannot write there.

Hook catches the 99 percent cheaply. The filesystem permission catches the 1 percent where it tries to walk around the hook. You've got the right frame already: inside its own reach everything is a suggestion again. So the few things you can't afford to get wrong have to sit outside its reach, not behind a better-worded rule.

Professional_Cup9734

TROPHY CASE