egghelp/eggheads community

Chanservneed

2008-05-11T03:45:44-04:00

That's caused by your flag l which tells the bot to have halfop on the channel, therefore it tries to gain halfop using the halfop command. Removing the o flag from chanserv tells the bot to never request op by itself. Therefore it would only get op, when chanserv feels like doing so.

I cannot exactly tell you why your bot does that, I can only remark that it is not neccessarily caused by the script, since I cannot reproduce what you describe.

Statistics: Posted by De Kus — Sun May 11, 2008 3:45 am

Chanservneed

2008-05-10T18:57:40-04:00

chanserv flags -> lo
my bot regain op even i'm as owner deop them..

then I change the chanserv flag from "lo" to "lv"
seem working, my bot do not REOP, but i got this on partyline, often..

[22:37] -ChanServ (service@dal.net)- Unknown command: halfop
[22:37] -ChanServ (service@dal.net)- For help: /msg ChanServ@services.dal.net HELP

there's no halfop or admin command on DALnet,

is this normal ??

Statistics: Posted by uffs — Sat May 10, 2008 6:57 pm

Chanservneed

2008-05-09T08:55:10-04:00

Ahh, I guess I know what he means. But looking at the handle:deop I wonder if this the place where reop conditions are checked. I am pretty sure that my bots do not reop uppon deop of myself. Looking at the code I understand, that only deops of chanserv are explicitly made undone (due to deops of net rejoins). Any other reop is triggered by the event "need op" of the bot itself.
So I wonder why my script would reop on deop of an friend or owner, testing with my own bots shows me that no reop is done.

Statistics: Posted by De Kus — Fri May 09, 2008 8:55 am

Chanservneed

2008-05-09T08:40:35-04:00

I think he means if the user has +nf chattr, and the victim was the bot, do not proceed to reop the bot, else if the user does not have +nf flags then proceed to reop the bot.

Statistics: Posted by r0t3n — Fri May 09, 2008 8:40 am

Chanservneed

2008-05-09T03:36:12-04:00

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?

Statistics: Posted by De Kus — Fri May 09, 2008 3:36 am

Chanservneed

2008-05-08T16:42:20-04:00

is it possible to add ..

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

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

Statistics: Posted by uffs — Thu May 08, 2008 4:42 pm

Chanservneed

2007-02-01T05:46:16-04:00

its working now.. thanks

Statistics: Posted by elisca — Thu Feb 01, 2007 5:46 am

Chanservneed

2007-02-01T04:38:34-04:00

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.

Statistics: Posted by De Kus — Thu Feb 01, 2007 4:38 am

Chanservneed

2007-01-31T19:27:43-04:00

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

Statistics: Posted by elisca — Wed Jan 31, 2007 7:27 pm

Chanservneed

2007-01-31T17:55:13-04:00

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.

Statistics: Posted by De Kus — Wed Jan 31, 2007 5:55 pm

Chanservneed

2007-01-31T17:36:14-04:00

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"

Statistics: Posted by elisca — Wed Jan 31, 2007 5:36 pm

Chanservneed

2007-01-31T15:05:25-04:00

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?

Statistics: Posted by De Kus — Wed Jan 31, 2007 3:05 pm

Chanservneed

2007-01-31T01:35:05-04:00

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

Statistics: Posted by elisca — Wed Jan 31, 2007 1:35 am

Chanservneed

2006-09-13T07:33:30-04:00

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

Edit: okay, upload done ^-^

Statistics: Posted by De Kus — Wed Sep 13, 2006 7:33 am

Chanservneed

2006-06-28T14:00:32-04:00

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

Statistics: Posted by De Kus — Wed Jun 28, 2006 2:00 pm