Page 1 of 1

Operscript (mute)

Posted: Sun Jul 30, 2006 10:17 am
by Alex

I'm quiet not sure if this is ther ight forum to post this question, but I try.

I'm using a opscript and I there have one for mute a single user in chat. My question is, would the code below work on Unreal 3.2.5 or has it to be re-written in one or another way :?:

Code: Select all

.Mute $snicks: {
    /onotice # 12(4Op Notice12)  13 Has Muted 4 $snicks- 13 on #
    /mode $snicks +z

.UnMute $snicks: {
    /onotice # 12(4Op Notice12)  13 Is Un-Muting 4 $snicks- 13 on #
    /mode $snicks -z
I'm not a scripter my self, so I wondered if someone here know what to do wit that code to get it work on Unreal 3.2.5.


Posted: Sun Jul 30, 2006 10:53 am
by Jobe1986
In Unreal you can mute a user 1 of 2 ways or both. You can either /shun the user or use and extened +b channel ban.

Unfortunatly the code youve provide will need to be modified to work with Unreal.

And not knowing exactly how the script works i dont know how to change the script to work. Sorry

Posted: Sun Jul 30, 2006 11:43 am
by Alex
Thanks for your reply Jobe1986. It was worthfull what you wrote, so maybe someone else that can scripting will look at it. However, any help have a value. :wink:

Posted: Sun Jul 30, 2006 1:42 pm
by Matridom
Some other/old servers had specific user modes in a channel that would ban "just them" The one i remember is +q from chatspace (this is going back years).

The answer has been giving up above, use shun or the +b ban. I would recommend using the +b ban as you won't need to be a netadmin, the user will be aware that they are "quiet banned" and you won't affect them on other channels.

I know mIRC scripting, but it's been a while, you'll probably want to change the script to something much simpler...

Code: Select all

.Mute .mode # +b $$1 4

Code: Select all

.Un-Mute .mode # -b $$1 4
The . instead of the / causes mirc to hide the command from you (so you don't see your client typing in /mode .....). You will still see the results of the command.

The '4' may need to change as it determins what mask is banned, check the mIRC scripting documentation to find the one that suits you best. Aslo, if you get creative, you can use Unreal's extended bans (~q for example) to get the exact results.

As for the Onotice, I don't know about you, but if an AOP was spamming me like that, they would be loosing their AOP pretty fast, i would recommend tossing the /onotice line completly.

Posted: Sun Jul 30, 2006 1:56 pm
by Alex
Thank you for your reply. As you said this mute command as I referred to was used on a server where I was an op on years ago, and it was made for IRCx.

Regarding to the onotice, we use the following which work perfect on Unreal3.2.5 without any modification:

I'll show you the code here and how it looks when using the following command on mIRC:

Code: Select all

Msg # OPs:/onotice # 12(Nick12) $$?="Enter message to ops:"
This is how it looklike when entered in chat to other ops:

[3:54pm] -> Ops #OpChat: (Nick) Test Message

so what I really type in mIRC is: /ops my message.

Posted: Sun Jul 30, 2006 3:08 pm
by Stealth
/onotice works on Unreal... All mIRC does is send "NOTICE @#Channel" to the server, and the server sends it to all the ops. Unreal supports this for all channel prefixes

Posted: Sun Jul 30, 2006 3:45 pm
by Matridom
Onotices definatly have their uses, as do other notices. What i was refering to was adding it to the existing command of a ban.

When a command like that get's issued, everyone in the channel can see it. So to me, it's stating the obvious, witch i find highly annoying.

Code: Select all

Msg # OPs:/onotice # 12(Nick12) $$?="Enter message to ops:"
if you where to make that..

Code: Select all

Msg # OPs:.onotice # 12(Nick12) $$?="Enter message to ops:"
you could get ride of this line '[3:54pm] -> Ops #OpChat: (Nick) Test Message '

I'm a stickler for clean interfaces..

Posted: Sun Aug 06, 2006 5:29 am
by aquanight
I could be mistaken but mirc by default has some idiotic /omsg and /onotice implementation that doesn't use statusmsg/wallchops at all (just directly /msg's all the ops).


Code: Select all

/omsg /.msg @#$1 $2-
/onotice /.notice @#$1 $2-

Posted: Sun Aug 06, 2006 12:41 pm
by White_Magic
aquanight is right, u need to alias it to do @#channel and the same with the other levels in the channel

Posted: Sun Aug 06, 2006 12:44 pm
by Jobe1986
Of course with UnrealIRCd 3.2.5 you could always set up aa alias to it in the config so every user can user it.

Posted: Mon Aug 07, 2006 4:57 am
by aquanight
Jobe1986 wrote:Of course with UnrealIRCd 3.2.5 you could always set up aa alias to it in the config so every user can user it.
No. As I said, mirc has its own /omsg and /onotice commands. Even if you define aliases in unreal's config, mirc will still use its own versions; all you will accomplish just letting everyone else who has a client that doesn't provide these two commands to use them. But mirc users must override them with a client-side alias.

Posted: Mon Aug 07, 2006 7:31 am
by Alex
Now wait a second. This mute script was not for everyone to use. It was made the way so only ops couold use it. When mute was set, it also was sent a oper pm to the other ops online in the same channel. So that means, you had to be opped up before you could use it.

Posted: Fri Aug 11, 2006 1:29 am
by aquanight
You still have to be op to use the /mode ...

Posted: Fri Aug 11, 2006 2:49 am
by Jobe1986
And just for safetys sake you can always use:

Code: Select all

if ( $me isop # ) { 
    /put commands here if you are op in the channel
That way you wont get ugly messages telling you that you are not op in the channel.

Posted: Fri Aug 11, 2006 12:19 pm
by Alex
aquanight wrote:You still have to be op to use the /mode ...
Yes that's right aquanight, but when I in the first place posted this, it was for a question how it could be used on an IRCd, since this script was made for IRCx which is totally different from IRCd. The IRCx that was used was a program for Windows.