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.

Bot identifying too slow

Old posts that have not been replied to for several years.
Locked
w
woodencross

Bot identifying too slow

Post by woodencross »

Hey guys,

I got an eggdrop running on a shell with anope and unrealircd. I installed the ident09.tcl for identifying and for (re-)getting ops in all channels I specified. The admin gave a vhost to the bot, but for having the vhost, the bot has got to identify himself to nickserv.
Now my problem:
The bot has joined all channels after a few seconds, but with the original hostmask. It takes nearly 30 seconds to identify itself to nickserv and with that, getting the vhost. I saw on another server an eggdrop restarting and it first identifyed and after that joined the channels.

Meanwhile, I edited the eggdrop.conf and added this:

Code: Select all

proc evnt:init_server {type} {
  global botnick
  putquick "MODE $botnick +i-ws"
  putquick "MSG NickServ identify ****"
set default-port 6667
}
I added the msg-stuff. Why does it not work like I want it?

Please help
User avatar
Papillon
Owner
Posts: 724
Joined: Fri Feb 15, 2002 8:00 pm
Location: *.no

Post by Papillon »

did you add the bind to execute your proc?

Code: Select all

bind evnt - init-server evnt:init_server
proc evnt:init_server {type} { 
  global botnick 
  putquick "MODE $botnick +i-ws" 
  putquick "MSG NickServ identify ****" 
} 
#I recommend leaving this outside the proc
set default-port 6667 
Elen sila lúmenn' omentielvo
User avatar
caesar
Mint Rubber
Posts: 3778
Joined: Sun Oct 14, 2001 8:00 pm
Location: Mint Factory

Post by caesar »

Not necesarly he is slow.. maybe the NickServ services are. :P
Once the game is over, the king and the pawn go back in the same box.
User avatar
awyeah
Revered One
Posts: 1580
Joined: Mon Apr 26, 2004 2:37 am
Location: Switzerland
Contact:

Post by awyeah »

Maybe your bot has alot of commands to que when it connects
to a server, you can eventually modify this a little bit to make
it faster if possible.

The "-next" option in putquick is currently the fastest way
for the bot to send commands to a server or services. By utilizing
this option all the queues are pushed up in front of previous queues
currently pending by the bot.

Code: Select all

bind evnt - init-server evnt:init_server 

proc evnt:init_server {type} { 
  global botnick 
  putquick "MODE $botnick +i-ws" -next
  putquick "PRIVMSG NickServ :IDENTIFY <password here>" -next
} 
·­awyeah·

==================================
Facebook: jawad@idsia.ch (Jay Dee)
PS: Guys, I don't accept script helps or requests personally anymore.
==================================
w
woodencross

Post by woodencross »

Hm, sounds good, gonna try that. Will post if it works or not :D
s
spock
Master
Posts: 319
Joined: Thu Dec 12, 2002 8:40 pm

Post by spock »

to bypass the queue completely you could do something like

Code: Select all

proc putnow { a } {
  append a "\n"
  putdccraw 0 [string length $a] $a
}
but you wont want to push too many lines at a time (excess flood / sendq exceeded / whatever else)

EDIT: (how to use it)

putnow "PRIVMSG #abc :test 1 2 3"
photon?
w
woodencross

Post by woodencross »

putquick "PRIVMSG NickServ :IDENTIFY <password here>" -next
This really works best! Thank you very much :D
Locked