egghelp/eggheads community

Another question about CTCP/DCC problem (the real one)

2008-02-26T15:39:29-04:00

Tried it in the latest cvs and worked fine for me. Are you sure you have set net-type correctly?

I used the same config file with 1.6.18 and cvs. So this shouldn't be a net-type issue. I will try now the latest cvs, too. I'll tell you about the results.

Edit: With the latest cvs eggdrop v1.6.19+tclver there is no problem. Thank you!

Statistics: Posted by BaS — Tue Feb 26, 2008 3:39 pm

Another question about CTCP/DCC problem (the real one)

2008-02-24T17:57:03-04:00

Tried it in the latest cvs and worked fine for me. Are you sure you have set net-type correctly?

Statistics: Posted by strikelight — Sun Feb 24, 2008 5:57 pm

Another question about CTCP/DCC problem (the real one)

2008-02-24T06:14:41-04:00

Rollback to official 1.6.18 has helped.

Statistics: Posted by BaS — Sun Feb 24, 2008 6:14 am

Another question about CTCP/DCC problem (the real one)

2008-02-22T12:06:42-04:00

Hello guys,

I have eggdrop v1.6.19+updates (taken from cvs).

I ran into problems with CTCP requests to bot.

It seems that a bot does not recognise what kind of CTCP it recieves.
This is what being shown in telnet session when someone requests a CTCP VERSION from bot:

Code:

CTCP :  from barmoley (~people@host)

While normally this should be like this:

Code:

CTCP version:  from anaesthesia (~-@host)

This is happening to all kinds of CTCP requests.

In config:

Code:

loadmodule ctcpset ctcp-mode 0set ctcp-version "BaS's BOT-16"set ctcp-userinfo "BaS's BOT-16"set ctcp-finger "BaS's BOT-16"

In reply to .module:

Code:

Module: ctcp (v1.0)

Could you please help?

Statistics: Posted by BaS — Fri Feb 22, 2008 12:06 pm