I have only one reproach, you shouldn't use fixed day for the main story events. Between the other characters, the jobs to buy some goods, and the different activities to build stats, there's occupations for way more days than the actual 32 covered by the story.
I know that you warn us to save at the end of the story, and that initially the game intend isn't multi-romance, but still it seem better to me if you use two counters (one for the day events, and one for the night events), or just one for both, up to you of course, then use something like this for the story branching :
Code:
default storyDayCounter = 0
label Class_Story_Events:
if storyDayCounter == 0 and day >= 3:
call Scene2 from _call_Scene2
$ storyDayCounter += 1
elif storyDayCounter == 1 and day >= 5:
call Scene4 from _call_Scene4
$ storyDayCounter += 1
elif storyDayCounter == 2 and day >= 8:
call Scene6 from _call_Scene6
$ storyDayCounter += 1
[...]
This way, even those who forgot to save, or overwrote the save by error, while be able to continue the story.
And to not mess with those who use a save file at the right day, add something like this :
Code:
label version_fixer:
[what's already in the label]
if version >= 4 and storyDayCounter == 0:
if day == 3:
$ storyDayCounter = 1
elif day == 5:
$ storyDayCounter = 2
[...]
This way, those who saved at the last story point they see will have storyDayCounter set at the right value. Those who start a new game will not be bothered. And those who forgot to save or overwrote their save will have to replay the events, but also see the ones they should have missed otherwise. Like you don't change variables values in the story scenes, it'll have no incidence on the game itself, but it will please them.
