-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
[1.9.2] Problem with .bans #1297
Comments
Hi @wilkowy ... sorry, its still early here- could you briefly summarize what you expect to happen and what is not happening? Thanks a ton |
Hi @wilkowy - we want to look into this, but still not sure what the specific problem you're identifying is. Can you rephrase it, so we know where to focus our attention? Otherwise we'll have to close this out. Thanks for the help! |
The issue is that when Also when using |
thanks for the additional clarification! |
Eggdrop 1.9.2
There is problem with command
.bans
and probably.exempts
and.invites
as well.The test were carried out on a busy bot with many users, bans and a few channels. Let's assume we have such environment: we have some global bans;
#first_chan
is a channel on top opeggdrop.chan
so this is the first channel in.status
;#chan_with_some_bans
which has a test timed-ban for the test purposes; and#chan_with_no_ban
is the channel with no local bans.Now the test (mind using the global console channel):
.console #chan_with_some_bans
.bans
.bans all
.bans #chan_with_some_bans
.bans #first_chan
.console #chan_with_no_ban
.bans
.bans all
.bans #chan_with_some_bans
.bans #first_chan
.console #first_chan
.bans
.bans all
.bans #chan_with_some_bans
.bans #first_chan
.console *
.bans
.bans all
.bans #chan_with_some_bans
.bans #first_chan
As you can see this code does not work..
The text was updated successfully, but these errors were encountered: