egghelp/eggheads community

Auto Oper

2010-10-26T03:57:24-04:00

I've tried to toggle other configs, such as set global-ban-time 130, to see if it is checked, but still .chaninfo gives me the default value ( ban-time: 120)

Nevermind, in the meanwhile I've found out the magic ".chansave" word... thanks again for your precious help!

Statistics: Posted by ali3n0 — Tue Oct 26, 2010 3:57 am

Auto Oper

2010-10-26T03:05:14-04:00

Sorry that I'm don't know ngircd, to be able to give you the exact command that you'd need to set it. With some experimenting though, you should be able to get it.
I hope this helps.

Sure it does! Thank you very much for your help. I'm still not able to gain op status, but at least I know why now. Seems that eggdrop is ignoring some of my config declarations, i.e. this is eggdrop reply:

To regain op's (need-op):
putserv "PRIVMSG #lamest :op me cos i'm lame!"

but I'm 100% sure that's the default one I've already changed. Here my eggdrop.conf:

http://pastebin.com/Rby95x43

I've tried to toggle other configs, such as set global-ban-time 130, to see if it is checked, but still .chaninfo gives me the default value ( ban-time: 120)

Statistics: Posted by ali3n0 — Tue Oct 26, 2010 3:05 am

Auto Oper

2010-10-25T21:02:41-04:00

...
#somechannel is correctly joined at startup though. I've tried other need-op commands, such as putserv "PRIVMSG mynick ciao", but I get no messages to mynick...

I'm not familiar with ngircd.

In the partyline, try:
.chaninfo #channel
and look for a line:
To regain op's (need-op):
putserv "privmsg chanserv :op #channel $botnick"

You may or may not have them now.

Here is a line I use, to set the above:

Code:

.chanset #channel need-op  putserv "privmsg chanserv :op #channel $botnick"

You can read a little about it with:
.help chaninfo and you'll have to find it, in the long return.
or, check here: http://www.egghelp.org/commands/channels.htm
for need-op .

Sorry that I'm don't know ngircd, to be able to give you the exact command that you'd need to set it. With some experimenting though, you should be able to get it.

I hope this helps.

Statistics: Posted by willyw — Mon Oct 25, 2010 9:02 pm

Auto Oper

2010-10-25T15:16:49-04:00

Hi folks. I'm new to eggdrop and I'm playing around a bit. I've got the same environment, ngircd and eggdrop.

Actually seems that OPER works fine (at least according to ngircd logs) but I can't get the need-op function to be called after #channel join.

This works to me:
bind evnt - init-server evnt:init_server

Code:

proc evnt:init_server {type} {  global botnick  putquick "OPER  "}

but not this:

Code:

channel add #somechannel {      chanmode "+nt-likm"      need-op { putquick "MODE #somechannel +o mybotnick" }

#somechannel is correctly joined at startup though. I've tried other need-op commands, such as putserv "PRIVMSG mynick ciao", but I get no messages to mynick...

Statistics: Posted by ali3n0 — Mon Oct 25, 2010 3:16 pm

re:

2009-03-15T23:40:02-04:00

Thank you for your response.

I've changed the command to OPMODE, but it seems to have no effect (also my irc server does not recognize that command, when I try it as a user/IRC operator).

I replaced the botnick variable with the bot username, as you suggested, so the config now looks like this:

Code:

bind evnt - init-server evnt:init_serverproc evnt:init_server {type} {  global botnick  putquick "OPER mybot mightypassword"  putquick "OPMODE #somechannel +o mybot"  putquick "MODE mybot +Hi"  putquick "MODE mybot -ws"  putquick "MODE mybot -o"}

This also didn't help.

The discussed channel is persistent and in eggdrop.conf, it's set with no parametres. I hope that does not collide with anything.

Any other suggestions, where to look?

Thank you

Statistics: Posted by Ron-skY — Sun Mar 15, 2009 11:40 pm

Auto Oper

2009-03-15T22:58:39-04:00

for an irc-operator to be able to change modes for a channel, they must use the OPMODE command instead of MODE

Also dont use botnick for your oper username, just put the entery you entered as username for the eggdrop's oper block.

Statistics: Posted by r0t3n — Sun Mar 15, 2009 10:58 pm

re: getting an IRC oper

2009-03-15T20:19:19-04:00

Hi,

I've done some reading about this, but I am a little bit confused about getting an IRC Operator status for my bot as it joins the designated server.

I am using eggdrop for my own irc server (running on newest ngircd) and I've set up eggdrop.conf like this:

Code:

proc evnt:init_server {type} {  global botnick  putquick "OPER $botnick "  putquick "MODE  +o $botnick"  putquick "MODE $botnick +Hi"  putquick "MODE $botnick -ws"  putquick "MODE $botnick -o"}

Note that values in lt/gt are replaced for the purposes of thread posting. Bot is also properly set as IRC Operator in ngircd.conf.

If I understand correctly, the proper way of setting up eggdrop as channel operator is this:
1) get an IRC operator status via /OPER
2) set +o for itself on that channel
3) (possibly for more security) de-op IRC operator status (via -o)

It's possible that I am wrong, the commands you see above are derived from my experiments as regular user (so I tried to oper up, give myself +o on channel, then de-op myself again).

Anyways, auto-oping for eggdrop does not work, so if anyone can come up with anything I might be/am doing wrong, I'd more than appreciate it.

Statistics: Posted by Ron-skY — Sun Mar 15, 2009 8:19 pm

Auto Oper

2008-03-31T00:24:01-04:00

Code:

proc evnt:init_server {init-server} {  global botnick  putquick "PRIVMSG Nickserv :identify "  putquick "oper  "  putquick "MODE $botnick +Hi"}

Works, tested (quite often).

Statistics: Posted by DragnLord — Mon Mar 31, 2008 12:24 am

Auto Oper

2008-03-30T20:41:30-04:00

Code:

set oper(user) "foo"set oper(pass) "bar"set oper(modes) "+H"; # Must be in format +-flagsset nickserv(host) "nickserv@some.network.org"set nickserv(pass) "foobar"set nickserv(modes) ""; # Must be in format +-flagsbind evnt - {init-server} evnt:autoproc evnt:auto {event} {    global botnick oper nickserv    if {$oper(user) != "" && $oper(pass) != ""} {        putquick "OPER :$oper(user) $oper(pass)"        if {$oper(modes) != ""} {            putquick "MODE $botnick $oper(modes)"        }    }    if {$nickserv(host) != "" && $nickserv(pass) != ""} {        putquick "PRIVMSG $nickserv(host) :identify $nickserv(pass)"        if {$nickserv(modes) != ""} {            putquick "MODE $botnick $nickserv(modes)"        }    }}

Untested!

Statistics: Posted by r0t3n — Sun Mar 30, 2008 8:41 pm

Auto Oper

2008-03-30T15:21:30-04:00

it was said like three times that you have to alter the script to suit your needs, I have no idea how or to whom your bot is supposed to ask for oper status on your network without more information. To make the bot oper-up, identify to nickserv, and then finally set itself mode +H, you just need to add all the parts together in the same procedure, something like this:
Code:
proc evnt:init_server {type} {  global botnick  putquick "PRIVMSG NickServ :identify "  putquick "PRIVMSG OperOp :login   putquick "MODE $botnick +H"}
Now you are expected to alter this procedure to suit your needs.

to oper its /oper user pass

to identify its /nickserv identify password or /msg nickserv identify password

to set mode H its /mode me +H

Statistics: Posted by TheDevil — Sun Mar 30, 2008 3:21 pm

Auto Oper

2008-03-30T14:43:32-04:00

it was said like three times that you have to alter the script to suit your needs, I have no idea how or to whom your bot is supposed to ask for oper status on your network without more information. To make the bot oper-up, identify to nickserv, and then finally set itself mode +H, you just need to add all the parts together in the same procedure, something like this:

Code:

proc evnt:init_server {type} {  global botnick  putquick "PRIVMSG NickServ :identify "  putquick "PRIVMSG OperOp :login   putquick "MODE $botnick +H"}

Now you are expected to alter this procedure to suit your needs.

Statistics: Posted by YooHoo — Sun Mar 30, 2008 2:43 pm

Auto Oper

2008-03-30T12:03:41-04:00

it should look similar to:
Code:
bind evnt - init-server operproc oper {type} {  putserv "OPER  "}
made sure it says putserv and it still fails to oper and fails to identify to nickserv as well.

Then you have other problems.
Start your bot with the -nt switches.

Statistics: Posted by DragnLord — Sun Mar 30, 2008 12:03 pm

Auto Oper

2008-03-30T04:12:50-04:00

it should look similar to:
Code:
bind evnt - init-server operproc oper {type} {  putserv "OPER  "}

made sure it says putserv and it still fails to oper and fails to identify to nickserv as well.

Statistics: Posted by TheDevil — Sun Mar 30, 2008 4:12 am

Auto Oper

2008-03-29T23:48:26-04:00

it should look similar to:

Code:

bind evnt - init-server operproc oper {type} {  putserv "OPER  "}

Statistics: Posted by DragnLord — Sat Mar 29, 2008 11:48 pm

Auto Oper

2008-03-29T18:44:45-04:00

Code:

# This is a Tcl script to be run immediately after connecting to a server.bind evnt - init-server evnt:init_serverproc evnt:init_server {type} {  global botnick  putquick "PRIVMSG NickServ :identify "  putquick "MODE $botnick +i-ws"}

this is found in your conf file, alter it to suit your needs

I edited this and the bot fails to identify and oper.

Statistics: Posted by TheDevil — Sat Mar 29, 2008 6:44 pm