egghelp/eggheads community

that would constitute a rampant privacy violation and should not be implemented, not in a script, not in anything

What I mean to say, when a bot joins a channel, people already in the channel before the bot came in, would have unknown getchanjoin time or 0? kind of weird. I don't think there is a way to get the getchanjoin time for users who were already present before the bot joined the channel! it's 0, and y...

a wonderful example of using eggdrop's hardcoded argument names

manually savnig 'clock clicks -milliseconds' timestamps seem to be the only solution. Addionaly you would have to be aware of getchanjoin possibly being zero (meaning a '$chanjoin - $now < 2' would be true ^-^). Alternately you could try to modify the eggdrops source to save a high resolution timer...

"advanced"?

no, this is very primitive coding

I suspect that by "binding" you mean something quite different from eggdrop's command binding; perhaps if you elaborate on what you want to accomplish, someone will be willing to help

well, actually I was not planing on adding a new dns module... but in a threaded prozess you can lookup the host via gethostbyname, which is basicly the same what eggdrop does (and probably also the dns module does). I havent thought on IPv6 support, but it shouldnt be that hard to implement ^-^. U...

use rconsole

it shows the uptime of each host on your botnet (and allows you to control it remotely without having to log into each bot, too)

1. read the file into list in memory
2. manipulate the list using [linsert] or [lreplace]
3. write the list back to disk file

I hate to disappoint you, given your enthusiasm, but most (if not all) of the stuff you want to implement is kind of pointless to eggdrop if you want to know why the connection was dropped and/or wish to bind to particular IP/port, get familiar with [socket] and use it instead of [connect] while the...

the utimer script executes outside the proc context, therefore $chan is not available for evaluation at execution time

the usual solution to this problem is to force evaluation of $chan inside the proc:

seems like not only the nick is messed up but the whole n!u@h is not IRC-compliant; my guess is eggdrop's n!u@h string splitting routines fail to produce correct results given the weird input format

start over, first type ./configure --help to see what install options are available; hint: use --prefix=$HOME to install this thing in your home directory

use a quality channel protection script (such as xchannel which can, among many other things, punish quote requesters for repeating)

also, have other ops (scripts or bots) add your bot to their userlists as friend