|
|
Also, I'd like a "save" (in addition to the "save & quit") button. Ironman only needs to ensure no reloading and that on quitting the game is saved, it doesn't need to prevent saving, for instance when you want to create a file to post with an error report ;). It can still save over the appropriate Ironman_1.sav (or whatever), but having to quit to the menu and them hit quick load every time I want to ensure my pogress is secured, or need to create a file for these error reports, is needless extra effort.
If there are any concerns with abuse of the "save" button, please realize you can easily save and quit, then quickload, then alt-f4 if things go badly and reload you snapshot. Ironman is already a feature that requires the player to play along with, so the extra convenience doesn't detract from the intent. |
|
|
|
Thanks!
* Directly after a combat is won or lost, ironman now autosaves. This should prevent any exploits with being able to work around the ironman restrictions, but please do let us know if you find any more! |
|
|
|
I assume exploits like save & quit, copy file as Ironman_2.save (or whatever is next) then copying it back (or loading the other file) if things go badly, and/or saving before doing something crazy and then hitting alt-f4 (or the unix/mac equivalents) when things start going poorly, but before combat actually ends, aren't being included in that "if you find any more", right? :) |
|
|
|
Yeah, stuff like that is kind of always going to be a thing, really. There are a few ways that we can get around that that we've tried in past games (Valley 2, I think?), but doing that sort of thing means that there is a nontrivial risk of the entire savegame becoming "invalid to load" because of time offsets if the game doesn't shut down well, etc. |
|
