soulfly do you need it for your opers or users? Either way if increase the recvq in either class it will increase the amount of text that users can flood with at any moment on the server. Granted for non opers this is not a good idea.
Well if it's for an eggdrop of yours just give it a no privelage oper line. Which will put it into the oper class and make it so that the bot doesn't get the same recvq as the user class. You might also want to make it so the bot goes mode +H (hidden oper status) after the bot opers and before it joins a room.
The alternative to a no priviledge oper block is to add a passworded allow block with nopasscont set that puts any user specifying the correct password into a class with a higher recvq.
SpaceDoG wrote:Well if it's for an eggdrop of yours just give it a no privelage oper line.
Bad idea. (Consider the bot being hacked.) Rather use Jobe1986's solution.
Ron a no priv oper block means that the bot gets no oper privelages. IE now kills no nothing. It doesn't even get local or global ops. I mean even with local oper status it can't do anything if nothing is specified like can_gzline and all of that fun stuff. Plus with the oper protect module you wouldn't have to worry about network admins being killed by the bot.
A no-priviledges oper still has the ability to see information such as real hosts and IPs even if masked. As well as the ability to see things such as restricted stats. Which although trivial if the bot were to be hacked that could be used to gain information to take down your network or even to gain a list of valid /oper user names complete with valid case.
Also the oper gets user mode +gO even if no flags are specified. So it would still be seen as a local oper.
