y.v.
patreon
Devlog - 22nd November - Code Adaption V2.00 Progressing...
🕑 Added 2024-11-22 08:57:54 +0000 UTCHi,
after the all-out upgrade of the OS, toolchain code and SDK things are looking good technically.
SJX runs nicely with the new Renpy Version in full 1.50 scope
First 2.00 design changes (combat particle effects, dynamic data loading, save game vetting, ...) work nicely
Most important: I can see now a path to have save game compatible loads from 2.00 going forward. How would it work from 2.00+:
while you (a) are playing "within" your version, you can save and load anywhere as usual
when you (b) fire up a new version and load a game of the previous version, the game detects, whether if the save game is from a designated "safe zone", updates all data and in theory continues merrily on its way
The designated "safe zone" inside the game code will be the "DAY X" intermission screens.
I'll start to tackle the major sandbox process flow changes needed for that from tomorrow. Luckily I have a CM system (git) installed now and can experiment on a safe code branch (thanks to nullvoid, Skiant and A.Ch.Vago for the suggestions to use git or some kind of professional CM...).
Goal is to have a stable version 2.00 end of December for VIP / Beta testers, one / two weeks later for Upper Tier and Official Patrons (new architecture and of course some new NSFW of course).
Then I'll use that 2.00 and release the Full Khelara Drengar Update as compatible upgrade 2.10 in spring (hopefully stress testing the save game compatibility to 2.00).
TLDR:
From Version 2.00 onwards, SJX may become save game compatible for usual upgrades (new items, new locations, new cutscenes, ...)
Development continues, break will be postponed after 2.00 is out Mid January
That was a bit technical, but let me know what you think.
y.v.
Comments
y.v.
I definitely have to balance that. For example when implementing major restructuring of skill/training I would not resolve that. Its more intended for an option to update items, locations, quests which would enable me to release intermediate save game compatible versions with new content. Also, as the new architecture demands that "migration saves" are from a designated game zone on top code level (DAY X Screen) I could happily exchange whole minigames in a compatible way (hopefully)
Piotr Sulecki
Please make sure to keep a lid on the vetting work. It's fine for small changes, but if you changed a significant mechanics in-game, don't waste your time implementing a translation from the old mechanics to the new one, just display a warning and ask the user to start a new game.
Tansi
Sounds good. Make sure you do not overload yourself though.
Donniels
Great, you are machine. Looking forward to 2.0 then
