Log in to create a new thread
Codename Entertainment Forums > Crusaders of the Lost Idols > Technical Support > Shop Menu Freeze during Autosave
| Shop Menu Freeze during Autosave
| |
|
2 Posts |
Link to post
- Posted March 24th 2017 at 4:33 AM
AlphasoldierI usually save up my gems because I'm a hoarder and I love opening multiple chests at once, but sometimes when I buy a bunch of chests in repetition the chest won't flash and disappear, effectively freezing my game in that window, because the close button doesn't work either.
After having had this several times, I managed to sorta be able to reproduce it, and it seems to only happen right before a level swap, which is usually right after an autosave. The only thing I can do to fix this is restarting the game, which is... well, it gets really annoying. Could this be fixed? A timeout mechanic is probably a good idea. Or even better, can you add an option to buy multiple chests at once with gems and event currency? This would save a lot of time and frustration. |
|
3620 Posts |
Link to post
- Posted March 28th 2017 at 11:25 AM
Erika/AlynianaThank you for the report. Sorry to hear you're experiencing this issue.
It is on the fix list to look into, and your supposition of the cause will help in trying to track it down. |
|
319 Posts |
Link to post
- Posted March 29th 2017 at 2:07 AM
ihatethisfingsounds like the issue ive reported but everyone in my post claimed to not have the issue.
i suppose autosave could be the issue....because i know turning off auto-progression isnt the answer. i have 21615 rubies to spend/play-with when they think they have fixed the issue. |
|
2 Posts |
Link to post
- Posted March 29th 2017 at 1:06 PM
AlphasoldierYeah, it happens less with auto-progression off, but autosaving still happens every so many minutes either way, which still allows it to happen.
It's no secret that the game also saves when you buy a chest, as you can see part of the save prompt on the right of the screen behind the menu. So I'm guessing something is messing up when it tries to save twice in short succession. Maybe the save data is sent twice, and the game expects it twice, but the server only sends it back a single time because it thinks it was a duplicate request? Or maybe the game doesn't properly interpret 2 responses in short succession? I'm just guessing though. |
|
Log in to reply to this thread! | |