ChanServ
Moderators: Moderators, Lobby Developers
ChanServ
Since 0.22 lobby update you'll notice ChanServ bot hanging out in #main, you can use it to manage your own private channels, type "/msg ChanServ !help" to get started. In order to get a channel registered, you'll still have to ask one of the moderators to do it for you, after that you'll have full control over the channel.
Note that currently channel functions such as founder/operator are locked to nickname, so if you rename your account you'll loose your rights as well.
Note that currently channel functions such as founder/operator are locked to nickname, so if you rename your account you'll loose your rights as well.
- SwiftSpear
- Classic Community Lead
- Posts: 7287
- Joined: 12 Aug 2005, 09:29
Not any time soon as I'm not currently working on the lobby, but if someone else makes a patch I can commit it. What needs to be done is a way to make channels persistent (currently they get created/destroyed on the fly) and then adding ban list on top of that, or simply add ban lists on top of current dynamic channels and make ChanServ update the ban list each time it joins a channel (this may be even better option perhaps).Is a Ban option going to become available?
- SwiftSpear
- Classic Community Lead
- Posts: 7287
- Joined: 12 Aug 2005, 09:29
Any idlebot could probably be programmed to hold a banlist. It would be simplistic, it would just auto kick anyone who's name it recognized was on the list, but it would work well enough in the short term. Optimally someone would mod chanserv to do it, since chanserv actually has access to IP's so it could maintain channel IP bans without having to give channel operators any information.
Such a bot is sitting on UF, banbot and slurbot. I'd be happy to provide source code so you could modify it to use server commands rather than chanserv commands, which is the only change I could see you making.
http://www.darkstars.co.uk/randomfiles/obscene.rar
Thats the source to the []Obscene bot, a bot which mutes people if they dont swear, aka #vulgar style. Its slurbot with the obscenity check done in reverse.
The difference between that and banbot is very small. Instead of checking SAID and SAIDEX message events for words, it checks JOIN events for bad usernames and sends a "SAYPRIVATE ChanServ !kick "+username+" #"+channelname
However a simple instance of the banbot program would do fine. []banbot is already running a single banlist across several channels already, namely #aflobby #af #[] #kobs #xta and #k to keep out the very worst of the lobby trolls.
http://www.darkstars.co.uk/randomfiles/obscene.rar
Thats the source to the []Obscene bot, a bot which mutes people if they dont swear, aka #vulgar style. Its slurbot with the obscenity check done in reverse.
The difference between that and banbot is very small. Instead of checking SAID and SAIDEX message events for words, it checks JOIN events for bad usernames and sends a "SAYPRIVATE ChanServ !kick "+username+" #"+channelname
However a simple instance of the banbot program would do fine. []banbot is already running a single banlist across several channels already, namely #aflobby #af #[] #kobs #xta and #k to keep out the very worst of the lobby trolls.
Sorry, i didnt google for Chanserv.Betalord wrote:the ChanServ used here is not what you are looking for, I assume you are looking for the ChanServ service found on irc networks such as dalnet (as this is your first post here I assume you googled for "ChanServ").
I've installed the TA-Dedicated Server on my Linux-Root.
and its trough any circumstance impossible to require an Useraccount for Login.
and i think, its needed to have at least one Admin-Account to manage the Dedicated Server for giving rights like admin, channeladmin etc.
i thought, its an serverside-modul for the server.
In that case, you can get chanserv from here.
If you're running server in "lan mode" that use -lanadmin switch to set up admin account (see readme.txt), if not, then you'll have to manually edit accounts.txt file. You'll have to set 2 right-most bits to 1, like this:
Betalord *** 1100000000000000000000011 ...
If you're running server in "lan mode" that use -lanadmin switch to set up admin account (see readme.txt), if not, then you'll have to manually edit accounts.txt file. You'll have to set 2 right-most bits to 1, like this:
Betalord *** 1100000000000000000000011 ...