egghelp/eggheads community

.dump problem (qnet)

2002-07-27T07:59:22-04:00

This may be IRCD related.

Map is a non-standart IRC command, thus there is no definition as to what reply code should be used.

Statistics: Posted by ppslim — Sat Jul 27, 2002 7:59 am

.dump problem (qnet)

2002-07-27T07:53:43-04:00

i tried NetStats1.2.tcl & lusers from DAWG, but somehow they dodn't work.

They didn't print any error / debug msg on the console, and i dunno what could be wrong...

Statistics: Posted by GodOfSuicide — Sat Jul 27, 2002 7:53 am

.dump problem (qnet)

2002-07-27T07:49:03-04:00

The bot isn't meant to return anything.

The bot will only place information on the partyline, based on your console flags.

It is also dependant on what the bot is programmed to recognise.
EG, it is programmed to listen for JOIN, PART, QUIT, PRIVMSG, NOTICE and so on, so that it can send replies and so what.

Lusers an map commands are not programmed into eggdrop, because there is no requirment (not forced by the protocol), and will not affect how the bot works.

There are to ways to get it to display this on the partyline.

1: Read throught he config file and enable the server debug console flags, then add them to your console settings.

2: Setup a Tcl script to process them based on the RAW bind. You can then issue them via a putlog command, designed to display in one of your current console flags.

Statistics: Posted by ppslim — Sat Jul 27, 2002 7:49 am

.dump problem (qnet)

2002-07-27T06:10:07-04:00

When i use .dumb mode #pmp +l 20 it works correct, but when i try .dump lusers or .dump map the bot doesn't return anything.

Is this a QNet Bug / Protection or a protection in eggdrop ? Cos /map /lusers etc returns are quite big.

Statistics: Posted by GodOfSuicide — Sat Jul 27, 2002 6:10 am