Error #3001

[JohnTravolta]

Hey, so I finally upgraded the game (my last version was 0.8.6) and am now running 1.0.22. Whenever a cut-scene or battle ends, however, I get:

Error #3001:
context : Main.saveOptions()
message : Error #3001

stack trace :

null

And am forced to quit. When the game crashes after the initial cutscene the game autosaves before crashing. I am running Windows 7. This sounds like a fairly simple error but uninstalling the game and re-installing it from my 1.0.22 upgrade executable didn't fix the problem. I hope someone has seen this before or can at least tell me what the error code is.

[larsiusprime]

This is a really rare error, but from the looks of it, it's caused by a file permissions error in the operating system. The game is trying to read/write to your save files or your config file and the OS has marked those files as read-only, or disallows writing, or some other such nonsense.

So, if you're on windows, go to:
C:\Users\<USERNAME>\AppData\Roaming\DefendersQuest\Local Store\

Make sure the game is not running.

Look for these files:
config.xml
SAVE_SLOT_1.xml
SAVE_SLOT_2.xml
SAVE_SLOT_3.xml

Select them, right click, properties, make sure they're not set to "read only." If they are, uncheck that box and hit "ok."

Try the game again.

If that doesn't work, go back to the files, copy them, and paste them somewhere else on your computer as a backup. Then try deleting the config.xml file - this is your settings file, it saves all your in-game options. If it's deleted the game just restores to the default settings.

Try the game again.

If that doesn't work, try deleting your save files (MAKE SURE YOU BACKED THEM UP FIRST!!!!!!).

Try the game again.

If it worked, you can import your save data by clicking "import" on a save slot and navigating to the backed up .dfq file.

Hopefully you should get it working somewhere along the line.

[JohnTravolta]

Hey, thanks for the fast response. I had assumed that that folder had been deleted when I uninstalled/reinstalled the game so I didn't check it but somewhere along the line I had made that a hidden folder (I have no idea why, I can't remember). Simply un-hiding the folder fixed all of my problems. Interestingly, I never got that error with version 0.8.6. Anyway, thanks again.