Currently, every time the resource string references are updates the IDS numbers are shuffled a little. This means that e.g. save-game data about which rumors have already been read isn't behaving as intended. Save-game data that uses CRC values based on (unique) nicknames is not affected by this.
We need to come up with a method to keep the IDS references consistent while keeping them unique. One means here could be to add an extra unique string in the .ini that the adjusted parser would look for and understand what to do with (somewhat like how the Vanilla mBases.ini has deprecated lines that were used to set up the knowDB).
Work on this may be combinable with tackling issue #662
Currently, every time the resource string references are updates the IDS numbers are shuffled a little. This means that e.g. save-game data about which rumors have already been read isn't behaving as intended. Save-game data that uses CRC values based on (unique) nicknames is not affected by this.
We need to come up with a method to keep the IDS references consistent while keeping them unique. One means here could be to add an extra unique string in the .ini that the adjusted parser would look for and understand what to do with (somewhat like how the Vanilla mBases.ini has deprecated lines that were used to set up the knowDB).
Work on this may be combinable with tackling issue #662