Improved the internal savefile space allocation routines. In the particular test case I was using (saving a 10x10 turf map) this resulted in a 99% reduction in the size of the final save file!
Improved the internal savefile space allocation routines. In the particular test case I was using (saving a 10x10 turf map) this resulted in a 99% reduction in the size of the final save file!
Yow! What did you do to accomplish this???
Knowing Dan, the 10x10 turf map consisted of 100 instances of the same turf. Before it used to save all 100; now, just the one. Ergo, 99% reduction!
Improved the internal savefile space allocation routines. In the particular test case I was using (saving a 10x10 turf map) this resulted in a 99% reduction in the size of the final save file!
Yow! What did you do to accomplish this???
Knowing Dan, the 10x10 turf map consisted of 100 instances of the same turf. Before it used to save all 100; now, just the one. Ergo, 99% reduction!
Ah, it's map-saving specific. So probably doesn't apply to my custom maps (though I also do some things to cut down on duplication in my maps).
Ah, it's map-saving specific. So probably doesn't apply to my custom maps (though I also do some things to cut down on duplication in my maps).
Well, not exactly. If you had 500 zombies roving around, each with the same stats, and you saved it, it would save only 1 zombie. More of an instance reduction thing.
Ah, it's map-saving specific. So probably doesn't apply to my custom maps (though I also do some things to cut down on duplication in my maps).
Well, not exactly. If you had 500 zombies roving around, each with the same stats, and you saved it, it would save only 1 zombie. More of an instance reduction thing.
Nope, cause I have my own routines for saving them too!
Knowing Dan, the 10x10 turf map consisted of 100 instances of the same turf. Before it used to save all 100; now, just the one. Ergo, 99% reduction!