Skip to content
This repository has been archived by the owner on Oct 20, 2023. It is now read-only.

Detect when queue is broken #3

Closed
DarkoGNU opened this issue Mar 11, 2019 · 7 comments
Closed

Detect when queue is broken #3

DarkoGNU opened this issue Mar 11, 2019 · 7 comments
Labels
enhancement New feature or request

Comments

@DarkoGNU
Copy link

So... there are situations like:

  • I was 240th or something like that and I instantly went to place 80th. It was going down to 60th, and I was stuck for over 10 minutes. Probably some bug, I reconnected.
  • I was maybe 80th again and I got 1st instantly. I didn't join for over 10 minutes. I disconnected.
  • some cases like just getting stuck, without any instant position change
    It happens to me sometimes both with the proxy and when I just use Impact. These anomalies should be detected and the proxy should begin queuing again.
    Sorry for poor English :|
@themoonisacheese themoonisacheese added the enhancement New feature or request label Mar 11, 2019
@starcraft66
Copy link

@themoonisacheese make the proxy send "/queue main" in chat when the queue breaks in order to be re-queued without losing your place or having to reconnect.

@themoonisacheese
Copy link
Owner

Thanks for the help, however the hard part is detecting when the queue is broken in the first place.

@ngt1133
Copy link

ngt1133 commented Jun 2, 2019

When you in queue, your position types in the chat. When queue is broken, server stops typing your queue. So my idea is, when the server stops writing your position in the chat to the chat, just restart the queue.

@starcraft66
Copy link

Yep, if you don't receive a chat message indicating your position in queue withing a 15-second window, consider the queue broken and send the message.

@themoonisacheese
Copy link
Owner

that's actually a very good point. will do.

@AverageComet250
Copy link
Contributor

Just thought I'd ask if this has been implemented yet and if this should actually be closed

@MrGeorgen
Copy link
Collaborator

Just thought I'd ask if this has been implemented yet and if this should actually be closed

code in this project hast not been implemented, but it is really long ago that I had this problem, so hausemaster might fixed it

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants