flamescape

Very odd. I've not been able to reproduce the issue in Chrome, so I still suspect that a browser extension may be the cause of your issue. I'm glad you've found a workaround anyway.

The problem is that the time for the question was over before the answer reached the bot. The bot had already announced "Time's up" before the answer came in. This is just the way of the internet. Sending messages (especially through Discord) is not instantaneous; it can take half a second for the message to arrive, and this one came too late. Either way, it's clear to me that this guy didn't know the answer to the question anyway. This was his third guess.

Hi NeruDX, It sounds like something is interfering with your ability to run javascript. My best guess is that you have some sort of overzealous security software which is disabling it for all browsers. Try disabling your security software temporarily (if you can) and see if this helps.

Cool. I'm glad I managed to get it working on your laptop. The option has been removed as the game no longer uses this technology. There's nothing to disable.

Same issue as: Continuing discussion on linked thread.

Same issue as: Continue discusson on linked thread.

Appears to be same issue as: I will close this thread and continue discusson on linked thread.

I have made some performance improvements to the maps. Please try again and open a new topic if the problem persists.

Duplicate of

Upon review, it does not appear that any pokemon were duplicated.

Please could you check which browser extensions you have installed? This could be caused by a conflict with a rogue extension. Alternatively, could you try using another browser and see if the problem persists? Let me know. Thanks.

This is working as intended.

Hi, I have made some changes to improve performance on the maps. This should hopefully fix your issue. Please open a new topic if the problem persists. Thank you.

Ok, I'm afraid there's nothing more I can do without further information. Please open a new topic if you discover a way to reliably reproduce this bug and I will investigate.

Fixed