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

stack_limit is not per command #805

Open
michaelortmann opened this Issue Jan 5, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@michaelortmann
Copy link
Member

michaelortmann commented Jan 5, 2019

Hei hei.

eggdrop currently defaults stack-limit / stack_limit to 4.

The minor problem is, this is irc network specific. The user can set it in eggdrop.conf, ok. We don't support 005 MAXTARGETS yet, which is the value eggdrop should use as stack-limit. We could set it depending on net-type. But this does not solve the following:

The major problem is stack-limit and 005 MAXTARGETS is deprecated. It is applied to all commands and not per command within eggdrop.

New irc servers do 005 TARGMAX instead, which means the stack limit is per command.

Example:

TARGMAX=DCCALLOW:,JOIN:,KICK:4,KILL:20,NOTICE:20,PART:,PRIVMSG:20,WHOIS:,WHOWAS:

Eggdrop can't make use of unlimited mass join and mass messaging 20 people at once, if there is a lower limit for another command, like KICK:4 which forces the single value stack-limit 4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.