Glad to have helped.

With the new error message up I have decided to explore further, and maybe narrow down what is causing the problem. Sorry if any of this is redundant. Also, I am not sure if what I have found is being caused by the new error message or by the bug itself, but here it is (done with Lost Grove):

Error Message Functionality
- If the bug is present, the error message can be called right at the beginning of the battle by pressing "E" on the keyboard; no move selection is required.

- If the bug is not present, pressing "E" on the keyboard at the beginning of the battle does nothing, and the first turn will execute properly.

Important Stuff
- Pressing the "End Turn" button on the screen always executes the turn correctly, and never calls the error message. It is possible to use the "End Turn" button instead of "E" on the keyboard during the whole battle and fight without the error message being called, even if the bug would have happened otherwise.

- Pressing "E" on the keyboard for the first time in a battle calls the error message even if you are not on your first turn. Demonstrated in these screenshots below, I attacked an enemy with the "End Turn" button and then followed up by pressing "E", which called the error message:

So this issue is isolated to using hotkeys? You've never had this issue when manually clicking on the buttons?

I made a slight change to how the script gets the char codes of characters pressed. I don't expect this to resolve the issue, but it's a very easy change and I figured there's a greater than zero chance it works. So I figured we'd try this first.

Let me know if this issue still happens. (I only made this change for within the Lost Grove)

Yes, the issue seems to only be triggered by hotkeys. Whether or not it is caused by the hotkeys themselves is the question, since in 80% of battles using hotkeys, the issue does not happen. But I am not a coding expert.

Lost Grove hotkeys are still triggering the error message right now, after clearing all cache & cookies and logging in & out.

I could not find anything else to help, so sorry about that.

yep, still happening
Got the popup 3 or 4 times total in my temple run just now

Hm. Unfortunately, I am just not sure why this is happening. I mean, at least, I know what's happening, just not why lol.

So, when you guys are triggering this error... it's basically issuing the command specifically for entering a battle, which is a specific configuration of variables. These variables are not passed when ending a turn. Pressing 'E' is directly attached to the "end turn" script or "interact" script - neither of which would be hitting t he "begin battle" script. Somehow, when you are pressing 'E' in those specific instances, it's passing along the variables to begin a battle... which should be impossible. That's just not how any of that is connected.

This issue is confounded by the fact that it's only happening to a select few specific people. For example, I have never been able to naturally reproduce or encounter this bug. However, for the ones who do, they consistently have it happen all of the time.

I have unfortunately pretty much exhausted my list of potential fixes outside of just re-coding how it all works, which isn't an option just to fix this one bug. I am sorry. =\

update, it's started happening on turns other than turn 1 today, or at least I've never seen it be any turn other than then until now-

I believe I have found an answer!

I think this bug is being caused by a chrome/firefox extension for Sylestia; not your code! After removing the extension, all battles have become error-free. I could be wrong and just lucky, but I have been testing for the past 20 minutes and no error messages. After redownloading the extension, the error messages began popping up again.

The extension adds additional hotkey functions to explore zones, and the "E" key is listed as one of them.

If you are curious, the extension is called "Sylestia Extension".

Link: https://www.sylestia.com/forums/?thread=100686&page=3#27 Author: Dracaena Time Posted: 2/13/2022 at 10:28 PM I believe I have found an answer! I think this bug is being caused by a chrome/firefox extension for Sylestia; not your code! After removing the extension, all battles have become error-free. I could be wrong and just lucky, but I have been testing for the past 20 minutes and no error messages. After redownloading the extension, the error messages began popping up again. The extension adds additional hotkey functions to explore zones, and the "E" key is listed as one of them. If you are curious, the extension is called "Sylestia Extension".

This would make a lot of sense. In the times I've tried to diagnose it, I have narrowed down the issue to as "Pressing 'E' is parsing code that doesn't/shouldn't exist". And, well, if that code is coming from an outside source (the extension), that'd answer it entirely lol.