This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post . Click the X in the top right-corner of this box to dismiss this message.
Support & discussion of released scripts, and announcements of new releases.
m4s
Halfop
Posts: 97 Joined: Mon Jan 30, 2017 3:24 pm
Post
by m4s » Sat Jun 17, 2017 4:55 pm
Ok I have found the solution.
The 141st line must be modified from this:
global botnick optimer
to this.
global botnick optimer
chanserv
Line 115 must be restored to:
global botnick chancheck nickopauth opcheck optimer
Thank you to everyone!
m4s
Halfop
Posts: 97 Joined: Mon Jan 30, 2017 3:24 pm
Post
by m4s » Mon Jun 19, 2017 1:30 pm
Hello again
The script works but today a checked my log files and realized that the script
authorizes to nickserv very often and checks the @ status also as often.
My log file shows this:
https://paste.ubuntu.com/24900683/
Is this normal?
Thank you for the answers!
simo
Revered One
Posts: 1108 Joined: Sun Mar 22, 2015 2:41 pm
Post
by simo » Tue Jun 20, 2017 8:17 am
you could use the code i posted wich is smaller and does everything u asked for auto identify on connect and when joining channel it sets OP
Give this a try:
Code: Select all
bind evnt - init-server evnt:init_server
proc evnt:init_server {type} {
global botnick
putquick "MODE $botnick +RSi"
putquick "PRIVMSG NickServ@services.dal.net :identify password"
}
bind notc - "*This nick is owned by someone else*" autoident
bind notc - "*Password accepted for*" compautoident
proc autoident {nick uhost hand text dest} {
putserv "PRIVMSG NickServ@services.dal.net :identify password"
}
proc compautoident {nick uhost hand text dest} {
putserv "PRIVMSG #yourchannel :\002Identification\002 has been successful.."
putlog "\002Identification\002 has been successful.."
}
bind pub o|o !opup opup_pub
proc opup_pub { nick uhost hand chan arg } {
global botnick nickserv chanserv identcmd identpass
putlog "$nick requested in $chan to op up..."
putserv "PRIVMSG $chan :\002OP-Up for $chan (Requested by $nick)\002"
putlog "Requesting ops for $chan..."
putserv "PRIVMSG NickServ@services.dal.net :identify password"
if {![botisop $chan]} {putserv "PRIVMSG ChanServ@services.dal.net :op $chan $botnick"}
}
bind join - * mejoin
proc mejoin {nick uhost hand chan} {
if {$chan == "#yourchannel"} {
if {[isbotnick $nick] && ![botisop $chan]} {putserv "PRIVMSG ChanServ@services.dal.net :op $chan"}
}
}
simo
Revered One
Posts: 1108 Joined: Sun Mar 22, 2015 2:41 pm
Post
by simo » Tue Jun 20, 2017 11:34 am
also from the looks of it, it seems the timers are responsible for the repeated identifying
m4s
Halfop
Posts: 97 Joined: Mon Jan 30, 2017 3:24 pm
Post
by m4s » Tue Jun 20, 2017 12:54 pm
simo wrote: also from the looks of it, it seems the timers are responsible for the repeated identifying
Thank you simo your script I saved it and I appreciate your work.
But it would be great if we could solve the original problem.
So the timer should responsible only for @ checking...
m4s
Halfop
Posts: 97 Joined: Mon Jan 30, 2017 3:24 pm
Post
by m4s » Wed Jun 21, 2017 12:58 pm
m4s wrote: Hello again
The script works but today a checked my log files and realized that the script
authorizes to nickserv very often and checks the @ status also as often.
My log file shows this:
https://paste.ubuntu.com/24900683/
Is this normal?
Thank you for the answers!
The solution is so simple. I had to restart the bot and script works!
Thanks to everyone!
Arnold_X-P
Master
Posts: 226 Joined: Mon Oct 30, 2006 12:19 am
Location: DALnet - Trinidad - Beni - Bolivia
Contact:
Post
by Arnold_X-P » Wed Jun 21, 2017 3:45 pm
Friend use eggdrop version 1.6.20
Do not use 1.8.1 is full of errors in timers
The problem will continue the same happens to me in my tcl of trivia
I get the same error using eggdrop 1.8.1
I recommend that you install eggdrop 1.6.21 that is a very stable version
Arnold_X-P
Master
Posts: 226 Joined: Mon Oct 30, 2006 12:19 am
Location: DALnet - Trinidad - Beni - Bolivia
Contact:
Post
by Arnold_X-P » Wed Jun 21, 2017 3:46 pm
Restarting the eggdrop will not solve the problem
The problem will come back later
See the problems with the version 1.8.1 view forum
m4s
Halfop
Posts: 97 Joined: Mon Jan 30, 2017 3:24 pm
Post
by m4s » Tue Jun 27, 2017 1:16 pm
Arnold_X-P wrote: Restarting the eggdrop will not solve the problem
The problem will come back later
See the problems with the version 1.8.1 view forum
Yeah, It seems you are right. After 4 days a got this:
Tcl error in script for 'timer611088': can't read "nickopauth": no such variable
I changed nothing...