Anope IRC Services

Anope Development => Feature Requests => Topic started by: SNU on July 15, 2007, 07:45:16 PM

Title: Unreal 3.2.7 and Mode +L
Post by: SNU on July 15, 2007, 07:45:16 PM

Hi.

Maybe you know, but
UnrealIRCD has announced a new Version of its IRC-daemon with Version 3.2.7

One of its changes is:

Quote

chmode +L does no longer require chmode +l

I tried it and it works fine. But Anope still says it requires mode +l
Maybe you can change here something for futher Versions or make a module that overrides several restrictions for Unreal 3.2.7 and further.

I know theres a problem... but maybe services could do a svsjoin followed by a kick on the +L'ed chan for that user which enters that chan. I know. Its not the finest method but it would be near the wish ,having permanent channel-links.

Thanks so far.

[Bearbeitet am 15-7-2007 von SNU]

Title:
Post by: Jobe on July 15, 2007, 09:47:03 PM

SNU, did you know you can use deny channel blocks to redirect users.

Title:
Post by: SNU on July 15, 2007, 10:34:01 PM

arrr... now I remember ^^

but... maybe it still could be possible to set a mlock +L #chan  what means for services automatically set "+l 1" when no +l is specified.

but thanks for that hint jobe1986

Title:
Post by: Jobe on July 16, 2007, 01:06:06 PM

I have to say I agree with you on the +l requirement. However, what happens if Anope drops the restriction, and someone uses Anope on a network running Unreal 3.2.6 or lower?

Title:
Post by: SNU on July 16, 2007, 07:58:46 PM

Quote

Jobe1986
...what happens if Anope drops the restriction, and someone uses Anope on a network running Unreal 3.2.6 or lower?

Yeah. Lets wait what changes in future versions of Unreal. As I noticed Unreal4.0 is coming nearer to be being usefull (stable). maybe Anope needs some restructuring... But what you mean, could be set by:
"IRCDModule" at the beginning of the conf. But Anope surely needs an "update"...

Title:
Post by: casper1256 on July 16, 2007, 08:39:35 PM

As far as I know there is a bug reported that +L won't work properly without +l in 3.2.7. (I'm not sure though). If that's true, there's absolutly no need for it now ;)

Title:
Post by: owine on July 17, 2007, 04:56:25 PM

Quote

Originally posted by Jobe1986
I have to say I agree with you on the +l requirement. However, what happens if Anope drops the restriction, and someone uses Anope on a network running Unreal 3.2.6 or lower?

I'm not sure how the Anope protocol modules work, but I know the protocol and IRCd version is synced during a burst in UnrealIRCd so that could be parsed and support altered depending on the version of Unreal the user is running.

Title:
Post by: katsklaw on July 17, 2007, 11:32:05 PM

The problem here is that Unreal3.2.7 was released *AFTER* Anope-1.7.19 so obviously there is no support for it. Anope has yet to release another version since Unreal added this new feature.

Since we are currently under a feature freeze it's possible that it may be a while before Anope supports the new feature. It's also possible, but please don't hold your breath, that it will be added before the next release.

In plain English, we haven't had time to react to this new feature.