Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
it stilll needs testing and more work however so they recommend quitting the game right after viewing legends mode so you don't corrupt your save. But the functional is there
I just wanted to post what I've discovered for people who just be trying to dip their toes in, or who might not want to use big mods.
Instead, load the newly created second timeline, retire from that, and presumably keep that timeline around as a reference copy. Once you retire that fortress instance, it'll always allow you to launch Legends mode on loading it.
Also, you can have two separate instances of Dwarf Fortress running at any time with no performance impact (multicore CPUs are handy), just go to Steam\steamapps\common\Dwarf Fortress and click on Dwarf Fortress.exe instead of launching it through Steam.
So you can have your fortress running (though probably might want to pause, or set up relevant alerts to cause a pause) while you check Legends in another process window.
Thanks for the heads-up, will have to check what exactly is going on, I did use that method to make a Legends save for my ongoing playthrough. Not sure why I don't remember it screwing up the active save.
Yeah, that's why I posted my findings here.
This extra process normally shouldn't be needed (other than for organising your saves), but due to the bug that's overwriting timelines instead of producing new ones, you've gotta be a bit careful.
In this case, what seems to work is simply renaming your saves (I think something is broken in what should be telling the game to advance the numbers of each timeline save, so instead, it's just overwriting the first one over and over).
This does mean that you cannot view a current, updated version of legends mode until the fortress is retired however.
Yeah, and some people might prefer to do that, but the point of this is that by the end of this process, you have 2 save "regions" or "worlds" for one setting. So all you have to do when you wanna look at legends is save and exit your game like normal, then open legends in the other save.
The point is that after messing with files once you create your world, you don't ever have to again for that world, so this method is more convenient for a long term world.
(Also, a neat bonus is that: if you start a game, you can open up a second instance of DF by force running with admin privileges, and then in the second DF, you can open up your legends save for that world. So you can browse legends while you're playing. I use it to create cool artefacts, or names, or symbols, based on my people's history).
The process seems complex in my little guide but it's really just:
-Start fort
-Save retired fort to new Timeline
-Rename file to "Legends/Active" to prevent overwriting bug
-Repeat x2
Then you have 2 saves you can use more intuitively than always messing with files.