on chrome, when hitting the "escape" key in a loading menu, it infinity loops on the loading icon (of the knight running)
Printable View
on chrome, when hitting the "escape" key in a loading menu, it infinity loops on the loading icon (of the knight running)
While it doesn't sound like it matters (just don't hit escape there), I can't reproduce this so far. What is the exact flow you're going through to get to a point where hitting escape breaks it?
here:Quote:
Originally Posted by Futumsh
-enter any towne
-Click to map
-hit enter (a different town )
-Click the escape key immediately (during the loading icon animation) You might as well spam click it so you can see what I am talking about
you will be stuck in a forever-loading screen.
And yes, it does matter. If it didn't happen so often to the point I was annoyed I would never post about it.
you literally have the escape key as a bind for the main menu. I click the escape key a lot. it's very annoying. saying "just stop pressing escape" is a strange response IMO. The whole point of this thread is to point out bugs and this is obviously a bug.
have you tried using fly spray
Sent from my iPhone using Tapatalk
I have used Google Chrome and Mozilla Firefox for Pocket Legends for last 6 years or so; and I haven't never noticed this before.. I checked both of the browsers and it happens on Mozilla Firefox too; but for me it just disconnects the game after pressing the ESC and waiting couple of seconds on that loading screen. But I don't think there is much they can do to fix this [or do it ever need to be fixed - if it's just an overall mechanic on browser or something like that.
Just disable the escape key. There, fixed it. I'm assuming it crashes because it is trying to open the menu during a loading sequenceQuote:
Originally Posted by Darkfor
Thanks, I've reproduced this and will look into it when I have time.
Escape there literally means 'stop connecting to the new server', though since there's no button for it, it's a bug that it gets processed anyway.
Closing.
This should be fixed if you refresh.