I’m playing WotR on the Switch. Whenever I enter Ten Thousand Delights, I can no longer save my game. It doesn’t matter if I leave again or not, once I enter, I can no longer save my game. All I get is “SAVINGERROR”. Any help with this issue would be super appreciated. I have two missions to complete inside there.
External link →Same issue. I have made u/owlcatstarrok aware of this in the bugs thread, so atleast they know about this issue.
Hopefully the upcoming patch fixes this but we shall have to wait and see. Although I know patching takes a long time for the Switch, it is unfortunate that we have waited for so long for a working game.
Most likely that's a lack of space. The closer to the end of the game, the bigger the save files get, and there's an upper limit the cloud service allows to store. So try deleting earlier saves, and the game should allow you to save. But we'll investigate nevertheless.
That doesnt make sense as skipping the brothel altogether makes saving later a non-issue
It is the location. Not about save space.
A patch is coming approximately in January, please let me know if it doesn't fix the issue.
Hello! I'm having the same issue on my Switch. My game is updated to the latest version, but the game started getting a "SaveError" and crashing when I tried to save (or use a portal to leave) the Ten Thousand Delights. This only started happening after I got Hilor's letter in the Flesh Markets. Doesn't happen as long as I avoid the Ten Thousand Delights. Disappointing because I have other unfinished business there. :-( The very long error message says something about a missing JSON file and the Den of Sweet Horror.
Hello, it's a known problem. January patch didn't fix it, but it seems to be related to an overly long file name of the location which console can't handle.
If this is really the only problem that causes it (so far it looks that it is), a fix for it is coming in the next patch, scheduled for the first week of March.
After the new patch i have the same problem on pc, once i go inside i can't save anymore
Hello, does it give you any error messages? Can you give a screenshot?
Hi, i do get a error messages if after i go inside 10 thousand i try to enter nocticula palace.
Also the problem with saves after 10 thousand occur in act 4 and in act 3 if demon and you try to do the mythic path quest, if you enter inside ten thousand at any point, you can't save anymore.
Thank you, we've found the issue, working on a hotfix right now.
I also get the saving error after entering Ten Thousand Delights during the "Traces of Shadows" quest. Happens right after Nocticula talks to me. Playing on PC
Hello, thank you, expect a hotfix very soon.
Thank you.
I did spend some time tracking down the issue and found that if I have never set foot inside the TTD I can save all I want. I can even save all I want after visiting the TTD. The trouble seems to happen after I reload a save after having visited the TTD. At that point if I ever set foot in the TTD again I get the SaveError problem again. I tested this by running through every quest in the building, saving every step of the way with no issue. It was only after I reloaded a save that the problem reappeared. To make sure it wasn't something I did in there necessarily I went back to my save after first entering the building and it too caused the issue where SaveError was happening. Going back to the save just before ever going into the building allows me to go through all of it again without the SaveError returning. However, again, the save error returns as soon as I load any save after having visited the TTD.
I don't know if this is useful but thought I would share.
Also, I figured this might be useful to the others experiencing the issue. You can get everything done there as long as you do it all in one go and never reload a save before you're done with the TTD. That is until the fix comes, and sounds like it will be soon. Hopefully the fix doesn't require going to an earlier save. I suppose in the off-chance it might, take this workaround with a grain of salt I guess.
We've already fixed the problem internally but thank you nevertheless! Just waiting for the hotfix to be ready to be deployed.
devtrackers.gg
