Chanservneed

De Kus · Post by **De Kus** » Fri Jun 16, 2006 4:49 am

Alchera wrote:You do not use mIRC? That particular client has a check box in its' options to ignore invites; which is what I was indicating. If left unchecked you will finish up in all sorts of places because you simply accepted an invite.

I am guessing the user wants to know if the same can be done with eggdrop.

De Kus wrote:However for channels he has records of, it joins automatically on invite. Thats a behavior this script is beware of, everything else is off-topic.

already answered?! or isnt it obvious that it ignores any other invites then?!
btw: you cannot "accept" or "deny" an invite... you simply join the channel after you were invited... or don't

.

Alchera · Post by **Alchera** » Fri Jun 16, 2006 7:41 pm

De Kus wrote:I am a bit confused about his request and if it has even to do anything with chan-/nickserv

My original response was to that as you indicated you did not understand what the user wanted.

The use of mIRC in my post was analogous the the query regarding eggdrop accepting invites to any channel because that is the most widely used IRC client.

Off topic:

De Kus wrote:btw: you cannot "accept" or "deny" an invite... you simply join the channel after you were invited... or don't

Invites can be ignored if a user so chooses, it really is as simple as that. I use XChat and I choose to use its setting to ignore (deny) invites. If that were not turned on then I would not be ignoring but accepting invites.

Lighty · Post by **Lighty** » Sun Jun 18, 2006 11:04 am

Hey that worked great! Thanx!

Where can I find a list of the commands to use with this script. I am now tryin to set the need-key.

De Kus · Post by **De Kus** » Sun Jun 18, 2006 3:33 pm

If you refer to '.chanset #channel need-...', there is no such undocumentated command supported by that script.

PS: you dont need the key to join, simply get an invite.

De Kus · Post by **De Kus** » Wed Jun 28, 2006 2:00 pm

Changes from v1.5 to v1.5.3:
- adjusted the putlogs (uniform format)
- trigger need op on chanserv deop
- all handle matchs in nocase
- Changed flag requirements for invite, since you only need a "Level above 0" for these commands on (default) chanserv

De Kus · Post by **De Kus** » Wed Sep 13, 2006 7:33 am

Changes from 1.5.3 to 1.5.4:
- fixed stupid missing var entry in global of handle:nickauthed

Edit: okay, upload done ^-^

elisca · Post by **elisca** » Wed Jan 31, 2007 1:35 am

ChanServ features: invite on need seem not working well.. my bot can not enter the chan with +i mode

De Kus · Post by **De Kus** » Wed Jan 31, 2007 3:05 pm

Are you sure that your bot knows it has the right to do an invite (read the full text of install requirements)? It expects to have at least voice level at chanserv for that channel, else it won't send an invite.
Also possible could be that it cant seen chanserv online -> no +watch supported by ircd?

elisca · Post by **elisca** » Wed Jan 31, 2007 5:36 pm

De Kus wrote:Are you sure that your bot knows it has the right to do an invite (read the full text of install requirements)? It expects to have at least voice level at chanserv for that channel, else it won't send an invite.
Also possible could be that it cant seen chanserv online -> no +watch supported by ircd?

my bot have a @ access in that chan, honestly i dont understand with this, i have read your Install requirements.. hmm could you explain to me more specific regarding this.
example what its mean, we must to do what with this "Add (if not existing) chanserv as a user with hostmark matching the real chanserv, global +m flag and flags represanting the bots access level on the channels"

and i think this is will be related to :

[8:25:55am] ((spitz) [08:28] Tcl error [handle:servwatch 1]: No such user.
[8:25:55am] ((spitz) [08:28] Tcl error [handle:servwatch 1]: No such user.
[8:26:05am] [elisca] .set errorInfo
[8:26:05am] ((spitz) [08:28] #elisca# set errorInfo
[8:26:06am] ((spitz) Currently: couldn't open socket: connection refused
[8:26:06am] ((spitz) Currently: while executing
[8:26:06am] ((spitz) Currently: "socket -async $hostname $x"

De Kus · Post by **De Kus** » Wed Jan 31, 2007 5:55 pm

Read the install requirements closer. You have to tell your bot that it has access on chanserv. How you do that is written in the install requirements. Your error message says clearly that you didn't do all steps mentioned there.

btw. the details of the errorInfo is from another error

, but thanks for the effort.

elisca · Post by **elisca** » Wed Jan 31, 2007 7:27 pm

i hope this`s not a dumb think..
does it`s mean we must set like this :

.+user chanserv chanserv@services.dal.net
.chattr chanserv +m

De Kus · Post by **De Kus** » Thu Feb 01, 2007 4:38 am

exactly, the global master allows chanserv to act against other policies (making the bot to never start a fight against chanserv which would be rediculous). Also add channel rights corresponding the access level of the bot to chanserv. The script will ask chanserv only for things it knows to have access by these accesses for a channel (and therefore not ask for op in a channel it is only on the voice list).
oh, and make sure your variable for network and the string "DALnet" match exactly.

elisca · Post by **elisca** » Thu Feb 01, 2007 5:46 am

its working now.. thanks

uffs · Post by **uffs** » Thu May 08, 2008 4:42 pm

is it possible to add ..

if {[matchattr $handle +nf -> procedure REOP if bot -o will halt..

if {![matchattr $handle +nf -> Bot regain OP

De Kus · Post by **De Kus** » Fri May 09, 2008 3:36 am

I just tried to understand what you tried to say, but I simply don't get it at all. The only thing I am pretty sure about is, that you are talking about the "op" brace in handle:need, right?