Anope IRC Services
Anope Development => Feature Requests => Topic started by: Swampy on May 29, 2009, 09:30:28 PM
-
Can 1.9 be made to support the following functions: (Config examples marked with *)
NickName No Expire Mode for Services Roots/Admins (like you currently have on channels) - Example: /NickServ Set NoExpire [ON | OFF]
* NickNameNoExpiry [ENABLE | DISABLE]
---
328 RPL_CHANNEL_URL (most services, such as atheme support this outta the box, maybe even have an additional ChanServ option to enable/disable: /CS SET #CHAN SHOWURLONENTRY [ON | OFF]
* RPLChannelURL [ON | OFF]
* RPLNumericNumber [328 | 999]
* RPLChannelURLString [%s %s %s] or [%s Channel URL for %s is %s] depending on how users want it to be shown.
---
Auto-Owner Functionality:
If option is enabled, the AutoOwner level should be settable by /CS LEVELS #CHAN SET AUTOOWNER value
* AutoOwnerMode [ENABLED | DISABLED] - This would either enable or disable the whole AutoOwner System.
* AutoOwnerXOP [ENABLED | DISABLED] - If enabled, this would give you an QOP list (Auto Owner List) to add/delete names to/from
---
*edit*
Storing the full nick!ident@host in topic if the IRCd supports it (eg. InspIRCd), Currently anope only stores nickname of the user in the database, Maybe will need a configuration option, eg. TopicShowsIdentHost [ON | OFF]
*edit*
I hope you will consider these ideas, or at least have modules for them made,
Many Thanks.
-
For the nickname no expire mode, we already have that as planned for a future edition of 1.9.x. (Although it's an up-in-the-air thing, it seems):
[?] Don't allow soper accounts to expire
We could probably look into the RPL_CHANNEL_URL one.
This isn't in TODO, but I know we've talked about reworking the levels system for ChanServ, which would negate the need for the last one. We'll have to see.
Also, if you want modules made, you have to ask module authors. We work on the core, not on modules specifically.
-
Thanks for replying
Oh and one I did forget above: ChanServ set Guard ON|OFF would be useful as well
-
You'll have to explain that one, although if it's what I'm thinking I've heard before, it's not useful because of BotServ already handling things.
-
Well as far as I'm aware, /ChanServ Set Guard ON
1) Forces ChanServ into the channel
2) Stops Operators Giving Rights to non-access/xOP list users
3) Protects against Channel Modes being changed
I think atheme does this and theia version 0.94 does this as default.
-
We'll probably have to look into it.