If it's solely the change to the iron shattering thing that makes old save games incompatible, could you make the iron shattering part an optional install, so that we can get all those bug fixes without having to start over?
No, that won't work either. The main differences that make savegames incompatible are two-fold. Firstly, the file BrokArmr.ITM has been removed because an identical one exists in MISC57.ITM. This will cause savegames in which ANY piece of armor has shattered to crash, either when you load the game, or when you go into an area where you dropped the broken piece of armor, due to the missing resource. Secondly, the shield shattering component adds an extra string in the middle of all the StrRefs that are added to dialog.tlk. This causes what I call 'StringShift' in which all the dialogue strings after this extra string are incremented by one StrRef number, screwing up all references after that. The effect isn't actually that bad (game-stopping), but all your journal entries have a major chance of being screwed up because this extra string is patched early in the installation. Making the shattering optional will not work because I would have to ensure the integrity of the other strings related to shattering weapons and armour, which simply is a downgrading of coding and messes things up entirely.
I should also add that some of the typo fixes made in the .tp2 file may cause
WeiDU to append strings to dialog.tlk a little differently than before, which could also screw up savegames.
Finally, I should say that if a piece of armor has not shattered, then all you are going to see in a previous savegame is screwed up journal entries, and possibly wonky worldmap names, and if you don't mind these, then I say 'go with your heart's delight and play your old savegame'.
Edited by Ascension64, 17 July 2005 - 06:50 PM.