Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Raffaele Nntifrega]

Hi, i think anope needs a feature to stop flooding while clearing the channel.
Do more events on one line.
Example:
Instead of:

[25:61:13] * Bot sets mode: -b test!*@*
[25:61:14] * Bot sets mode: -b testt!*@*
[25:61:14] * Bot sets mode: -b testtt!*@*
[25:61:14] * Bot sets mode: -b testttt!*@*
[25:61:14] * Bot sets mode: -b testtttt!*@*
[25:61:14] * Bot sets mode: -b testttttt!*@*
[25:61:14] * Bot sets mode: -b testtttttt!*@*
[25:61:14] * Bot sets mode: -b testttttttt!*@*
[25:61:14] * Bot sets mode: -b testtttttttt!*@*
[25:61:14] * Bot sets mode: -b testttttttttt!*@*

Would be better:

 * Bot sets mode -bbbbbbbbbb test!*@* testt!*@* testtt!*@* testttt!*@* testtttt!*@* testttttt!*@* testtttttt!*@* testttttttt!*@* testtttttttt!*@* testttttttttt!*@*
Edited: ... errata corrige

[katsklaw]

Problem is this will rely on each individual IRCd since each one allows a different number of stacked modes. For example ircd1 only allows 3 stacked modes, ircd2 will allow 6 but only if they are the same type and only 4 modes of mixed types and so on. So that said changes to the conf parser, the ircd proto stuct and a revision to do_mode to say the least is called for. Which could result in a few hours of code changes at minimum.

A faster solution is if you have a lot of modes to change, do it yourself in your own client, not with services. Additionally, this isn't a flood of any kind. Yes, it's lines of mode changes, but that doesn't make it a flood.

PS: it's Anope, not Adobe.

[Robin Burchell]

This is planned eventually, but is not high priority.

Thanks!

[Raffaele Nntifrega]

Problem is this will rely on each individual IRCd since each one allows a different number of stacked modes. For example ircd1 only allows 3 stacked modes, ircd2 will allow 6 but only if they are the same type and only 4 modes of mixed types and so on. So that said changes to the conf parser, the ircd proto stuct and a revision to do_mode to say the least is called for. Which could result in a few hours of code changes at minimum.

A faster solution is if you have a lot of modes to change, do it yourself in your own client, not with services. Additionally, this isn't a flood of any kind. Yes, it's lines of mode changes, but that doesn't make it a flood.

PS: it's Anope, not Adobe.

Here is the raw sent on join from the IRCD:
TOPICLEN=308 KICKLEN=256 MAXTARGETS=20 AWAYLEN=201 CHANMODES=Ibeg,k,FJLfjl,ABCDGKMNOPQRSTcimnprstz FNC NETWORK=Anope MAXPARA=32 ELIST=MU EXTBAN=,SsMRmOTpNQrjcBA EXCEPTS=e CALLERID=g INVEX=I are supported by this server

as u can see MAXTARGET or MAXPARA should be the value, this message is an IRC standard (i mean that have to stay there ).

This is planned eventually, but is not high priority.

Thanks!

np 

P.S. i edited the first post with "anope"  ty

[Josh Johnson]

I don't think servers get that sort raw on connect/netburst... I don't know. I'll check that and post back.

Update: Apparently InspIRCd sends a command that's called `CAPAB` which has some of the capabilities of the server. (I completely forgot about this. ) I suppose it's completely possible with most/all IRCds with some protocol module edits; that is, if the Anope devs are up to it.

[deiks]

Well how about in some way:

if protocol is unreal use 12
else protocol is inspircd use 10
.
.
.