Print

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

[Unshaven]

Has their been any word on if the next version will be compatible with our saved games from 0.31.03 ?

Not a huge deal if it isn't just curious mostly.

[Jay]

40dX saves were compatible with 40d saves.
Thus-
They should be, but we'll see.

[Knight Otu]

40dX saves were compatible with 40d saves.
Thus-
They should be, but we'll see.

Yep, ideally, save-breaking shouldn't happen in the near future. Bug fixes might cause problems in that area, though, so it isn't 100% guaranteed.

[Unshaven]

That's good news.

[Quatch]

Except, 31.04 (the merge version), includes a lot of changes that might have changed values in the raws. people have been reporting that updating the raws only works if they have not been re-ordered (smelting iron requires 3 copper bars and other randomness).

So it will likely work, but no guarantee until it is tried.

[hermes]

Except, 31.04 (the merge version), includes a lot of changes that might have changed values in the raws. people have been reporting that updating the raws only works if they have not been re-ordered (smelting iron requires 3 copper bars and other randomness).

So it will likely work, but no guarantee until it is tried.

Hmm this is something that has been confusing me a little...  could anyone clarify for me...

I've read that the raws have to brought across with the save files, so does this mean that the game copies and changes the raws from their vanilla state itself when it's running?
If this is the case, and if the raws ever need updating, wouldn't this break save compatibility every time?

I'm sure I've got the wrong end of some stick on this though.

[Cruxador]

Except, 31.04 (the merge version), includes a lot of changes that might have changed values in the raws. people have been reporting that updating the raws only works if they have not been re-ordered (smelting iron requires 3 copper bars and other randomness).

So it will likely work, but no guarantee until it is tried.

Hmm this is something that has been confusing me a little...  could anyone clarify for me...

I've read that the raws have to brought across with the save files, so does this mean that the game copies and changes the raws from their vanilla state itself when it's running?
If this is the case, and if the raws ever need updating, wouldn't this break save compatibility every time?

I'm sure I've got the wrong end of some stick on this though.

No, the raws for a world stay unchanged. He'd probably just forgotten about that.

[Unshaven]

So what I gather from the conversation is that the save games will likely be compatible but some saves may become unstable due to bugs.

[Xinael]

Your saves keep a copy of their raw files now (take a look in one of the folders in \dwarf fortress\data\save\ - you'll see a folder in there called raw with a copy of them). I'm guessing the point of this is so you can have different raw mods for different saves, and that changing something in one save (or even in the main \dwarf fortress\raw\) won't affect existing saves. It'd also make it easier to share your saves with other people without wrecking any other games they've got going on.

So this might mean that even after an update that changes the raw files, your saves will still work fine, because they'll use the raw files kept with the save itself. Of course it might also mean that the game could look for something that's been added to the raws in the new version and wouldn't be able to find it because your raws are from the old version, which would probably cause problems.

I guess my answer is maybe?

[czolus]

As its an alpha, things may change that break save compatibility with little-to-no warning.  But he hasn't explicitly stated that save compatibility will be broken for 0.31.04.

[Quatch]

He has now explicitly stated (in case you missed that dev log update) that saves are compatible, so I am hoping this involves checking for obvious bugs as well as a lack of save-breaking-changes.