First of all, hi mIRC community!
So today, I downloaded the new mIRC client(7.14) and found an unpleasant surprise when I tried to use the built in /ban command.
* /ban: must be an op on #channelname
The command has always worked perfectly as a halfop on older versions of mIRC.
So I dug up the versions.txt and found this:


Are you sure this is the way it was meant to be? If it is then I am sorry, if not, please squash the annoying bug

Thank you,
-Kaur

There is a topic somewhere here (sorry, I don't want to try and find it right now) where Khaled said he planned to loosen that restriction. Not sure if the plan is for it to happen with the next release, though.

Seems like the search function isn't working on these forums...
After manually searching I was indeed able to find this topic on page 2 of threads.
https://forums.mirc.com/ubbthreads.php?ubb=showflat&Number=226779&page=2#Post226815



Thanks for your help

I don't think it's the client's place to decide what a user can and can't do on the channel. If I want to adjust the permissions in my channel to allow non-ops to set certain modes, why does the client need to stop this? It's perfectly acceptable for the client to let the server give the error message.

I agree.

That is how mIRC used to work long ago. However, over the last fifteen years users have requested all kinds of changes to the way mIRC behaves. The routines that handle the display of IRC server messages include numerous exceptions (in the many hundreds) that determine how or whether a server message is displayed based on server or network type, user modes, channel modes, message type, context, command history and so on. The same applies to many commands whether internal to mIRC or specific to IRC. It would certainly have been easier for me not to have created all of these exceptions, however I decided to implement them in situations where I thought it made sense for one reason or another. There are no plans to remove these exceptions at this time.