Hey!
Thanks a lot for using TRS and for the super detailed report. You gave the exact steps and symptom, which made it easy to act on. It was the first thing I did this morning, because a variable getting stuck like that can quietly break a whole game.
Good news: it's fixed. ✅
In plain terms, your game has two layers:
- The blueprint: what you build in the Editor, including each variable's starting state (e.g. "gate #2 = OFF").
- The playthrough: the live session, where things change as you play.
The bug: beating the boss wasn't just flipping the variable in your current playthrough. It was also writing "ON" back into the blueprint.
So your saved default got permanently changed, every new run started with gate #2 already open, and the Editor showed it stuck at "Current State: ON".
The fix makes beating an enemy affect only the live playthrough. Now:
- Beating the boss opens gate #2 during that run ✔️
- Your authored blueprint stays untouched ✔️
- Restarting resets the variable to OFF, so it's fully reusable ✔️
I also added automated tests (including one that runs your exact "2 gates + end-boss" scenario end to end) so this can't come back.
PS: thanks for the heads-up on the games list! Appreciate you tracking those down, and shout-out to Luisworks for The Legend of Elda being your way into TRS. I'll get the count sorted.
Thanks again for making the engine better. Happy building!