heya, first off thanks for playing and I'm glad you're enjoying the project. To answer your question, first you need to know that I'm not a coder or game developer in any professional capacity. I went to school for psychology so i'm completely self taught for this based on reading forums and watching videos. I'm still learning in real time-- that's why the quality of the original game changed so much as it progressed. So if there's a way to avoid this issue, I'm not sure how to do it. I'll give you a pretty lengthy but detailed response though-- just know that I probably won't sound like I know what I'm talking about. lol
So "choices" in the game are based on declarations within the code. When the game starts, all known variables and declarations within the game will be loaded. I load all of mine as "false" when you start a New Game. When you make a choice in the game, the variable assigned to that choice then becomes True. Later in the game, if that choice becomes important, the game will remember that the variable is true and your story will follow that "true" path.
The problem and the requirement for starting a New Game after each update is because as the story progressed, I added new variables. So for example, if you played the first Update of Chapter 1, your New Game would not have loaded all the chapter 10 variables yet because that chapter wasn't written yet. The game has to load all variables within the game at the start or it'll crash when that variable becomes required (usually the error message will say something is "not defined.")
One criticism of this is obviously that I could have just loaded all known variables for the entire game when I first started writing the story back in 2017. The problem with that is I wasn't sure where things were going. I'm a fan of the story myself so I didn't want to plan a lot out, I wanted to be surprised along with the reader so the story wrote itself each time. Another problem with that stems from people that are actual coders. Without exception, there's always a segment of readers that break into my code every update (especially in the original version) and looked for spoilers or clues to where the story was going. Hell, I even had a few fans that have never actually played the game-- they download each update and just break into the code script and read that like a novel-- they never even boot the game: just the code. To avoid hackers finding future story spoilers, I just never included any future information-- including those variables that would prevent the game from crashing.
The Fix: So the reason that boot message is there is that during each update, you need to start a New Game. The newest version of the game will load all variables--including the new ones just added into the story when you click New Game. But then immediately following that, you normally will have some choices to answer. Those answers will modify the code to flag things as True and essentially recreate your old save file and choices based on what's required for that update. Then it'll drop you right at the end of the last update with all your old choices.
Hopefully that makes sense. If not, feel free to ask :)