Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Very Annoying Issue!

A topic by Gamer735 created 36 days ago Views: 113 Replies: 6
Viewing posts 1 to 3
(2 edits)

I've not been using TRS (Tiny RPG Studio) very long, but as is sometimes common with these small browser-based engines, the logic within the Editor can get messed-up, particularly variables.

After putting 2 gates ("magic doors") in 2 different rooms and an end-boss with a variable to open gate #2, then playing my game in the Editor, once I run the Game and beat the boss, the variable I used for gate #2 has: Current State: ON, and Stays Set At That (ie. that variable CAN'T be used again EVER in my game, as it's PERMANENTLY Now ON!).

Any fix for this apparently OVERLOOKED BUG???

PS: Off-Topic, there are currently 34 TRS Games made (your Milestone of 30 is MISSING: Serving Time by VeryLukely [well, he's HIDDEN it, so good luck with that one!], Tutorial by Diguifi Studios [you list it on one of your pages though], Test by JeanCarls, The Legend Of Elda by Luisworks Studios [thanks to him that I even found TRS!]). And that's NOT including any other content creators who choose to make more TRS Games in the future who may just decide to only post on their itch.io Profile instead of here.

Developer

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!

Wow, that was FAST! Thank you so much!

Yes, it was literally breaking my games to the point that I wasn't sure there was even a way to fix it, and I barely started using TRS when I noticed the Bug right away. I even tried the Reset button and Reloading the WebPage, but to no avail.

I really appreciate you breaking it down the way you did, and also for other users. It shows how much you and Diguifi Studios care about this nice little engine you've made. I'm more than happy to report any Bugs so that it can make TRS even better. You even made a failsafe to prevent that Bug, which is awesome!

You're quite welcome for the feedback and TRS Games count. I've had other itch.io users alert me of other Bitsy-like engines within the past few months or so as well (eg. Whimtale, Wareware), so it's only fitting that yet another would point me to TRS. I'm grateful.

(4 edits)

Well, I hate to be "that guy" here, but I Imported my previously Exported (Saved) Game so that I could implement your Fix (ie. change Variables to the Ordered ones I wanted before the BUG happened), but when I Set my End-Boss + Gate (Magic Door) Link to my previous Variable, you guessed it, it was STILL turned ON!!!

Thanks for your prior Fix, but it didn't seem to work...

I DO have some GOOD NEWS for you though, to help you pin it down better:

- besides some of MY TRS Games in the Editor, it ALSO Happens when you Beat and Replay certain Users' created Games too!

Here's a list (only small right now until I've played ALL 33 [excluding Serving Time!]) of those TRS Games: 

1. Diguifi Studios': Tiny RPG Tutorial.

2. JeanCarls': Tiny RPG Test (the First Fan-Made TRS Game, just a bit before: The Worst RPG Ever).

Besides the BUG with the (at least) 2 TRS Games I listed above, I need to get another BUG posted that's been plaguing the engine for a while:

When switching screens (rooms, scenes, maps), a Glitch can often occur temporarily: the top of the screen will move down, which can be quite jarring for users (even though it lasts only a couple seconds). Have you tried to fix this?

Just want to post an UPDATE here. First, thank you to the 2 Devs for their recent fixes!

The switching rooms BUG is STILL active. Please try to work on a fix if possible when you get the time. Thanks!

Developer

Hi, just reading this thread, could you provide a short video, or even share here the URL of a game where this behavior is replicated? I’m not sure if I understand how the bug happens