BTW I looked in the code and it's just a theory, but I think that it's very likly that the back button breaks the game. I won't recomend to be used. I'll try to explain. Most SugraCube games just changes some values when you press a button or link, the back button returns them to the previous values. Everyting is fine. But here a lot of things that are used to trigger events doesn't happens in the SugarCube code. The author decided to put a good chunk of the code in native javascript fuctions that are called from timers (this window.someting errors that a lot of people reports). So what probablt happens is when you click some button or link the game state advances and sometimes some timer is triggered with the new values before you press the back button and return the old. The back button restores the previous SugarCube state, but not what the native timer managed to do. So the state is broken and this leads to buged quests, broken states, etc. And this is hard to noctice imediatly and can be fixed latter. BTW save scumming probably have the same issue if you not fully reloading the game and start from the main screen before loading. This won't happen everywhere, but it's dagerous when advancing to a new day or around places that have event triggers or just count the progress for a event.Cheat 'back button'?? Most useful cheat for me)))