spelling corrections in #4617 can crash the game with popup "Failed to parse wrf/multires.wrf" #4639
Comments
Forgon uploaded file popup displaying warning message "Failed to parse wrf/multires.wrf" |
Forgon uploaded file logfile containing error messages |
Forgon uploaded file bash script that can fix the problem |
Berserk Cyborg uploaded file |
Berserk Cyborg changed blocking which not transferred by tractive |
Berserk Cyborg changed blockedby which not transferred by tractive |
Berserk Cyborg commented Have not tested the above, will do so later. I also used this as an opportunity to remove that resolution patch and fix trailing white-spaces and the super pulse laser research item for NullBot. |
Berserk Cyborg changed status from |
Berserk Cyborg changed owner from `` to |
Berserk Cyborg changed resolution from `` to |
Berserk Cyborg committed [52] In Warzone2100/warzone2100@52db941:
|
resolution_fixed
type_bug
| by ForgonTicket #4617 (implemented in commit '2ce9492056d84846a07174770cfc2c46abf44e7b') corrected the string 'Incenediary' to 'Incendiary' in the following files:
This affects Incendiary Mortar and Incendiary Howitzer, whose misspelled mentioning in old files, e.g. savegames and mods, can cause the game to crash with a popup displaying a message 'Failed to parse wrf/multires.wrf' (see attached image [raw-attachment:popup.png]) and error messages similar to:
The problem can easily be fixed by correctly spelling 'Incenediary'. Linux users can use the attached bash script [raw-attachment:fix_spellings], which can be used in the following ways:
./fix_spellings [file]
-- backs up 'file' and corrects spelling within it./fix_spellings [directory]
-- backs up 'directory' and corrects spelling within it./fix_spellings [archive.zip]
-- backs up 'archive.zip', extracts its files into new directory 'archive', corrects spelling within that directory, recreates zip archive 'archive.zip' and removes new directory 'archive'./fix_spellings [archive.wz]
-- analogous to procedure above, since '.wz' files are '.zip' filesIssue migrated from trac:4639 at 2022-04-16 12:54:57 -0700
The text was updated successfully, but these errors were encountered: