1.2b (May 05, 2023)
=====================
Updated to be compatible with Starsector 0.96a
1.2 (July 12, 2022)
=====================
Updated to be compatible with Starsector 0.95.1a
Added the following to saves/common/config/lw_autosave_settings.json.data:
- "forceSaveAfterMapChange", forces a save after every hyperspace jump
- "saveAsCopy", if enabled, every autosave creates a new save
Removed autosave_settings.json.default as it was confusing new players
Updated config loading logic to autopopulate any missing entries
Updated autosave to use API's cmdSave() instead of simulating keypresses
1.1c (March 26, 2021)
=======================
Updated to be compatible with Starsector 0.95a
Renamed generated settings file to saves/common/lw_autosave_settings.json.data
(Old settings file will be removed if present)
1.1b (August 28, 2020)
========================
Moved version file hosting to GitHub
1.1 (November 16, 2018)
=========================
Updated to be compatible with Starsector 0.9a
This mod now requires LazyLib 2.4b or later
Settings are now stored in saves/common/autosave_settings.json.data
- This file will only exist after launching the mod at least once
1.0f (April 21, 2017)
=======================
Updated to be compatible with Starsector 0.8a
1.0e (March 16, 2017)
=======================
Switched version file hosting to Bitbucket
1.0d (November 19, 2015)
==========================
Fixed issue where simulated quicksave key presses weren't always registering
1.0c (November 19, 2015)
==========================
Updated to be compatible with Starsector 0.7a
1.0b (December 08, 2014)
==========================
Added "minutesBetweenSubsequentWarnings" setting to autosave_settings.json
Fixed bug where the mod started spamming sector messages after a failed autosave
1.0 (December 08, 2014)
=========================
Initial release:
- By default, warns when you haven't saved in a while, and tells you how many
battles and market transactions have occurred since the last save
- Player can enable autosaves in autosave_settings.json, can autosave if enough
time has passed since the last save, or set it to force a save after every
battle or market transaction
1.1 (November 16, 2018)
=========================
Updated to be compatible with Starsector 0.9a
This mod now requires LazyLib 2.4b or later
Settings are now stored in saves/common/autosave_settings.json.data
- This file will only exist after launching the mod at least once
May I repost this on fossic.org? With some strings translated.
Any chance of a new feature being added? Specifically, using save copy instead of overwriting the save?
Global.getSector().getCampaignUI().cmdSave();
Global.getSector().getCampaignUI().cmdSaveCopy();
Nice mod. Would like to add that the saving can be done now without needing to emulate keypresses.perhaps contribute on this mod github (https://github.com/LazyWizard/autosave) would be a better option for that
Saving:CodeGlobal.getSector().getCampaignUI().cmdSave();
Save Copy:CodeGlobal.getSector().getCampaignUI().cmdSaveCopy();
Not a knock on your mod, of course. I'm still learning more about the modding API and figured I'd share a discovery. :)
autosaving is disabled by default because save times can become extremely long with many mods enabled
I really need this mod but when I try to start the game it crashes and I get this error message. I've tried starting with the settings untouched and with the settings changed but it doesn't make any difference.
42293 [Thread-3] ERROR com.fs.starfarer.combat.CombatMain - org.json.JSONException: JSONObject["forceSaveAfterPlayerBattles"] is not a Boolean.
I really need this mod but when I try to start the game it crashes and I get this error message. I've tried starting with the settings untouched and with the settings changed but it doesn't make any difference.How to fix that?
in \Fractal Softworks\Starsector\saves\common\config\lw_autosave_settings.json.data,I really need this mod but when I try to start the game it crashes and I get this error message. I've tried starting with the settings untouched and with the settings changed but it doesn't make any difference.How to fix that?
1.2 (July 12, 2022)
=====================
Updated to be compatible with Starsector 0.95.1a
Added the following to saves/common/config/lw_autosave_settings.json.data:
- "forceSaveAfterMapChange", forces a save after every hyperspace jump
- "saveAsCopy", if enabled, every autosave creates a new save
Removed autosave_settings.json.default as it was confusing new players
Updated config loading logic to autopopulate any missing entries
Updated autosave to use API's cmdSave() instead of simulating keypresses
Can there be an option to autosave _before_ starting a battle, or going into one? like, if an enemy fleet that is pursuing is like 10 pixels away from your fleet then autosave pre emptively? so its easier to just reload a save and restart a battle which idk how to do any other way.
Version 1.2 is up, get it here (https://github.com/LazyWizard/autosave/releases/download/1.2/Autosave.1.2.zip) (mirror (https://www.mediafire.com/file/r3zesjfrckuu4ux/Autosave_1.2.zip/file)). Still requires LazyLib (https://fractalsoftworks.com/forum/index.php?topic=5444.0).
Changelog:Quote1.2 (July 12, 2022)
=====================
Updated to be compatible with Starsector 0.95.1a
Added the following to saves/common/config/lw_autosave_settings.json.data:
- "forceSaveAfterMapChange", forces a save after every hyperspace jump
- "saveAsCopy", if enabled, every autosave creates a new save
Removed autosave_settings.json.default as it was confusing new players
Updated config loading logic to autopopulate any missing entries
Updated autosave to use API's cmdSave() instead of simulating keypressesCan there be an option to autosave _before_ starting a battle, or going into one? like, if an enemy fleet that is pursuing is like 10 pixels away from your fleet then autosave pre emptively? so its easier to just reload a save and restart a battle which idk how to do any other way.
There's no good way to do this, unfortunately, otherwise I'd have added it in this release. Sorry!
I forgot to ask if there's a way to manually install this as to sidestep the mod automatically being disabled for being out of date even if it technically still works.