Home Creators Posts Import Register Favorites Logout
haven't archived this post yet. have a subscription? use the importer!

Downloads

  • Cheat Sheets 0.47.0.35.pdf
  • Windows - Just Friends Closed 0.47.0.35.zip
  • Linux - Just Friends Closed 0.47.0.35.zip

Missing 5 full-res photos, 3 files, as this post has not yet been imported.

Content

So... Here's a new build! 

And with it a lot of new... Features/Issues.

So let's be real here: I ended up finishing the Save system, way earlier than I thought I would thanks to a breakthrough I had. However, with the new system, a lot of new issues will arrive for you guys. But wait a second, let me explain:

The idea of reworking the save system came after a new patron a few months ago came to me with a very particular crash. The game was crashing for him in a place the game didn't crash for me. After a lot of deliberation, I asked if he had played the Public build of the game and he said yes. 

Knowing this, I asked if he was loading a save from that build, and positive, he was. The biggest difference apart from content to play through the builds, (and of course not counting that Patreon's closed builds have more content than the public ones), is that the newer builds have a Filter System. I noticed that probably what was happening is that the game wanted a filter, and he loaded a save without filter info, and that somehow crashed his game when the game changed the filter. 

By understanding that, the new save system had to be done, so I added it to the Roadmap, and well we are here now.

It took me two weeks working nonstop to get to a working system, and to remember a few things I had forgotten, some functions have values that can be changed but it seems I forgot to document that so I had to do some tests.

Either way, after that I spent the entire rest of my time checking every single combination of saves, to make sure you would not be able to load a save if you shouldn't, and these are the new rules I ended for this build:

  • You cannot load a save from a newer build into an old build, so for example, if you load the save from this build on the public build (once the public build arrives with the save system on it), the following message will appear:

Of course, I want you to understand, this message only appears after the build 0.47.0.35 which means if you try to load this save on the build 0.35 for example, the game will try to load nonetheless, after all, I can't update older builds. But the idea here is that once we arrive at a public build that has the save system implemented, it won't let you load saves there if they are from newer builds. So, let's say next month you create a save on build 0.38 and you go back to 0.37, you would not be able to load that save. 

  • You cannot load old saves on your new build anymore: Meaning if you come from build 0.35 and try to load that save on Build 0.47.0.35 this message should appear:
  • Finally, you CAN load saves from older builds as long as this save is from a build ONE VERSION only below the current version, meaning you can load a save from 0.47 into 0.48, the save will be updated as soon as you save it again. 
  • However, if you're on Version 0.49 and your save is from 0.47, this message will appear:

And, the final issue: I cannot test this meaning you guys will have to test it: Saves from 0.46 downwards doesn't have the information of what build you're using. My save System checks for that number now, meaning if there's no number saved in your save, the first message will be displayed by the game: Save not compatible. 

This means you cannot load saves from 0.46 on build 0.47. I'm sure of it because that's one of the conditions once you try to load a save: If the build version is more than 3 numbers lower or the build number is null, do not allow the save to load. 

I'm sorry for that guys, but that's how it is, updating the save system would render all older saves incompatible. 

To mitigate that, I created a new Cheat Sheet Updated for version 0.47.0.35, not only that but I want you to remember that: Skip dialogues are saved separately from the normal save of the game. Every time you close your game, the game saves what route you read and how many dialogs you have read. This means even if you delete all your saves manually from the game, you will still be able to skip dialogs, even new dialogs as long as they're on the index of the dialog you've read. 

So you can skip the entire game to the place you were on Wagner or Karnal's route with no problem. With the new Cheat Sheet, you will be able to go through the routes pretty quickly.

However, if possible, please: Play through all routes, including the B, F, and A routes, save before you click on dialogue, and read all of them.  The more you check them, the easier it gets for you to find issues with the dialogues and suggest your corrections. Remember: Accepted suggestions will take your name to a new section of the credits, the Text Revision Team! 

And that's it for this build. Tomorrow or after I will be bringing the new poll for Tier 3+ patrons.

I have added all new patrons to the credits with a few exceptions, but those already know about it, and that's it. I hope you all enjoy this new build. And I'm sorry for the issues, but messing with the save system always causes them.

Files

Previews only

Comments

Sparky85

just a quick queston.. the cheat sheet indicates that Day 4 (5th Day) with Karnal at the pool is implemented. however after going to the pool and meeting Karnal there the game just ends.. is this a bug or is it just not implemented yet in this build?

yekkusu

Thanks for the feedback. To help me figure it out if there's something wrong please click on the suggest correction button and send me the same dialog with a * in it so I can check exactly what dialog is the last one you see before the credits trigger. There's a high probability that during some combing through the texts maybe a route link is not added and the game just thinks the day ended earlier. I will check first thing in the morning and if I find an issue I will fix it and upload a patch build for your all. Again thanks for the feedback.