Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Iados]

Currently, every time you select "Save Game", it closes the game.

Why not splitting the option? "Save game and continue" and "Save game and exit". No longer the need to return to the main menu every single time you want to save!

[NW_Kohaku]

That's because you aren't supposed to be "saving the game" as a backup, usually.

It happens just because the game is buggy and such, and so sometimes you really do need to reload a save because of a crash or severely undesirable performance, but you aren't meant to be reloading the game just because a dwarf died.

In the tradition of Roguelikes, you are meant to have permanent death, not a "savescumming" method of just reloading until you get through some slim odds through dumb luck.  (Of course, playing more than one game, where you rely upon knowledge you gained in the last playthrough isn't much different from a really far-distant savescum, but whatever.)

[blue sam3]

That's because you aren't supposed to be "saving the game" as a backup, usually.

It happens just because the game is buggy and such, and so sometimes you really do need to reload a save because of a crash or severely undesirable performance, but you aren't meant to be reloading the game just because a dwarf died.

In the tradition of Roguelikes, you are meant to have permanent death, not a "savescumming" method of just reloading until you get through some slim odds through dumb luck.  (Of course, playing more than one game, where you rely upon knowledge you gained in the last playthrough isn't much different from a really far-distant savescum, but whatever.)

Saving without exiting doesn't effect that. Exiting without saving does, but not vice-versa. It is identical to saving to menu then starting playing again, but faster.

[Patchy]

The save function is done the way it is to act as a deterrant to save scumming. It doesn't prevent it, and it's not supposed too, just discourage it. It is merely relying on human laziness to work.

[sockless]

That's sort of what autosave is for, so if your game crashes, you have something to fall back on.
The only reason that you would save and not exit is if you are about to do something that you might want to reload from before it happens. That's not in the ethos of the game.

[Asteranx]

The only reason that you would save and not exit is if you are about to do something that you might want to reload from before it happens. That's not in the ethos of the game.

I would disagree.  If you're plagued by frequent crashes for whatever reason, you'd logically want to save your progress equally if not more frequently.  The 'ethos' of the game is to be a consistent world where what you do stays done.  Having crashes set you back goes against that just as much as being able to 'undo' things by save scumming.

Call it insurance against potential instability.  It certainly wouldn't let you do anything you can't already do.

Like blue sam3 said, the suggestion is for saving without exiting.  You can actually already accomplish this by exiting (which also saves), then restarting.  Same net effect, Iados is just looking for a more automated/streamlined way of doing it, which wouldn't involve the long load times you get on larger fortresses, and could therefore be done frequently if you're worried about your stability.

[tolkafox]

Seasonal saves. It saves every season, if you need to save more than that then you have a problem that won't be fixed by the above suggestion. That's an instability that's not caused by the game but by your computer.

I've crashed once back in 31.16, fortunately for me it was only two months after spring. I redesignated the walls for my outside parameter and went about business as usual.