Upgrade from 3.0.6 to 3.2.0

**Magnate** · June 14, 2011, 13:24

Originally posted by arturolorioli

First thing, the warmest hello to all the forum members and thanks for all the much interesting material you have posted.

I'va played Angband for several years, using an old 3.0.6 version. After a lapse of almost 2 years I started again to play, searched for new versions and found the 3.2.0.

But unfortunately the 3.2.0 version doesn't seems able to load my Level 47 character. Is some sort of upgrade necessary to play 3.2.0 with 3.0.6 characters? Or is it impossible? Or is it very simple, and I am just doing something wrong?

Thanks in advance for the assistance, and happy gaming

Arturo Filippo Lorioli
(Roma - Italy)

Welcome. I'm afraid I have bad news for you: there was a break in savefile compatibility in between 3.0.6 and 3.2.0. Possibly more than one, in fact. This means you cannot convert that savefile to 3.2.0, and need to finish your game in an older version (I think 3.0.8 or 3.0.9 may work but not sure).

The good news is that this won't happen in future. Savegames from 3.1.1 onwards should load correctly into any future version ...

**jens** · June 14, 2011, 14:04

Until 4.0 that is ;-)

**Timo Pietilä** · June 14, 2011, 14:18

Originally posted by Magnate

Welcome. I'm afraid I have bad news for you: there was a break in savefile compatibility in between 3.0.6 and 3.2.0. Possibly more than one, in fact. This means you cannot convert that savefile to 3.2.0, and need to finish your game in an older version (I think 3.0.8 or 3.0.9 may work but not sure).

The good news is that this won't happen in future. Savegames from 3.1.1 onwards should load correctly into any future version ...

Between 3.2 and 3.<something-development> has change in PVAL -handling (multiple PVAL:s). I suspect that that again broke the savefile compatibility. I also guess that removing special artifacts completely causes havoc if you already have one and its base item gets removed.

**Magnate** · June 14, 2011, 15:41

Originally posted by Timo Pietilä

Between 3.2 and 3.<something-development> has change in PVAL -handling (multiple PVAL:s). I suspect that that again broke the savefile compatibility. I also guess that removing special artifacts completely causes havoc if you already have one and its base item gets removed.

Dealing with those in reverse order:

- as long as the base object exists in object.txt, the fact that it can no longer be generated is fine. Commenting out the base items would cause a crash, but it's perfectly safe to leave them in and simply not create any artifacts based on them.

- quite a lot of work has gone in to making sure that old savefiles from before multiple pvals will work properly in new versions. Once 3.3.0 comes out, I'll be looking very carefully at any bugs reported on this - and there *will* be a 3.3.1 which will fix them.

**Timo Pietilä** · June 14, 2011, 16:03

Originally posted by Magnate

Dealing with those in reverse order:

- as long as the base object exists in object.txt, the fact that it can no longer be generated is fine. Commenting out the base items would cause a crash, but it's perfectly safe to leave them in and simply not create any artifacts based on them.

That leaves unknown flavors in knowledge menu forever if you don't solve that in some other way. Maybe check which INSTA_ART items can be actually generated?

**Magnate** · June 14, 2011, 16:06

Originally posted by Timo Pietilä

That leaves unknown flavors in knowledge menu forever if you don't solve that in some other way. Maybe check which INSTA_ART items can be actually generated?

Yes - good suggestion.

**arturolorioli** · June 14, 2011, 19:20

Originally posted by Magnate

Welcome. I'm afraid I have bad news for you: there was a break in savefile compatibility in between 3.0.6 and 3.2.0....

Oh well, things that happen ... I suppose it's the price of progress

Thanks for the prompt and helpfull answer.

Arturo Filippo Lorioli
(Roma - Italy)