I've had this issue probably about once every half an hour while battling for the past few days.

When I'm using hotkeys very quickly, I think something gets messed up in the timing of how the game handles it, and it ends up thinking I'm using two attacks at the same time with the same pet (at least going based off the layered attack icons):


Un-selecting that attack or un-selecting that enemy removes the second attack but still doesn't give me the option to end my turn. The problem only seems to be solved by re-loading the page.

Does this issue only happening in Astryl's Vale zones? Or does it also happen in The Lost Grove?

Hey!!

I know I didn't report this issue, but I've had it occur to me in the Lost Grove. It only happened between stage four and five, where it would last for the entirety of the battle, and then transport me to the barracks, no matter where I was previously. I haven't had it occur since, so it might have just been something specific to that stage.

Fortune Event is amazing, by the way :)

It definitely happens in the LG, and I think I've encountered it in the old battling system as well (I think I ran into it defending the sanctuary of saerielle from an attack but I'm not 100% sure).

I haven't had the issue of being transported back to the barracks, though, and it hasn't lasted for a whole battle. I just reload the page and it fixes it and then all is well for 20-30 mins until it happens again.

So I took a look at the script. What appears to be happening is probably what you are guessing. When you see the abilities stacked like that, basically it was running two processes at the same time overlapping each other and it's probably very likely that in that scenario, things break.

The problem is, the scripting code for the exploration systems (they all share basically the same script code with some different modifications for each iteration) is extremely convoluted and difficult to work with. I really do not think there is much hope I can somehow figure out a fix for this without breaking ten other things.

Javascript runs at the speed of your device/browser. If you have an older device (or even just using a mobile device) or an overloaded device, Javascript can end up running pretty slow. This can be confounded by poorly written code or large Javascript files, both of which apply here lol.

So my best guess is that the scripts are running slowly on your device and you sometimes move faster than they can keep up. Since they are not well written, they are susceptible to this and do not have fail safes in place for when actions hit it faster than it can keep up. Thus, it breaks.

May I ask for the device and/or operating system and web browser that you're currently using?

Ah, yeah, that makes sense. If its not something you can fix until that portion of the code gets revamped, its not the end of the world - reloading fixes it so it doesnt really get in the way too much.

Im on a 2019 MacBook Air running macOS Monterey 12.4, and I use Google Chrome. My computer does have very limited storage, though, which makes it a little bit slower than it might otherwise be as that limits its working memory. I would say its typically about average processing speed for a decent laptop - not overly slow, but not a super speedy gaming computer either.