A suggestion would be to make it work with the other netbots components.
Example, a bot needs to enter 'coz the channel is full. It will request a limit increase (botnetop) and all the bots in the botnet will increase it. If there's a desynch, this game can last 5 minutes.
The idea would be that the bots in the botnet stores infos on which bot does the limit. If a bot needs a channel limit increase, it will ask the bots that does the limit first (like botnetop). If none of those bots are around, then normal way will do it.
When a flood is detected, sentinel is turned on, and we are trying to kick/ban the flooders, a channel limit increase is the least thing you needed, bringing in more flooders. So it would be nice that no limit increase would happen.
All in all, taking scenarios and individual bot settings per channel into consideration, making it a strong cooperative botnet.
On a sentinel note, but possible scenario: A channel is always run +i (invite) and also stored as the channel mode. if you type "lc" (lock channel), channel is set +m. When you type "uc" to unlock it, the botnet sets mode -im, then they set mode +i again. Same story about always moderated channels after a join flood.
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
more interactive chanlimit
I've saved a copy of your message and will hopefully remember to look at these issues the next time I'm working on the relevant scripts.
Most of the issues you mention are a pain in the behind in that there are seemingly simple solutions on the surface but this simplicity tends to drop away when all factors are taken into account during implementation.
Most of the issues you mention are a pain in the behind in that there are seemingly simple solutions on the surface but this simplicity tends to drop away when all factors are taken into account during implementation.