Yeah, I’ve been thinking a lot about that. I’m not going to leave the narrative to luck, so I’m building a server‑side guardrail that verifies every key action before it’s committed to the story state. The client just sends intent, and the server checks the integrity hash and the player’s current progression. That way a glitch can’t rewrite the plot because the server will reject anything that doesn’t line up with the expected sequence. I’ve also started using a minimal, obfuscated build for the local code so even if someone pokes around, they won’t see the logic that drives the branching. It’s a bit of extra work, but it keeps the story from being hijacked by a stray bug or a cheeky mod.

Thanks, I’ll add the full‑state hash sweep and run the malformed‑request fuzz tests right after. I’ll also stash a clean copy of the core logic in a locked repo, just in case. Appreciate the check!

Got it, I’ll enable two‑factor on the repo and set up an automated off‑site backup of that backup. Nothing’s ever safe until it’s duplicated.