4 ms·

I agree, that bug is probably the most ridiculous. To be honest I'm trying to fathom how it even exists, it seems so easy to just up whatever limit is imposing

by tomc1985 6y ago

I agree, that bug is probably the most ridiculous. To be honest I'm trying to fathom how it even exists, it seems so easy to just up whatever limit is imposing that size.

kmeisthax 6y ago
I wouldn't be surprised if there's literally a variable called SAVEGAME that's a char[8192] array somewhere in the serialization path and that's what's causing the corruption.
- saagarjha 6y ago
  You're off by ten orders of magnitude ;) char SAVEGAME[8388608];