try:x3teamz wrote:I was wondering if I could request a module for helpop status. I would like my helpops to be able to use /kill and have the swhois "is a Help Operator" without having to give them an o:line or services access. If this can't be made a module, consider this a feature request O_o
Code: Select all
/helpop ?SVSO
Code: Select all
[14:48:02] -irc.*- *** Notice -- shadownight ([email protected]) is now a local operator (o)
[14:48:03] * shadownight sets mode: +wghOWq
Server notice mask (+kcfFjveGnqsU)
You are now an IRC Operator
*snip OPERMOTD*
// Attempt to use /kill on self here.
Permission Denied- You do not have the correct IRC operator privilegesCode: Select all
oper Test {
from {
userhost *@*;
};
password "test";
class Client;
flags {
helpop;
};
maxlogins 1;
};
What's to fix? If I didn't specify any of the local/global/etc flags, why should I get any of the privileges they provide? If I only have helpop, then fine, I'm only a helpop - I get +h and that's it (+O too but I guess that's needed for deopering) - I only see when people do /helpop stuffs, no extra privileges or anything. If all I have is helpop then that's how it should beStealth wrote:Now codemastr is gonna go fix it
.[12:45] <codemastr> if that's the case, then it is a bug
[12:45] <aquanight>
[12:45] <codemastr> helpOP requires you to be an OP, hence the name
[12:54] <Stealth> how else can my official helpers see /helpop
[12:54] <codemastr> they have no reason to see it! That's my whole point!
[12:55] <codemastr> /helpop is meant to ask for OPER HELP
I agree, I like the idea of positively identifying helpops via the /whois .. who said that the ops in helpops must refer to IRCops? .. it can mean Help Channel Ops?aquanight wrote:What's to fix? If I didn't specify any of the local/global/etc flags, why should I get any of the privileges they provide? If I only have helpop, then fine, I'm only a helpop - I get +h and that's it (+O too but I guess that's needed for deopering) - I only see when people do /helpop stuffs, no extra privileges or anything. If all I have is helpop then that's how it should beStealth wrote:Now codemastr is gonna go fix it
Besides it's already a conf setting that help channel ops can get +h anyway.I did, and so did DALnet, the people who created +h.who said that the ops in helpops must refer to IRCops?
Umm, no there isn't. Please show me this option.Besides it's already a conf setting that help channel ops can get +h anyway.
The type of help helpops are to provide DOES require an oline. "Hi, I'm klined, why?" "I can't tell you, I'm not an oper." "I lost my nickserv password, can you get it?" "I can't help you, I'm not an oper." It has NOTHING to do with general help.Last I checked helping users didn't require an o flag
No harm, just needless bloat. I have NO intention of doing this. Why does someone who provides help need to be a helpop? They don't. How many users actually use /helpops or even know the command exists as a method to send a message to +h users? If they knew this, then they'd probably be smart enough to solve a general issue on their own!Where is the harm in letting password protected access to /helpops?
My bad, it's an Anope conf setting.Umm, no there isn't. Please show me this option.Besides it's already a conf setting that help channel ops can get +h anyway.
