Invalid modes that DO exist

DJ747 · Post by **DJ747** » Sat Nov 20, 2004 1:25 pm

I'm trying to set my bot to force the mods +ntCT The bot is on an Unreal3.2.2 server and all those modes exist but it told me: "Error trying to set +ntCT for #DJ747, invalid mode." Yes those are all REAL modes, i tried them out myself, anyone have any ideas on how to make my bot think they are real?

greenbear · Post by **greenbear** » Sat Nov 20, 2004 3:03 pm

Make sure the 'net-type' setting in your config file is correct.

demond · Post by **demond** » Sat Nov 20, 2004 3:11 pm

net-type is irrelevant to his problem, it's merely a switch setting other ircd-specific vars, but not valid chanmodes

valid chanmodes should be obtained from server numeric 005 (ISUPPORT) reply, as does mIRC; afaik eggdrop doesn't do this

demond · Post by **demond** » Sat Nov 20, 2004 3:33 pm

enforce +nt and try this:

Code: Select all

bind mode - "% -C" enforce
bind mode - "% -T" enforce
bind mode - "% +o" enforce
proc enforce {n u h c m v} {
  if {$m=="+o" && [string compare -nocase $v $::botnick]} return
  putserv "mode $c +CT"
}

DJ747 · Post by **DJ747** » Sat Nov 20, 2004 8:38 pm

CHANMODES=be,kfL,l,psmntirRcOAQKVGCuzNSMT <-- there is C and T in the chanmodes, maybe my eggdrop can't read the line properly? Or is this thing internal?

greenbear · Post by **greenbear** » Sun Nov 21, 2004 12:05 am

Hmm, the only way i get the eggdrop to report invalid mode is if a use a incorrect syntax. Make sure you set channel modes with

.chanset #channel chanmode +ntCT

demond · Post by **demond** » Sun Nov 21, 2004 12:24 am

DJ747 wrote:CHANMODES=be,kfL,l,psmntirRcOAQKVGCuzNSMT <-- there is C and T in the chanmodes, maybe my eggdrop can't read the line properly? Or is this thing internal?

this is part of a string that your irc server sends to you (or to your bot, or to anyone for that matter) when you connect to it - so called ISUPPORT reply - server numeric 005 (it can also be obtained when you /version the server)

your mIRC client reads and interpret it; your eggdrop doesn't - thus the unknown modes your bot is complaining about

the only way to make the eggdrop aware of it is to write a script which binds raw to numeric 005 and interprets it - but you still can't teach the bot about those modes that are unknown to it

so mIRC and some other clients (irssi?) have an advantage over eggdrop on this particular feature

greenbear · Post by **greenbear** » Sun Nov 21, 2004 12:49 am

/me still think he just messed up the .chanset syntax

demond · Post by **demond** » Sun Nov 21, 2004 1:12 am

gb wrote:/me still think he just messed up the .chanset syntax

probably so, but even if you issue the correct command, eggdrop - unlike mIRC and other clients - still won't recognize and enforce modes that it doesn't know about

greenbear · Post by **greenbear** » Sun Nov 21, 2004 1:22 am

That might be, but eggdrop wont return a error, unless you have a raw bind on it.

Alchera · Post by **Alchera** » Sun Nov 21, 2004 12:09 pm

Are those two particular flags actually available for normal users? Some modes can only be used by IRCops.

DJ747 maybe paste (from your conf) the chanmode setting you have. It could just be a syntax error.

awyeah · Post by **awyeah** » Sun Nov 21, 2004 12:39 pm

Try doing this in DCC lets see if it works.

(Make sure your dcc:tcl unbind is commented in the .conf file)

Code: Select all

.tcl putserv "MODE #channel +TC"

greenbear · Post by **greenbear** » Sun Nov 21, 2004 1:40 pm

It's a syntax issue, no point in beating this thead to death.

<gb> .chanset #gb +wrong_syntax
<G> Error trying to set +WRONG_syntax for #gb, invalid mode.

<gb> .chanset #gb chanmode +CORRECT_syntax
<G> Successfully set modes { chanmode { +CORRECT_syntax } } on #gb.

The error msg with the wrong syntax is the same as DJ747 got.

And the eggdrop also don't return anything, legal mode or not, if the syntax is correct.

EOF