game savefile made with NVO resets itself?

hi, my game stores it's savefile in a file made with "Named Variable Object". Sometimes I open the game and find that my save data was reset/deleted so I assume the NVO corrupted or something? It's happened to at least one other person who played my game so its not just my computer. Would ini object be better and not do that?

Quote from DavidN

I have had a couple of people mention corruption with the Crystal Towers 2 save file (which uses the Named Variable Object), too... the issues are few and far between, but apparently it does happen (how often are you seeing it?)

The INI++ object seems to be the most popular way of dealing with save data now.

Not often, about like 3 times in several months. But it might still be enough to annoy people. I probably won't change it in my finished games but I will consider the ini object if I make any more.

I'm saddened to report that the ini++ object has given me this same problem with save data resetting too. It's rare, but it can happen in ANY of my MMF games regardless of whether they use NVO or ini++. I will be switching back to NVO for future games because I find it simpler to use.

basically my saving system is that at start of frame (in global events) it
- load file TouhouWF2.cuteness
- set value boss1clear to get value (boss1clear)

it basically sets everything to itself.

then when the boss dies it does
- add 1 to boss1clear
- save file to TouhouWF2.cuteness

that's pretty much it. I've always wondered about setting it to itself, if its neccessary or not, but it doesnt seem to work right if I leave that out.

also just wondering, could a problem happen if the game LAGS at start of frame or around the time it loads or saves? I know there's a such thing as "Lag glitches" where lag causes problems to happen that aren't normally a problem with the game.