| View previous topic :: View next topic |
| Author |
Message |
BaS
Voice
Joined: 30 Jan 2008
Posts: 6
|
 Posted: Fri Feb 22, 2008 12:06 pm Post subject: Another question about CTCP/DCC problem (the real one) |
 |
|
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 ctcp
set ctcp-mode 0
set 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? |
|
| Back to top |
|
 |
BaS
Voice
Joined: 30 Jan 2008
Posts: 6
|
| Posted: Sun Feb 24, 2008 6:14 am Post subject: |
|
|
| Rollback to official 1.6.18 has helped. |
|
| Back to top |
|
|
strikelight
Owner
Joined: 07 Oct 2002
Posts: 708
|
| Posted: Sun Feb 24, 2008 5:57 pm Post subject: |
|
|
| Tried it in the latest cvs and worked fine for me. Are you sure you have set net-type correctly? |
|
| Back to top |
|
|
BaS
Voice
Joined: 30 Jan 2008
Posts: 6
|
| Posted: Tue Feb 26, 2008 3:39 pm Post subject: |
|
|
| strikelight wrote: | | 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! |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
