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

\dropflag, \droppowerup, etc. being delayed. #10

Open
MinoMino opened this issue Mar 17, 2015 · 0 comments
Open

\dropflag, \droppowerup, etc. being delayed. #10

MinoMino opened this issue Mar 17, 2015 · 0 comments
Assignees
Labels

Comments

@MinoMino
Copy link
Owner

From #minqlbot on Quakenet.

<quaker_oats> Is it normal for example my binds for \dropflag and \droppowerup to be delayed if minqlbot is active ?
<@mitch> Yes
<quaker_oats> Any way to remedy?
<@mitch> No, it's how the bot works :> Mino can explain it better than I can off the top of my head
<@Mino> Oh wow, I had no idea those commands were passed through the text channel.
<quaker_oats> Ah
<@Mino> That's kinda dumb.
<quaker_oats> ?
<@Mino> Basically there are two channels, one is text-based and has stuff like team changes, chat, getting scores, and so on. The other one has stuff like players' movement, shooting, jumping, etc.
<@Mino> And it's unexpected to hear that dropflag and such isn't taken care of by the latter.
<@Mino> The bot has a queue system for the former channel to avoid having the bot and the user execute commands more or less at the same time, because the server will simply ignore one of them if you do so.
<quaker_oats> My bind for "\team s" is delayed a split second also in case you're wondering anything like that
<@Mino> So if dropflag is one of the delayed ones, it means that if you were to press dropflag and a chat bind more or less at the same time, only one will go through.
<quaker_oats> And also "\team r" and "\team b"
<@Mino> Which is pretty dumb, in my opinion.
<@mitch> Off the top of my head, I would guess it's to stop spam
<@mitch> Seeing as you get the announcer with and flag interactions
<@Mino> Ah
<@mitch> Same reason I would guess they made /say etc. not be able to be used repeatedly at the same time
<quaker_oats> "get the announcer with"?
<@mitch> any*
<@mitch> The announcer shouts stuff on flag interactions
<@mitch> voice over, w/e
<quaker_oats> oh
<@Mino> Well, I could modify the queue system to push dropflag first in queue. Can't think of a better solution.
<@Mino> The other solution would be to bypass the queue system, but that could make the bot drop messages or commands.
<@Mino> or have dropflag be dropped if someone was to do something like !teams right before
<@Mino> so the first solution sounds like the best to me
@MinoMino MinoMino self-assigned this Mar 17, 2015
@MinoMino MinoMino added the bug label Mar 17, 2015
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

1 participant