Mode +f, Not working as described...?

These are old archives. They are kept for historic purposes only.
Post Reply
Dmnchild
Posts: 2
Joined: Thu Jul 17, 2014 7:23 am

Mode +f, Not working as described...?

Post by Dmnchild » Thu Jul 17, 2014 7:31 am

Greetings. After reading documentation, and searching forums, I did not see this issue brought up.

/mode +f [7j#i2,30t#m2]:15

This seems that it should work based on documentation. But when I use this, It sets:

mode +f [7j#i2,30t]:15

So it seems there is no event to happen after the 30t in the time frame. Just curious if I am overlooking something in to documentation, or if this is just flawed?

I am running Unreal3.2.10.2

Dmnchild
Posts: 2
Joined: Thu Jul 17, 2014 7:23 am

Re: Mode +f, Not working as described...?

Post by Dmnchild » Thu Jul 17, 2014 10:03 am

After testing, I guess this is not indeed its correct usage. Though I wish it was. While kicking people exceeding the msg limit helps, 10t#m2 if it would work would be better in situations where the users can just rejoin.

Jobe1986
Official supporter
Posts: 1180
Joined: Wed May 03, 2006 7:09 pm
Location: United Kingdom

Re: Mode +f, Not working as described...?

Post by Jobe1986 » Thu Jul 17, 2014 5:53 pm

It is possible that the fake lag implemented by most IRCds including UnrealIRCd would artificially delay enough of the 30 messages to prevent them all being parsed within 15 seconds. Most people find smaller numbers work better but ofc it does take some tweaking.
Your IP: Image

Syzop
UnrealIRCd head coder
Posts: 1927
Joined: Sat Mar 06, 2004 8:57 pm
Location: .nl
Contact:

Re: Mode +f, Not working as described...?

Post by Syzop » Sun Jul 20, 2014 7:49 pm

't' is messages from one individual and only supports kick or ban
'm' is total messages from everyone
See also /HELPOP ?CHMODEF for all types and the available actions and the m/t difference:

Code: Select all

The +f channel mode provides comprehensive flood protection for a channel.
This mode allows you to prevent join, nick change, CTCP, text, and knock
floods. The syntax for this mode's parameter is as follows:
-
+f [<amount><type>{#<action>}{,...}]:<seconds>
-
The amount specifies the number of times the specified flood must occur
before action is taken. Below are the available types:
-
==-----Type-----Name--------Default Action---Other Actions-----==
       c        CTCP        +C               m, M
       j        Join        +i               R
       k        Knock       +K
       m        Messages    +m               M
       n        Nickchange  +N
       t        Text        kick             b
-
The difference between type m and t is that m is tallied for the entire
channel whereas t is tallied per user.
-
If you choose to specify an action for a mode, you may also specify a
time (in minutes) after which the specific action will be reversed.
-
't' with action +m makes no sense, but 'm' with action +m is logical.
So instead of /mode +f [7j#i2,30t#m2]:15 you probably want /mode +f [7j#i2,30m#m2]:15

Don't worry about the mistake, it's a complicated channel mode. Very powerful, though.

Post Reply