UniOP Control

By UncleJohn on Oct 14, 2009

NOTE: Enter the network your going to use it on after the $network == line.

I made this because I wanted to be able to moderate any channel via right clicks, this includes the ability to moderate, and invite only a channel all using the right click menu.

Moderate, and invite show up in the channel right click menu, where all other controls show up when you click on a persons nick itself.

The PM Ignore feature is there because I know many of you get folks whining bout being banned via Query, this will let you simply right click on them and do a partial pm ignore only.

UPDATE: Added PM ignore feature to query menu.
UPDATE: Added nick info all, and a few pieces of help info.

Tested to work with NNS, and Mirc 6.35

;
; ------- SET VARIABLES --------
;
alias setvars {
  ;#$chan reasons
  set %channel.r.ban This isnt the place for you. 
  set %channel.r.kick If you want come back in, keep it up and you wont be welcome anymore.
  set %channel.r.silence Im giving you some time to think about why your silenced.
}
on 1:CONNECT:{ if ($network == GeekShed) { setvars } }
on 1:LOAD:/setvars
;
;
;
; ------- populate the right click menus --------
;
menu nicklist {
  -
  #$chan
  .Silence 
  ..User - 15 Minutes:{
    mode $chan +bb ~q: $+ $address($$1, 2) ~n: $+ $address($$1, 2)
    set %channel.silenceTime1 You have been silenced for 15 minutes.
    timer 1 3 /notice $$1 %channel.silenceTime1 %channel.r.silence
    timer 1 900 /mode $chan -bb ~q: $+ $address($$1, 2) ~n: $+ $address($$1, 2)
  }
  .Kick
  ..Kick ?:/kick $chan $$1
  ..-
  ..Kick the idiot:/kick $chan $$1 %channel.r.kick
  ..-
  ..Enter Custom Reason:{
    set %channel.prompt1 $$?="Enter the reason for the kick:"
    kick $chan $$1 %channel.prompt1
  }

  .Ban
  ..Get rid of the trash:{
    mode $chan +b $address($1, 2)
    notice $$1 %channel.r.ban
  }
  ..-
  ..Enter Custom Reason:{
    set %channel.prompt1 $$?="Enter the reason for the ban:"
    mode $chan +b $address($1, 2)
    msg $$1 %channel.prompt1 
  }
  ..-

  .Voice
  ..Voice User:{
    msg chanserv vop #$chan add $$1
  }
  ..-
  ..Del Voice:{
    msg chanserv vop #$chan del $$1
  }
  ..-

  .Op
  ..Add Op:{
    msg chanserv aop #$chan add $$1
    mode #$chan +o $$1
  }
  ..-
  ..Del Op:{
    msg chanserv aop #$chan del $$1
    mode #$chan -o $$1
  }
  ..-

  .Hop
  ..Add Hop:{
    msg chanserv hop #$chan add $$1
    msg chanserv halfop #$chan $$1
  }
  ..-
  ..Del Hop:{
    msg chanserv hop #$chan del $$1
    msg chanserv dehalfop #$chan $$1
  }
  ..-

  .Nick Info
  ..Check:{
    ns info $$1 all
  }
  ..-

  .PM Ignore
  ..Ignore PM:{
    ignore -pn $address($$1, 2)
  }
}
..-
menu channel {
  #$chan
  .Mod
  ..Lock:{
    mode $chan +m
  }
  ..-
  ..Unlock:{
    mode $chan -m
  }
  .Invite
  ..Lock:{
    mode $chan +i
  }
  ..-
  ..Unlock:{
    mode $chan -i
  }
  ..-

  .help
  ..Group:{
    msg #$chan If you would like to group another nick to your main registered nick, please type /msg nickserv group <main nick> <password>
  }
  ..hostmask:{
    msg #$chan If your hostmask is not resolving, it is most likely due to port 113 being blocked on your router, this port needs to be open for identd to set your hostmask properly.
  }
  ..-
}

menu query {
  .PM Ignore
  ..Ignore PM:{
    ignore -pn $address($$1, 2)
  }
}

Comments

Sign in to comment.
Hawkee   -  Mar 16, 2010

UncleJohn, that was just a temporary bug, it's been fixed.

 Respond  
Jethro   -  Mar 16, 2010

This is the first time I see an identifier placed with $chr(35) like this:> #$chan

 Respond  
napa182   -  Mar 16, 2010

click edit uptop to update it.

 Respond  
UncleJohn   -  Mar 16, 2010

Hawkee I cant! I tried, it just says "This snippet already exists" and then asks me to view it.

 Respond  
Hawkee   -  Mar 15, 2010

I removed your duplicate snippet. Please update this one.

 Respond  
UncleJohn   -  Oct 16, 2009

Firstly, because combining +m and +i is not a good thing 99% of the time, the reason to go +m is to shush trouble makers in the channel while you ban them..etc +i is only if there is a larger issue.

Secondly, because adding $+ is completely and utterly not needed in #$chan line. I have tested it on NNS and 6.35, and others have on 6.34 and not had any issues.

 Respond  
Cracker200   -  Oct 15, 2009

n lol

  msg chanserv vop #$chan add $$1
  msg chanserv vop # $+ $chan add $$1

=D

 Respond  
Cracker200   -  Oct 15, 2009

But why not do...

 menu channel {
  #$chan
  .Mod
  ..Lock:{
    mode $chan +m
  }
  ..-
  ..Unlock:{
    mode $chan -m
  }
  .Invite
  ..Lock:{
    mode $chan +i
  }
  ..-
  ..Unlock:{
    mode $chan -i

menu channel {
  #$chan
  .Mod
  ..Lock:{
    mode $chan +mi
  }
  ..-
  ..Unlock:{
    mode $chan -mi

? o.O

 Respond  
Cracker200   -  Oct 15, 2009

Lolol nice =D

 Respond  
Are you sure you want to unfollow this person?
Are you sure you want to delete this?
Click "Unsubscribe" to stop receiving notices pertaining to this post.
Click "Subscribe" to resume notices pertaining to this post.