What with all those devs using tons of endless loop nowadays ? It's messy, time consuming, it completely break the rollback, and, more than anything else, I still didn't found one that wasn't totally useless and can't be replaced by some proper Ren'py code.
So,
@Ranger , please change this messy thing:
Code:
label wait:
window hide
show screen gui_actions
jump action_wait
label action_wait:
pause
jump action_wait
By this correct one :
Code:
label wait:
window hide # probably not event needed
call screen gui_actions
jump expression _return
Then make your "gui_actions" screen
return instead of
jump :
Code:
screen gui_actions:
[...]
imagebutton:
[...]
action Return("show_quest_help")
[...]
It will do
exactly the same thing, except that it will be bug free. No more game crashing, by example, because the player just wanted to explore the ship and so gone to an empty place.
Then also correct your "s_quests_ui" screen, starting by its opening :
Code:
label show_quest_help:
hide window
hide screen gui_actions
$quest_text = QuestTuple("", "")
show screen s_quests_ui
jump action_wait
label close_quest_screen:
hide screen s_quests_ui
jump go_to_location
replaced by this :
Code:
label show_quest_help:
hide window # probably not event needed
hide screen gui_actions # probably not event needed
$quest_text = QuestTuple("", "")
call screen s_quests_ui
jump go_to_location
Then remove all the useless "action Jump("action_wait")" in the screen itself.
Once again it will do exactly the same thing, without the bug and the rollback breaking part.
The "s_quests_ui" screen can also benefit from the screen
You must be registered to see the links
statement (with the help of the
You must be registered to see the links
screen action) but well, it don't break the game, so do as you want.