Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

Thanks for the thoughtful feedback, Operator — really appreciate you taking the time to explore it this early!

The slightly cramped layout is intentional — it’s meant to feel close and a bit oppressive, like the terminal is breathing with you. That said, I’ll make sure desktop scrolling behaves properly in the next patch. The experience was built mobile-first, so the virtual keyboard and spacing lean toward that setup, but I’ll “fix” it so desktop is fully served too.

The missing README.txt is actually part of the fiction (EVE’s selective honesty 😉), and nothing in the system is case-sensitive — she’ll respond the same either way.

Thanks again for the detailed notes and for tuning into the signal this early. Every echo helps refine the next one.

I can get a protocol_01_overide.log "Decryption successful" but it stays red and has the same prompts when I try to view it.

(+1)

You’ve found a fantastic and very sneaky little bug — great spot! You’re not doing anything wrong.

It’s actually a race condition in the logic: the file unlocks successfully, but a helper routine that updates your memory cohesion immediately flips it back to “locked” about a millisecond later. So it’s unlocking perfectly — just not staying that way.

I’ve already patched it locally and will push the fix live within the next 24 hours. Thanks again for catching this — that’s exactly the kind of sharp feedback that helps refine the signal for everyone.

@drelbs Just pushed a patch that fixes this issue — you were absolutely right about what was happening!  

The unlock logic now behaves exactly as intended, and `protocol_01_override.log.lck` should properly stay decrypted once accessed. Huge thanks for catching that — it was a rare one to spot. Appreciate you helping make the build tighter for everyone!