[an error occurred while processing this directive] [an error occurred while processing this directive]
Op/Voice Information .....

Bans - Mask Types and Setting Bans

[ Page 1 ]    [ Page 2 ]    [ Page 3 ]    [ Page 4 ]


Setting Bans

KICKS AND WARNINGS

Our channel policy is not to kick without warning the user at least two times. We can send our warnings via notice so we don't flood the channel. We can also ping the users so we are sure they've got our warning .

Example of a private warning:
     /df /notice $$1 please don't flood the channel, it is highly annoying, thx. | /ping $$1

Thats an example of one warning via notice, we add the ping so we are sure the user got our warning and they are not lagged.

The command line to kick one user from channel is : /kick #channel nick reason

Reason is very important because the user must know why he/she has been kicked out of the channel.

You can have this line in your aliases: /k /kick # $$1 $2-
     so we type: /k nick reason


CHANNEL BANS

The command line for a channel ban is:
     /mode #beginner +b nick/ip
     /ban #beginner nick/ip masktype

We can complicate things a little bit adding a timer to this second line. Timers goes in seconds and it goes this way:
     /ban -u300 #beginner nick 3 .... that's a five minutes ban.

To kick and ban one user , we first ban it and then kick it, this is the way, you can add this line into your aliases:
     /kb /ban # $$1 3 | /kick # $$1 $2- (that $2- is for the required reason)
     /kb5 /ban -u10 # $$1 3 | /kick # $$1 $2- (this is a 5-sec ban, it avoids the rejoin after the kick)

Sometimes you have seen a duct-tape ban in action, if a user (not wearing the @) is banned in the channel but not kicked they won't be able to send a msg to channel or change nick -- that's the duct tape ban. I'm sure you wonder how do we do that. Well, we take advantage from a little tip, when a regular user is banned but not kicked (as long as they are not wearing a @) they are not able to talk in channel, or change their nicknames. So we just ban them with a 5-min timer, it's a very handy tool, believe me :o .

This is the line I use:
     /dtb /ban -u300 $chan $$1 3 | /notice $nick $$1 You have been been silenced for 5 minutes I hope this makes you change your attitude. | /say $$1 has been silenced for 5 minutes.(duct tape ban)

In that ban the user and the channel are both informed as to 'why' the user was removed.

Here are some more examples of how we might ban someone. Something to remember, all we have been discussing so far only bans a person, it doesn't kick them, or remove them from channel. You'll want to add that command to the aliases with a | separating the command lines.

For example, if I wanted to both kick and ban out a person from channel, a standard line would look like this:
     /kb /ban # $$1 $2 3 | /kick # $$1 $2-

Using that ban shown above, to kick/ban someone out of #Beginner, we would type:
     /kb nickname reason

Example:
     /kb bossmom Flooding

Would look like this:
     *** bossmom sets mode: +b *!*bossmom@*.dialup.netins.net
     You were kicked from #bossmom by bossmom ( Flooding )

Not that anyone would really do that on purpose :)


CHANNEL BAN LIST

Channel ban list has a capacity of 30 bans. To access it we double click on main channel window, or type /channel, or right click on main window and then click on channel modes .

We must clean up the list from time to time so we have room to more bans. To remove the bans we highlight them and click on unban and apply changes.

Which bans do we remove first?
     1-Server bans
     2-X bans (as long as X is with us and we have a good ping reply from him)
     3-Older bans


USER LIST

We can keep a userlist, with the IP's of the ops and vees. Most of our scripts are set to act against level 1, which is the default level. If we add a level over 1 to our friends we protect them from our scripts. We use level 5 for +V's, and level 10 for Ops.

Not everyone use the same access levels, you can use whatever level you prefer, or even a named level like 'ops' or 'voices'. The user list is located in our mirc editor ( alt+r ) and then go to users label.

Once in a month, or sometimes sooner, all the ops/voices receive an updated op-v-ip.txt. It's the list of current ops and voices in #beginner. To easily modify this text, you can open it via wordpad, and do a search & replace the *!* to 10:*!*, and then just change the vees to 5:*!*.

You can also use a wonderful script made by Alk that can be downloaded here. Memoe has also written a script file that helps keep our user lists updated, and you can download it here. Either are very easy to use. Please download either (or both) files, and there will be instructions inside the zip, or inside the .mrc file, telling you what steps you'll need to take.

You can also use the /guser and /ruser commands of our mirc. The first one add a nick with an specified level into your userlist, the second one removes that user from your userlist.

I have two aliases that can become very handy sometimes :
     /addu /guser $?=level $?=nick 3 (adds an IP to our user list)
     /nou /ruser $?=level $?=nick 3 (removes an IP from our user list)



[ Page 1 ]    [ Page 2 ]    [ Page 3 ]   [ Page 4 ]


 


[an error occurred while processing this directive]
[an error occurred while processing this directive]