I was exploring the Second Floor (North) of the Ancient Temple fighting enemies and opening chests without any issues, but during a battle against the Pyromancer of Du'vhal the game suddenly stopped responding when I hit the "end turn" button. If I refresh the page it lets me select moves again, but the moment I click "end turn" it gets stuck and nothing happens.

Still having issues? Trying to fix any errors I see in the error log. But it's hard to tell exactly who/what is triggering them so I can't be sure if I fixed any one person's specific errors atm lol.

If it's not fixed, just keep trying every ~30-60 minutes so it keeps logging errors for me to try and find and fix.

Hi, Krin, I just ran into the same problem as Elleshie in the Temple. I'm in the first dungeon against the Earthbender of Du'val. I attacked her all the way to her having full mana, and now it is stuck in the battle. I refreshed and I can select block/attack/etc but I cannot end the turn and progress in the battle. I have tried refreshing several times with the same result.

Hehe. I have been trying to fix this error! Do you know exactly what happened the first time before it broke? Like, did you enter the battle, then leave for some reason, come back and try to continue? Or did this error happen right away in the fight?

The error seems to be triggering due to the attempt of spawning the fragment adds.

It happened on turn six or seven of the fight, right when she hit full mana and her fragments would have spawned. I was attacking normally just to build my own mana, and then blocked on her full mana. Then bam... stuck. I didn't leave the battle, but just tried to refresh the screen. I am still actively stuck in the battle.

Do you want to see the battle logs?

Thank you for the information. I was able to duplicate the bug.

I am working to fix it now.

Thanks, Krin. You're awesome. Good luck!

This should finally be fixed! I have been trying to fix this bug for years lol. It only now is a code-breaking bug because we upgraded from PHP 7.4 to PHP 8.2, so this specific error was upgraded from a "warning" to now "fatal". However, this gave me the needed information to actually find what was triggering it and replicate it myself - which then let's me diagnose and trace the whole process until I find the culprit.

You should be able to continue the battle without issue now.

It worked! Thank you, Krin. You're the awesome sauce! I'm glad I was able to give you what you needed to finally fix the problem.

Thank you so much for fixing it! :)