Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Botserv to kick users of access list  (Read 6629 times)

0 Members and 1 Guest are viewing this topic.

DarkMind

  • Guest
Botserv to kick users of access list
« on: February 24, 2006, 07:19:19 AM »

Hi,

i want the botserv, to kick flooders and repeaters. That is surely no problem with user who aren't listed in a chans access list. Now I wanna know how i can get the botserv to kick and ban flooders who are registred and listed in the access list.


Thanx


[Anope 1.7.13 + Unreal3.2]

[Bearbeitet am 24-2-2006 von DarkMind]

[Bearbeitet am 24-2-2006 von DarkMind]
Logged

FiXato

  • Guest
(No subject)
« Reply #1 on: February 24, 2006, 04:31:18 PM »

if you use the xOP system, disable DONTKICKVOICES
Quote

/bs help set dontkickvoices
[2006-02-24 - 17:30:15] BotServ: Syntax: SET channel DONTKICKVOICES {ON|OFF}
[2006-02-24 - 17:30:15] BotServ:
[2006-02-24 - 17:30:15] BotServ: Enables or disables voices protection mode on a channel.
[2006-02-24 - 17:30:15] BotServ: When it is enabled, voices won't be kicked by the bot
[2006-02-24 - 17:30:15] BotServ: even if they don't match the NOKICK level.


else if you use the ACCESS LEVELS system, modify the level for the NOKICK description.

[Edited on 2006.2.24 by FiXato]
Logged

DarkMind

  • Guest
(No subject)
« Reply #2 on: February 25, 2006, 07:59:47 AM »

Hi,

I use XOP, DONTKICKVOICES is disabled,but botserv only kicks those voices, who arent listed in the access list.
Logged

FiXato

  • Guest
(No subject)
« Reply #3 on: February 25, 2006, 01:50:24 PM »

Hmm... then I think your only solution is switching to the access levels system.
Logged

owine

  • Anope User
  • Offline Offline
  • Posts: 130
(No subject)
« Reply #4 on: February 25, 2006, 04:34:29 PM »

you want...
Quote

/botserv set #chan DONTKICKOPS on

-BotServ- Syntax: SET channel DONTKICKOPS {ON|OFF}
-BotServ-
-BotServ- Enables or disables ops protection mode on a channel.
-BotServ- When it is enabled, ops won't be kicked by the bot
-BotServ- even if they don't match the NOKICK level.

i think.

[Edited on 25-2-2006 by owine]

[Edited on 25-2-2006 by owine]

[Edited on 25-2-2006 by owine]
Logged

FiXato

  • Guest
(No subject)
« Reply #5 on: February 25, 2006, 10:36:55 PM »

I think that that won't help either, since it still doesn't affect those on the ACCESS list, it is just for the manual opped persons.
Logged

ShelLuser

  • Guest
(No subject)
« Reply #6 on: February 26, 2006, 02:30:36 PM »

I think you are all right but the whole issue goes deeper than this. Next to the options described you also have, for example, the "NOKICK" level (default set to 1, "never get kicked by the bot"), PROTECT or PROTECTME (default set to a higher value), etc.

Its most likely not a specific setting but a combination. However, in this case my bet goes out to NOKICK (this is on 1.7.12 by the way).
Logged

FiXato

  • Guest
(No subject)
« Reply #7 on: February 27, 2006, 04:36:35 AM »

And still it is too bad that those things are only usable under the access levels system and not the default xOP system..
Logged

ShelLuser

  • Guest
(No subject)
« Reply #8 on: February 27, 2006, 01:12:11 PM »

Quote
Originally posted by FiXato
And still it is too bad that those things are only usable under the access levels system and not the default xOP system..

I disagree. Adding too much bells and whistles would only defy the whole purpose of the xOP system. The current setup where you have autovoice -> autoop -> AKICK and founder access is very straight to the point.

Still, I certainly would welcome an option for the service administrators to control the default levels which newly created channels get, even within the xOP system. A bit like the currently availble 'ChanServ default options'.
Logged

FiXato

  • Guest
(No subject)
« Reply #9 on: February 28, 2006, 12:58:43 AM »

ideally it would be nice if either services admins, or even channel founders, could create their own level aliases.
So that they could specify several levels templates. So they are not restricted to just vop/hop/aop/sop, but can create their custom 'ranks'. So combining the simple adding of users to a group, but the advanced possibilities of the access levels.
Logged
Pages: [1]   Go Up