UnrealIRCd Forums

<16:46:42> <[templar]> ny
<16:46:43> <[templar]> ???
<16:46:45> <[templar]> nu
<16:46:47> * irc.serv sets mode: +b *!*@87.226.15.94
<16:46:47> * [templar] was kicked by irc.serv (Flooding (Limit is 3 lines per 6 seconds))
<16:47:28> <_OTTO_> =]]]]]
<16:47:29> <_OTTO_> lol
<16:47:31> <Revo|ution> :D
<16:47:32> <_OTTO_> napiwi
<16:47:33> * irc.serv sets mode: +b *!*@195.244.132.50
<16:47:33> * _OTTO_ was kicked by irc.serv (Flooding (Limit is 3 lines per 6 seconds))
<16:47:50> <blacksheep> XD
<16:47:51> <blacksheep> XD
<16:47:52> <blacksheep> NICE

And this "blacksheep" wasn't kicked. Why?

Because Blacksheep was on the access list for the channel perhaps. I assume there is some sort of services involved there in which case Blacksheep could as i say be on the access list or be a superadmin on the services. I know with Anope if you are on the access list for a channel or have set superadmin on then flood protection like that wont affect you.

Is blacksheep an oper?

Did backsheep have voice or better?

backsheep is regular user in channel scope
backsheep is regular user in server scope
he has _the_same_ priveleges, then other ppls, that was banned.
Total amount of users on chan: 500+, on server: ~3'500

Because Blacksheep was on the access list for the channel perhaps.

Server don't know about user access list. It can't even imagine, that access list can exists in this world.

He probably just didn't go over the flood limit, the server recives the data (message's) sent from the client before anyone else would. so it was no doubt down to the person(s) sending over the allowed amount to the channel and it just not yet showin up on the channel, but the server recived it as a channel flood.

If ya think its a bug i would report it to bugs.unrealircd.com

judgin by the logs, simply they had +a or +q or +e
if they really did break the flood limit then the server would have kick banned them, as it did for the 2 before with no problems.

u/someone would need to test it on purpose to really see if there is a bug or not, a one off isnt enuff to say it is or isnt