egghelp/eggheads community

control $idx command

2003-09-06T06:39:15-04:00

thx :>

Statistics: Posted by Guest — Sat Sep 06, 2003 6:39 am

control $idx command

2003-09-05T19:01:28-04:00

Once you have control over a DCC session, you can do plenty of things.

However, there are four things you can do at the end of your control proc.

1: Retain control over the session

2: Pass control over to another proc.

3: Return control back to eggdrop, at which point they are on the partyline again.

4: Use "killdcc" to kick the user off the partyline.

I wouldn't recommend doing #2 .. Eggdrop has problems freeing sockets that are passed beyond a single control proc... Mainly because there is no sense in having multiple controls for a single idx when all can be written within the one procedure.

Statistics: Posted by strikelight — Fri Sep 05, 2003 7:01 pm

control $idx command

2003-09-05T12:40:03-04:00

Once you have control over a DCC session, you can do plenty of things.

However, there are four things you can do at the end of your control proc.

1: Retain control over the session

2: Pass control over to another proc.

3: Return control back to eggdrop, at which point they are on the partyline again.

4: Use "killdcc" to kick the user off the partyline.

Statistics: Posted by ppslim — Fri Sep 05, 2003 12:40 pm

control $idx command

2003-09-05T11:51:15-04:00

I need an example for control $idx :/

i have tryd

Code:

bind dcc - login pl:logproc pl:log {handle idx text} {control $idx te:con}proc te:con {idx text} {putdcc $idx "test" }

but we can i make to logout ?

Statistics: Posted by Guest — Fri Sep 05, 2003 11:51 am