D
Dr PinkCake
Guest
Guest
Hi!
I've been experimenting with multi persistent files when it comes to saving games between releases. My intention is to reduce the size of the binaries by saving a multi persistent file with all variables that I need for in the new release.
I have gotten it to work, but I feel that it's kind of clunky; especially if the player is playing multiple playthroughs at once.
This is my current approach:
1. The player plays until the end of the Episode.
2. The player gets a prompt that asks if he wants the current game to be set as start for the next episode. If 'Yes' -> mp.save() #Multi persistent file is saved
3. In the next episode with a new binary, click Start game and continue playing.
However, if the player wants to play the game in two different ways (or three which is how my game was designed to be played) he must also do the following:
4. In the new episode, save your game. So you can continue playing later.
5. Go back to the previous episode and play until the end. Repeat steps 2. and 3.
I'd rather have the approach that let's the player just save their games as usual (right-click/save) and then load their saved games in the next episode. But this doesn't natively work.
Since there are a lot of experienced devs here, I was wondering if anyone has any valuable pointers or insight on this subject?
I've been experimenting with multi persistent files when it comes to saving games between releases. My intention is to reduce the size of the binaries by saving a multi persistent file with all variables that I need for in the new release.
I have gotten it to work, but I feel that it's kind of clunky; especially if the player is playing multiple playthroughs at once.
This is my current approach:
1. The player plays until the end of the Episode.
2. The player gets a prompt that asks if he wants the current game to be set as start for the next episode. If 'Yes' -> mp.save() #Multi persistent file is saved
3. In the next episode with a new binary, click Start game and continue playing.
However, if the player wants to play the game in two different ways (or three which is how my game was designed to be played) he must also do the following:
4. In the new episode, save your game. So you can continue playing later.
5. Go back to the previous episode and play until the end. Repeat steps 2. and 3.
I'd rather have the approach that let's the player just save their games as usual (right-click/save) and then load their saved games in the next episode. But this doesn't natively work.
Since there are a lot of experienced devs here, I was wondering if anyone has any valuable pointers or insight on this subject?