Here's a scenario where this behavior could have unexpected consequences:
- The developer of a mod wants to store game progress externally in an array of 16 entries.
- The mod is released, people play it and have their progress saved in this array, stored as a file on disk.
- The developer then releases an update to the mod which increases the size of the array to 32 elements.
- However, players that want to keep their progress will encounter errors -- as the game loads their files, the array is implicitly sized back down to 16, thus causing exceptions once the game tries to access indices of 16 or higher.
I argue that this behavior is undesired, and the game should only resize the gamearray if the contents of the file do not fit.
In the attachment you'll find the CON file I used to test this.
Attached File(s)
-
save_array_test.zip (2.25K)
Number of downloads: 96