Well I'm disciplined enough to stop myself from copying savefiles. In Pillars of Eternity I once lost 40 hours of progress because I lost a fight despite the fact that alt-f4 would have saved the file from deletion.
IronMan needs more save options.
- Thread starter DoomBlackDragon
- Start date
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Does not work.
Ironman games must go to the Steam Cloud. And it is protected agaisnt these kinds of modifications. All the server has to store is a single checksum per game and thus be able to detect such modification. Trivial data demands.
This hasn't been true of EU4 for quite some time, and is certainly not currently true of Stellaris.
I don't want to add to the "ironman achievement " drama but I like the current system.
Although I do agree with the OP in that auto saves can easily be increased to once every 3-6 months for the sake late game performance
Although I do agree with the OP in that auto saves can easily be increased to once every 3-6 months for the sake late game performance
CK2 autosaves every 6 months, so I guess there is leeway in adjusting the frequency to make it a longer then monthly.
I CK2 Archievements are locked out if you used the Start Designer.
It would be a heck of a lot easier to cheat/shortrack stuff via the Editor then via Ironman mode.
The whole gameflow is a lot slower, so longer save intervalls are less of an issue.
Don't use the Steam Cloud because it lags as fuck. Use local save and your problem is solved.
Also, the frequent save is to prevent cheating, just play the normal mode if you will not cheat anyway.
Also, the frequent save is to prevent cheating, just play the normal mode if you will not cheat anyway.
Steamcloud saves to the disk, from where it is synched into the cloud.
The synching is only done when the game is closed or started.
The issue with spreading saves out in ironman is that anybody will find reasons to savescum, especially in a game where a random quirk of the RNG can royally screw somebody, potentially unfairly. So with that in mind, I think saves should be spread only a tad bit farther apart. Maybe by four months? Also, something needs to be done about the immense number of ships you acquire in the late game. As cool as it is, we don't need fleets of 1000 battleships if it's going to make our framerate resemble the melody of Sweet Dreams (are made of these).
That is not a mater of Ironman or Archievements. That is a mater of general performance.
And oddly the only arguments for a longer save intervall thus far was performance too.
Almost as if people try to de-hardify ironman using the Performance Argument.
Or as if people associate a general performance problem to be a Ironman problem.
In what possible way having longer auto-save intervals makes ironman less hard?
Really, you need this explained, it's such a basic point I'm not even sure where to start... so I guess at the begining.
Saves scumming is the act of reverting to a prior game save, this lets you act again but aware of the arch of the game so you can react to problems before they happen and undo significant mistakes and miscalculations after you've learned they are miscalculations. In fact, the further you go back, the more knowledge you can bring to bear against a problem and the greater an impact you can have.
As, I hope you're aware, the current Iron Man mode automatically creates a save at every month. So this limits save scumming to being something that can only occur within a 30 day timeframe. This minimizes the impact of this practice to preparations that take less than 30 days, in this game that's very little, and mistakes that become apparent within 30 days, that's maybe a missed click but is rarely an ill conceived war or diplomatic arrangement.
Anyway, I hope that helps, if you feel any more basic game concepts and strategies are confusing, do feel free to ask.
And removing my tongue from my cheek for a moment. There is an important debate to have here. Does the monthly ironman auto-save hinder game performance for enough players to justify a lessening of the iron man requirements? Can the performance issues be addressed without changing the save requirements? To what extent will the Ironman experience be affected by a lessening of the time save restrictions. But you'll never be a part of that debate if you continue this repugnant rhetorical strategy where you challenge established premises and drown out or derail productive conversation. Seriously, be better.
Last edited:
As i've said before, you can make backup copies of your save at any time and in any quantities. You can load saves from 3 month ago, 6 month ago, year ago and so on.
Having longer auto-save intervals doesn't change anything.
So if you find the thought of someone save scumming so terrifying that you're willing to suffer monthly freezes just to stop them from doing so, well, monthly auto-save doesn't make save scumming any harder.
Please do. And keep it that way for the rest of this conversation if you may.
Yes.
No.
By not having game become unresponsive at the beginning of each month.
My tongue and cheek know a love that can not be bound by your mortal laws. Or good taste.
Brilliant. So by going outside the program to do something the developers did not intend you can get around existing mechanics. Hey, I got a hot tip for you... if you disagree with the game's current design philosophy on fleet maintenance costs you can use the ` key on your keyboard to bring up a console and then the resource_energy command to give yourself as much energy as you think is fair.
However, that fact has as much of a place in a discussion about fleet maintenance cost as YOUR brilliant plan has in a discussion about Iron Man mode.
First off, what's with the middleschooler taunts? I take some small comfort in that you're bad at them, but that you tried to make this about me being 'chicken' at all is just sad. You couldn't even muster up a "bawk bawk" sound? That would have at least been entertaining.
Secondly, you have not established this occurs in more than edge cases, let alone enough to even think it's happening to me.
Thirdly, you haven't established that loosening the restrictions on Iron Man is the only way to resolve it, let alone the best way to resolve this freezing.
Fourthly, your genius plan is to pause the game every 3-4 months, alt tab out, find the save file in your program, copy it to a storage folder, then if you need to go back, presumably you'd close the game out entirely, paste the file into the program, reload it and then you will have save scummed. There is no way a sane person says that's not harder than simply clicking reload from inside the game UI.
Fifthly, I'm not even sure this actually works. Founder's pretty up on game mechanics and he's saying it doesn't, meanwhile you needed me to explain how save scumming makes the game easier.
Finally, nice work. You said something that was on point and contributed to the discussion. You're on your way to a solid C-.
These questions were meant to serve as staging points for actual debate. You were supposed to see these, present your position and then make arguments in favor of those positions. I'm afraid I might need to revoke that C- sport, this assignment is woefully incomplete.
Last edited:
I just did some tests. You can copy the file - could even make a copy in the steam cloud folder ([Steam Programm Folder]\userdata\86628553\281990\remote\save games\). The game will just ignore anything not named "ironman.sav" in the folder.
You can not restore a previous savegame while stellaris is running. That will trip up the game in most cases. But while it is offline it is possible.
Apparently thier savescum protecton needs an upgrade.
Reacting the to write event would be easy enough. I have .NET code for that among my "often cited programming links".
Of course then you end up double the diskload for each save you "back up" (you have to make a copy of hte files once it is written).
The files are easily 1 MiB in size, so not likely to cause an issues even if you store the last 100. But managing the whole shinding would be kind of annoying even with a dedicated programm to do the copy/backup operation.
Oh, that's.. neat?
Honestly, I can't imagine alot of people are going to those lengths just to get an edge on achievement farming but I am glad to know the plan being presented is viable. I'd have felt terrible for Deep Space Explorer if it wasn't.
Honestly, I can't imagine alot of people are going to those lengths just to get an edge on achievement farming but I am glad to know the plan being presented is viable. I'd have felt terrible for Deep Space Explorer if it wasn't.
A, Founder beat me to it. Just run a non-cloud ironman match. If you think you're making an important choice and unsure of the results, just make a copy. I'm not sure why people are achievement hunting. I normally like Ironman matches so that I have to say "oh well" and live with the choice.
While this is all going on, can I just ask for the following:
A warning message/popup window that tells you that achievements are currently disabled due to any active mods whenever you start/load into an iron man game.
Happens quite often, that I start the game in order to play my ironman-save and still have mods enabled from a previous mp-game with my friends.
A warning message/popup window that tells you that achievements are currently disabled due to any active mods whenever you start/load into an iron man game.
Happens quite often, that I start the game in order to play my ironman-save and still have mods enabled from a previous mp-game with my friends.
There are too many elitest in this thread.
Saving is annoying and, no matter what, will freeze the game. That is unavoidable as it needs a quick period as to actually save the game and can't both run it and save it at the same time.
A month can last from 10 to 20 seconds (on fastest), the actual save lasting from 0.5 to 2 seconds.
(12x10)-(12x0.5)=114 seconds, 6 seconds saving.
10 years, (120x10)-(6x10)=1,140 seconds, 60 seconds saving.
It is small but there is one problem: we don't perceive it by the actual time it takes up but by how often it occurs (10-20 seconds intervals). For an example:
You get hit by a spoon every 10 seconds, it doesn't really hurt but is just a minor annoyance. This goes on for 10 minutes and you start to get annoyed. An hour and you get angry and try to find a way to stop the hitting. A day and you start to become frustrated as you can't find a way to stop it. A year and you become insane and quit life.
Saving is annoying and, no matter what, will freeze the game. That is unavoidable as it needs a quick period as to actually save the game and can't both run it and save it at the same time.
A month can last from 10 to 20 seconds (on fastest), the actual save lasting from 0.5 to 2 seconds.
(12x10)-(12x0.5)=114 seconds, 6 seconds saving.
10 years, (120x10)-(6x10)=1,140 seconds, 60 seconds saving.
It is small but there is one problem: we don't perceive it by the actual time it takes up but by how often it occurs (10-20 seconds intervals). For an example:
You get hit by a spoon every 10 seconds, it doesn't really hurt but is just a minor annoyance. This goes on for 10 minutes and you start to get annoyed. An hour and you get angry and try to find a way to stop the hitting. A day and you start to become frustrated as you can't find a way to stop it. A year and you become insane and quit life.