Wallop

[PurplePants]

Trying to get the bot to see wallops thus:

Code: Select all

bind WALL - * do_wallop

proc do_wallop {handle msg} {
    putlog "Wallop: handle = $handle"
    putlog "Wallop: msg = $msg"
    return 1
}

Nothing at all happens. Nor does ACT appear to achieve anything. Is there something I'm missing? This is Windrop v1.6 if that makes a difference.

[caesar]

Is he/she using +w usemode?

[PurplePants]

Ah! That could be it 'cos I have no idea what +w is all about .

/me is off to find something to read, but if you feel the urge to elaborate I'd be very appreciative...

[caesar]

in the .conf file should be something like this: set init-server { putserv "MODE $botnick +i-ws" } (at least at me is like this.. change to +iw-s and should work smoothly.

[PurplePants]

Thanks for that - easy to miss

Strange. It was +i-ws so I changed it to +iw-s and then +iws just for the hell of it. Still nothing.

[caesar]

After you have changed the +iw thing, have you .restart-ed the eggdrop?

[PurplePants]

Oh yes, complete shutdown and restart.

[caesar]

Still nothing?

[PurplePants]

Not a peep

I'm gonna try sending the MODE thingy once the bot is online and settled down, just to make sure.

[PurplePants]

Gah!

Put it on a bind so I could trigger it on command. Tried "MODE ...", ":MODE ..." and "$botnick MODE $botnick ..."

Nothing worked. Did the same with another bot (similar but different .conf). Took out all scripts that weren't the base set. Nothing

Now I'm thinking of a bind RAW - * to see what's coming up from the server, but I don't know that it would get me any closer to figuring what's up.

[ppslim]

What exactly have you place in the "init-server" setting?

There are setting in the config file, that allow you too see these raw messages (so long as you then enable the correct console flags) going to and coming from the server.

[PurplePants]

Code: Select all

set init-server { putserv "MODE $botnick +iws" }

The other bits I mentioned ("put on a bind") I had a PUBM bind where I could type !stuff and it would then do this:

Code: Select all

putserv "MODE $botnick +iws"

That was in case the init-server thing wasn't successful for some reason.

[ppslim]

My best sugestion would be to enable the server debug settings in the config file, enable your console flags to accomodate them, then follow this.

type ".dump MODE <botsnickname> +iws" in the partyline

You should see what is sent to the server, and what is returned.

Type ".dump MODE <botsnickname>" without he modes, and the server should return the current modes.

Now you should wait, and see if any messages are sent.

If you see nothing, it's a server issue, and is beyond our scope.

[PurplePants]

I added every flag there was mkjpsbcxrow

Code: Select all

[23:47] [@] PurplePants!~purplepan@dunkers.gotadsl.co.uk PRIVMSG #antibottersinc
 :ACTION slaps ABITest around a bit with a large trout
[23:47] Action: PurplePants slaps ABITest around a bit with a large trout
.dump MODE ABITest
[23:47] #PurplePants# dump MODE ABITest
[23:47] [@] blueyonder4.uk.quakenet.org 221 ABITest +iw

That first one was me slapping the bot. The proc I posted right at the start wasn't triggered (at least, there was no log output).

Silly question, but is there something in the compile time that can disable this sort of stuff?

[ppslim]

What sort of stuff? If you mean the ability to use those console flags, to view all in and out traffic, the yes/no.

There is no compile time flag, however, there is a config file setting to disable it.