Print

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

[Devath]

Run Comrades, check in in Bloodrock or your turn is gonna get skipped.

[Dadamh]

Hm, next version will possibly going to break save compatibility.  Kinda sucks but I suppose we'll keep using 40d from now on.

[iluogo]

Ok this means The Eternal halls can live on

[Eita]

Hey, it fixes the bug we currently have.

[iluogo]

It's Dogman's turn so you should PM him

[Dadamh]

Ok, I PMed Dogman.  Hopefully he'll be back here and start his turn again shortly.

[Run Comrades]

sweet!

[Dogman]

RIGHT! Sorry. I didn't notice I was being sent to the third page whenever I typed in the URL for the forums (long story short, I was clicking on the first link in the drop down box, which happened to be a link to the third page of the community games section). I'll start on my turn right now.

[penguinofhonor]

I don't know if people have been talking about this or not:

What happens when saves get broken?

[Dadamh]

We all get depressed and try to find a way to fix it.  So far, that way seems mostly to be either replaying the turn(s) that caused the bug, or waiting for Toady to have a fix in a new version.

[Kishmond]

I'm confused, what exactly changed in the savegame compatibility department? It still says saves from 27.169.32a are compatible.

[TheSpaceMan]

It's the NEXT update that will break the compatibility I think. So it should all be ok.

[penguinofhonor]

But it will get broken and it will break the eternity of the fortress. That's not cool.

[Dadamh]

Well, no.  It doesn't stop us playing forever.  Just stops us using the fort with the new versions.

[Run Comrades]

Seeing as how I keep several "back issues" of DF, it certainly won't be hard for me to open a slightly dusty folder once in a while to play this fort