egghelp/eggheads community

Need codes :)

2001-12-01T05:03:00-04:00

Ok, alright. Got it.
I changed the code to

set away [lindex $areas [rand [llength $areas]]]
set aaway ${away}
putserv "AWAY :$aaway"
}

It works perfectly now Thanks for all the help guys

Statistics: Posted by Guest — Sat Dec 01, 2001 5:03 am

Need codes :)

2001-12-01T04:50:00-04:00

Ok, i've changed it to init-server.
It's working fine, except, it has one problem now.

set areas {
{1 away reason here}
}

It is only able to display the reason 1. Not the rest of the line. Any ideas?

Statistics: Posted by Guest — Sat Dec 01, 2001 4:50 am

Need codes :)

2001-11-30T17:39:00-04:00

personally I prefer binding these kinds of events to raw 001, though when you do that you gotta be 101% sure it ain't gonna return 1 and stop the bot noticing its connected.

Statistics: Posted by Petersen — Fri Nov 30, 2001 5:39 pm

Need codes :)

2001-11-30T15:58:00-04:00

EEK - yup

Statistics: Posted by ppslim — Fri Nov 30, 2001 3:58 pm

Need codes :)

2001-11-30T15:46:00-04:00

connect-server is triggered when eggdrop starts connecting to the server. Using init-server would better suit what you are trying to do, as it triggers once connected.

Statistics: Posted by Wcc — Fri Nov 30, 2001 3:46 pm

Need codes :)

2001-11-30T13:11:00-04:00

OK - part 1.

change

putserv "AWAY [lindex $areas [rand [llength $reas]]]"

putserv "AWAY [lindex $areas [rand [llength $areas]]]"

You will see 2 lines the same in the script, change both.

As for the connect-server script not working, add a putlog line in the script, see it that proves the script is being called.

Some IRC server set you as returned upon the first receiveing the first non-automated command fromt he client. A auto-mated command is classed as somthing that should be returned automaticaly byt he client, like a ping. This maybe causing the problems.

If the putlog line is displayed, then yes, this is the problem.

Statistics: Posted by ppslim — Fri Nov 30, 2001 1:11 pm

Need codes :)

2001-11-30T05:43:00-04:00

err ppslim,

the code doesn't seems to work. The bot doesn't set itself away on-connect. There's no tcl error though ..

Statistics: Posted by Guest — Fri Nov 30, 2001 5:43 am

Need codes :)

2001-11-29T06:39:00-04:00

[ This Message was edited by: galaxyboy on 2001-11-30 02:43 ]

Statistics: Posted by Guest — Thu Nov 29, 2001 6:39 am

Need codes :)

2001-11-28T11:57:00-04:00

It is easy to make it set itself away on connection to the server.

It's not easy to set itself away on netsplits though. Not all servers provide a detectable netsplit message. It will be allmost imposible to detect them if no1 getting lost in the split is in the room.

Here is the code to the current detectable way

Code:

set areas {{1 away reason}{another away reason}{think of some more}}bind evnt - "connect-server" away:connectproc away:connect {t} {  global areas  putserv "AWAY [lindex $areas [rand [llength $reas]]]"}bind splt - "*" away:splitproc away:split {nick uh hand chan} {  global areas  putserv "AWAY [lindex $areas [rand [llength $reas]]]"}

This only marks the bot as away. There was nothing noted as to when it should be marked as returned.

Statistics: Posted by ppslim — Wed Nov 28, 2001 11:57 am

Need codes :)

2001-11-24T05:39:00-04:00

Hi,

Is there anyway to code this script such that it will set bot to be autoaway with preset reasons upon connected to the IRC Server? Next, is there anyway to make it set autoaway if there's a netspilt?

If it's possible, how can it be done? Can someone kindly do some coding on it?

Thanks

Statistics: Posted by Guest — Sat Nov 24, 2001 5:39 am