Bay 12 Games Forum

Thought week isnt over yet, damn, guess lost track of time.
Havent acomplished anything on the turn anyway, everything is either done already or near-impossible to do, and havent learned how to play fortress mode in 5 years of playing DF, so good luck lurkerZ

Also on another copy of the save I've forwarded the clock by a ridiculous amount to the year 1000, and the game appears stable (or at least doesn't crash every few days as reported earlier) I've progressed a month or four without crashes, presumably because whatever causes the crash might have died of old age. Not sure if that will last but I'm out of testing time for today (and will not have further time to test this week)

If you skipped less than 4 months it could not crash just because crashes begin about 3-4 months playing into the save, after 6th hematite. But if it actually works thats narrows it down a little

https://drive.google.com/file/d/1q12T50MrzvvfTBPL07dMajZLdRECMI_f/view?usp=sharing
Saved exacly 1 tick before the disaster. Maybe that will somehow help
EDIT: Maybe, the exact tick it happens. When retired and set timeskip to 0 tick it crashes

Well, it happend again. Now its 7th hematite that causes the crash. dont even know why and how its 7th hematite, considering few days have passed. Luckly we have a solution, but still hope it wont happen again

After testing can say for sure: something bad happens every few days, causing a crash. we can dodge that date with gui/gm-editor df.global, but there should be a long-term solution

Two solutions:

One, if you can get into the game whether that be fortress or adventure mode, 'gui/gm-editor df.global'
Find the current year, and current year tick. Jump them ahead enough to pass the date by some arbitrary amount.

Two, if you are trying to unretire or load the save in anyway where the calender shows up before play, even from the main menu before loading, 'set-timeskip-duration -ticks 0' this will cause no time to pass whatsoever and bypass the specific date crash. Then you can use the first solution to skip time past the date of the crash.

Thank you, that worked!
will post my save in two days, after i finish adventuring.

Notice there's an over 2 month difference between the last save and the one you uploaded. You should use something like

Code: [Select]

set-timeskip-duration
to see if Unraveller's latest save goes beyond that cursed date so you won't risk playing for nothing. Or maybe reclaim one of the NPC forts to play a few months to see there are no issues.

FUn, did exacly that, it does break every time! Wanted to download an unmodified, unfixed save, but it seems like unraveller updated whole google drive file, so i cant find it anywhere in this topic. Ill try earlier save just for a test

Will it let you progress beyond that date in fort mode and then unretire your adventurer?

Tried that, won't work

I suggest trying to use questport to teleport on the farthest part of the map, maybe that jogs something in the save. Maybe it's something in the adventurer's area that break the game.

Sadly forgot to make a backup before i retired, so it is impossible. Also, traveled every way possible, so doubt that. Here is the save:
https://drive.google.com/file/d/15vnSeOx6s3kAz2fYxSODmH963THMeR8k/view?usp=sharing