Page 2 of 2
Re: Allowing saving during splashscreen
Posted: Mon Sep 03, 2018 6:01 am
by Remix
Code: Select all
label before_main_menu:
if not persistent.seen_prologue:
$ renpy.jump_out_of_context("prologue")
return
label prologue:
"1"
"2"
"3"
if not persistent.seen_prologue:
$ persistent.seen_prologue = True
$ renpy.call_in_new_context("_main_menu")
return
label start:
"Start"
"Middle {a=call:prologue}read prologue again{/a}"
"End"
return
If I read your requirements correctly, that should do the trick.
Re: Allowing saving during splashscreen
Posted: Mon Sep 03, 2018 10:39 am
by Coren
Hmm, I tried that and I can't call the save screen during the prologue. I'm familiar with persistent switches, I'm just hoping to be able to allow the player to save during the prologue so they don't feel obligated to finish it in one sitting
Re: Allowing saving during splashscreen
Posted: Mon Sep 03, 2018 1:22 pm
by Remix
Strange, it works fine for me on 7.1.0.795.
What code are you using?
Which Ren'Py version?
Re: Allowing saving during splashscreen
Posted: Mon Sep 03, 2018 3:02 pm
by Donmai
Re: Allowing saving during splashscreen
Posted: Mon Sep 03, 2018 3:08 pm
by Remix
My version uses that (which incidentally runs in the same context as main menu so does not allow saves/right click)
then jumping out of context (to allow saves etc)
in the prologue label (which then sets the persistent so you can access main menu without before_main_menu doing its thing again)
Seems a logical way to approach the problem.
Re: Allowing saving during splashscreen
Posted: Mon Sep 03, 2018 3:30 pm
by Donmai
Ah, didn't see your post. Sorry.
Re: Allowing saving during splashscreen
Posted: Mon Sep 03, 2018 8:13 pm
by Imperf3kt
Remix wrote: ↑Mon Sep 03, 2018 3:08 pm
My version uses that (which incidentally runs in the same context as main menu so does not allow saves/right click)
then jumping out of context (to allow saves etc)
in the prologue label (which then sets the persistent so you can access main menu without before_main_menu doing its thing again)
Seems a logical way to approach the problem.
Which is what I assumed the main_menu label existed for, but apparently not.
Is that just an oversight I made, or is it an error in the documentation, do you think?