|
|
Joined: Mar 2006
Posts: 398
Pan-dimensional mouse
|
OP
Pan-dimensional mouse
Joined: Mar 2006
Posts: 398 |
When I ban someone with "ban -u" it doesn't automatically unban them. I'm sure the reason why it's not working is because im -o (chanmode), but I am oper - +o (usermode) It seems odd that it doesn't attempt to unban when i'm oper, regardless of current channel status, when the topic in channel central is unlocked Regards, JD. PS. http://www.mirc.com/forums.php is giving a HTTP 403 error at present.
[02:16] * Titanic has quit IRC (Excess Flood)
|
|
|
|
|
Joined: May 2010
Posts: 8
Nutrimatic drinks dispenser
|
|
Nutrimatic drinks dispenser
Joined: May 2010
Posts: 8 |
This is not a mIRC bug, but related to how IRCds work.
They require the user to be at least halfop to set and remove bans.
|
|
|
|
|
Joined: Dec 2002
Posts: 5,524
Hoopy frood
|
|
Hoopy frood
Joined: Dec 2002
Posts: 5,524 |
Thanks this is due to /ban not being consistent in checking whether you are an op/oper. I have changed this behaviour for the following commands: /ban, /pop, /omsg, /onotice, /wallop. These will now check whether you are either an op or an oper.
The auto-op/voice/protect features, which trigger only if you are an op, could also be changed in the same way - however I am not sure if that would be appropriate.
Also, the @ prefix for remote events, which triggers only if you are an op, could also be made to trigger if you are an oper - however, again, I am not sure if that would be appropriate.
Ps. The website was experiencing some issues yesterday - it looks like it is back to normal :-)
|
|
|
|
|
Joined: Mar 2006
Posts: 398
Pan-dimensional mouse
|
|
OP
Pan-dimensional mouse
Joined: Mar 2006
Posts: 398 |
Thanks this is due to /ban not being consistent in checking whether you are an op/oper. I have changed this behaviour for the following commands: /ban, /pop, /omsg, /onotice, /wallop. These will now check whether you are either an op or an oper. Thanks :-) The auto-op/voice/protect features, which trigger only if you are an op, could also be changed in the same way - however I am not sure if that would be appropriate. I'm not sure either. I would probably say it wouldn't be. Also, the @ prefix for remote events, which triggers only if you are an op, could also be made to trigger if you are an oper - however, again, I am not sure if that would be appropriate. Agreed - I definitely think this one wouldn't be (the @ prefix I would expect to have an @ specifically)[/quote]
[02:16] * Titanic has quit IRC (Excess Flood)
|
|
|
|
|
Joined: Mar 2006
Posts: 398
Pan-dimensional mouse
|
|
OP
Pan-dimensional mouse
Joined: Mar 2006
Posts: 398 |
This is not a mIRC bug, but related to how IRCds work.
They require the user to be at least halfop to set and remove bans. Hi enticore, I was specifically referring to a mIRC feature - Many servers will let an IRCoper unban a user even when they are not at least halfop in the channel
[02:16] * Titanic has quit IRC (Excess Flood)
|
|
|
|
|
Joined: Jan 2007
Posts: 1,156
Hoopy frood
|
|
Hoopy frood
Joined: Jan 2007
Posts: 1,156 |
Pertaining to whether @ should trigger for op AND oper. With the $nick identifier I can specify custom usermodes. A server I script for uses ', so to check for them I use $nick(#,$nick,').
It could be a solution to allow the prefixes to not be so fixed so that you can only use . or @ but instead be able to include non-formal usermodes. It sounds like it could cause issues or be too much of a pain to implement. But just in case I wanted to offer this idea.
Thank you.
|
|
|
|
|
Joined: Apr 2010
Posts: 969
Hoopy frood
|
|
Hoopy frood
Joined: Apr 2010
Posts: 969 |
I think khaled was speaking more for
on @*:....
|
|
|
|
|
Joined: Feb 2003
Posts: 3,432
Hoopy frood
|
|
Hoopy frood
Joined: Feb 2003
Posts: 3,432 |
The auto-op/voice/protect features, which trigger only if you are an op, could also be changed in the same way - however I am not sure if that would be appropriate.
Also, the @ prefix for remote events, which triggers only if you are an op, could also be made to trigger if you are an oper - however, again, I am not sure if that would be appropriate.
Maybe a option if you are a oper to turn it on/off? default should be off.
if ($me != tired) { return } | else { echo -a Get a pot of coffee now $+($me,.) }
|
|
|
|
|
