Monosomething
Well-Known Member
- May 24, 2019
- 1,931
- 3,470
- 448
UNFORTUNATELY your fix didnt work. Got an error alongside it but accidentally skipped it (something something "saphire...out of memory error") and... yep. The save file is 389MB large again. Ive deleted it. Dont think theres a point looking at it again.Curious about something but need a test subject... Involves the Save Bloating Glitch
So while looking over the Bloated Events 342-347 on Map 002 in $game_map I found in the only Bloated Save I got to research (Thanks Monosomething ) they all have the same defect which is a Move Route with Code Parameters that contains garbage, a megaton of garbage...
You don't have permission to view the spoiler content. Log in or register now.
Now I'm thinking while I don't know what f*ckup caused this however if I just overwrite the Move Route each time this Event Loads then perhaps that will keep them all below 32 MB each and in check
However I do have a speculation that the Script Sapphire Action System IV which handles Path finding for Events (Such as Enemies and the like) might be bleeding into these Events but that is mostly based off these having Garbage in the Move Route data. I'm not sure how it would actually respond when calculating a Blank Graphic Event being told to move somewhere especially if it doesn't 'Exist' so would it try moving it to nowhere until it hit some memory cap
Patches v0.16.11 Map 002 Band-aid?
Patches/Patch1566418311.rvdata2
Might plug the hole then again it might not however I haven't been able to replicate the Glitch to test it properly
Note: This is only for Map 002 World Map N
If you did experience the Save Bloat Glitch and tried this out then Thanks for testing it; I'm also curious if Saving on any other Maps cause this as well
Current Record Holder is Monosomething with a Save File of 389 MB
I guess people will just have to learn to live without rice (or whatever the bit of food in that tier 0 quest was).