Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection error resulted in immediately kicking user from draft #13155

Open
xenohedron opened this issue Dec 17, 2024 · 5 comments
Open

Connection error resulted in immediately kicking user from draft #13155

xenohedron opened this issue Dec 17, 2024 · 5 comments
Labels

Comments

@xenohedron
Copy link
Contributor

Twice today, despite a quick reconnection, user was instantly replaced by a draftbot. There should be a 3 minute grace period.

INFO  2024-12-17 02:19:46,976 CLIENT DISCONNECTED - Athanar [Wait: 1 Draft: 1 ] at 47.33.139.135                         =>[WorkerThread#43[47.33.139.135:63098]] Main$MageServerConnectionListener.handleConnectionException 
INFO  2024-12-17 02:19:55,314 Athanar connected to server with restored session                                          =>[WorkerThread#43[47.33.139.135:63101]] SessionManagerImpl.connectUser 
INFO  2024-12-17 03:01:25,595 CLIENT DISCONNECTED - Athanar [Draft: 1 ] at 47.33.139.135                                 =>[WorkerThread#40[47.33.139.135:64202]] Main$MageServerConnectionListener.handleConnectionException 
INFO  2024-12-17 03:01:33,840 Athanar connected to server with restored session                                          =>[WorkerThread#40[47.33.139.135:64205]] SessionManagerImpl.connectUser 
@Grath
Copy link
Contributor

Grath commented Dec 17, 2024

I've seen several complaints in the Discord about people immediately losing the game when they disconnect recently.

@tiera3
Copy link
Contributor

tiera3 commented Dec 17, 2024

I think it is relevant that Athanar was the host for that event; I have found in 1v1 matches earlier when the person who puts the match up disconnects, they are much more likely to be auto-kicked than the person who joined.

However, I was the first person to be insta-kicked on a momentary disconnect, and I wasn't the host. (It has been happening a lot to me over the last couple of months.)

@JayDi85
Copy link
Member

JayDi85 commented Dec 17, 2024

Athanar pressed the wrong button — that’s the reason:
IMG_1012

If table owner leave the table before it started (e.g. in waiting dialog) then it will be canceled for anyone too by design. I don’t look at tourney logic with a sub-tables — maybe it has some bugs so owner can ruin whole tourney for all (if true then it must be fixed).

@xenohedron
Copy link
Contributor Author

xenohedron commented Dec 17, 2024

No button was pressed. There was nothing intentional about the disconnect.

This was during the draft, not the waiting dialog. The draft continued fine for the remaining players.

@JayDi85
Copy link
Member

JayDi85 commented Dec 17, 2024

You can ask Athanar for a client side logs — it must show the real reason of disconnection. From a server side logs above — it was a user with requested a disconnect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants