Boards›Report a Bug

[CLIENT] Error lockChampionPickV1 Get kicked instantly on selecting Lock

MechanicalRose·1/14/2016, 10:55:02 PM·1 votes·516 views

Not sure entirely how to reproduce it, riotsupports twitter just told me to post it here. Which is why I am.

Basically it was my first time in the new champ select, I selected Ashe and hit lock in with about 1-2 seconds left and then it just immediately kicked me, about 4 seconds after I was kicked this message showed up saying the server didn't respond. Screenshot

I then had to wait 5 minutes before trying to get into a game again.

My internet should have been fine since I was in a call with someone and there was no problems with that at any time.

It hasn't happened since. I don't really want to try to reproduce it and get penalized lol

My best guess is the timer didn't match the actual time somehow perhaps due to lag between my end and the servers so when I hit select it possibly may have already kicked me but on my end still showed a few seconds left and that I wasn't kicked? That's just my best possible guess, but I don't see why that would happen when I usually only have like 39 ping.

I don't know if this has happened to anyone else but if you're fast enough with selecting I think you'll probably be fine?

First time posting one of these sorry if I've made any mistakes or waisted anyones time. Thank you for the patience.

1 Comments

2134bob1/18/2016, 4:58:33 AM1 votes

Same situation in the new launcher. I have average ping and solid internet with no packet loss. I selected TF, then locked with 2 seconds or so left (not on purpose, i was chatting with people about our picks). Immediately kicked and got a message for the "dodge" i tabbed out of my now useless launcher (5 minutes to google how much lp i lost for my mistake) and when i returned i had this on my screen: http://prntscr.com/9rijly

Rather than bitch about the lp loss, i mean its my fault i didnt lock sooner, i would like to propose a solution. Make a setting for auto locking your prefered pick if there are 5 seconds or less on the clock. That way, if i pick a prefered champ and don't lock a champ it can OPTIONALLY default back to my prefered if i fail to lock. Now i realize that this may defeat the point of the two stages. But having this as a option would prevent a lot of accidental dodging and would help reduce the long queue times stemming from this human error.

Back to this error message any insight regarding the message would be much appreciated, was it a timing error on my(our) part or is it a random bug that i just happened to hit?

Thank You

[EDIT:] Logs are here: https://www.dropbox.com/sh/9iz118yw9v4hfug/AABisPpED8csCFisjgNY-DRKa?dl=0