[IRCServices] Support Request

[Georges Berscheid]

Hi,

if you need nothing more than your channel being kept open, use /os raw 
:ChanServ JOIN #channel.
This will slightly desynch services though, since they will not know any 
of their pseudo-clients have joined a channel, but that should not 
really be a problem.
But if you want to have channel commands like !op !deop etc. you might 
use eggdrop bots since there are loads of modules that support these 
commands. Or you might want to write a module for services which does that.

Georges


Andrew Armstrong wrote:

>One more question, but first, thankyou Finny!
>
>Was a bit confusing, could not seem to work out why I could not bring up the
>list...
>
>The message should (possibly) be changed to a more helpful "Was not added to
>the operator list, Plasma already exists on the administrator list."
>
>One last request, can anyone suggest some decent/working/useful bot services
>for channels?
>The purpose of the bot would have to (possibly) idle when there is zero (0)
>users in the channel, to keep the channel open in order to retain channel
>keys (this is important).
>
>Some suggestions we have come up with are eggbot - but what modules do we
>use? This bot seems a task to configure with so many services to tighten up!
>
>What we are basically looking for is something similar to epona style
>BotServ (ie, the commands !op !deop) and basically functioning as a simple
>bot with simple commands such as !op !kick and !seen available to the users
>who match the channel accesslist. One thing that dissapointed us though is
>that the bot will not remain in empty channels to retain key settings
>(setting RESTRICTED ON is not an option).
>
>Does anyone have experience with such a bot? Any ideas on how to set up such
>a simple bot?
>It would need to be basically like epona's bot, but be able to idle in empty
>channels.
>
>Thankyou.
>
>
>----- Original Message -----
>From: "Finny Merrill" <griever at t2n.org>
>To: "IRC Services General Mailing List" <ircservices at ircservices.za.net>
>Sent: Monday, June 16, 2003 5:55 PM
>Subject: Re: [IRCServices] Support Request
>
>
>  
>
>>On Mon, 16 Jun 2003 17:51:20 +1000, Andrew Armstrong
>><andrewa at bigpond.net.au> wrote:
>>
>>    
>>
>>>Hey,
>>>
>>>I am having a problem with the OperServ function OPER LIST command, and
>>>would be greatly appreciated if I can get some help.
>>>
>>>Just some information for you, I am an IRC Administrator and Services
>>>Root Administrator on this IRC Network.
>>>
>>>I have the following usermodes: +acfghikmnorswxzACGMTWZR
>>>My o-line is: O *@* * plasma 4567bcefghiklnruwxzABCDIKNORXZ 55
>>>      
>>>
>>Wow, nice.
>>
>>    
>>
>>>The problem I receive is that I will attempt to list the operators in
>>>      
>>>
>the
>  
>
>>>OperServ list, and the list returns blank. However, the ADMIN LIST
>>>command works fine and returns the admin list as expected.
>>>      
>>>
>>>To confirm I indeed did have atleast one user on the list, I typed:
>>>/msg OperServ OPER ADD Plasma
>>>
>>>I received the following message:
>>>-OperServ-Plasma already exists on the Services admin list.
>>>      
>>>
>>Note the key word *admin*. You're trying to add someone to the oper list
>>who's on the admin list, which you can't do.
>>
>>Maybe we should change the OPER and ADMIN commands so that if you ADD
>>someone
>>to one list who's on the other, it removes them from the other list.
>>------------------------------------------------------------------
>>To unsubscribe or change your subscription options, visit:
>>http://www.ircservices.za.net/mailman/listinfo/ircservices
>>    
>>
>
>------------------------------------------------------------------
>To unsubscribe or change your subscription options, visit:
>http://www.ircservices.za.net/mailman/listinfo/ircservices
>
>
>  
>