View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005711 | unreal | ircd | public | 2020-06-16 00:35 | 2020-06-19 07:50 |
| Reporter | westor | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 5.0.5.1 | ||||
| Summary | 0005711: Add "immune:max-targets-per-command" for "set::max-targets-per-command" operclass permission | ||||
| Description | Hello, The "set::max-targets-per-command" is very helpful option, especially for floodbots, but it is very limited right now so, even an IRCop or a custom operclass cannot bypass that setting that is incorrect (personally) in some cases, it would be nice if there was a "immune:max-targets-per-command" setting to allow the IRCops and some custom operclasses to bypass it. Now lets say i have "maxchannelsperuser 15;" and "max-targets-per-command privmsg 5;" if the user is joined in more than 5 channels he would not be able to use /ame or /amsg in all his joined channels. (THAT'S CORRECT) but what about an ircop or a network bot that wants to do this on a purpose (probably because a game bot or general rss information bot on multi-channels), it's not possible. It would be very nice and appreciated if there was an option like "immue:max-targets-per-command" for bypass, i think that one is deserved to exist because that setting is very powerful and the only thing that missing is an bypass setting :) :) :) :D :D :D - Thanks! | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
