Being a 400+op is based on much more than just IRC knowledge.
It is also based on things like good judgment, diplomacy,
and trustworthiness.  It is possible for a person to become a
400+ op without knowing everything there is to
know about mIRC.  Goooood thing for some! :)
Becoming a 400+ op
is also based on two kinds of loyalty..  loyalty to the channel
and loyalty to the manager.
.Ops should, however continue to learn.  This is what we
think a 400+ op should know...and then some :) Phew!
 View ban lists | Adduser | Remuser | Autoop on/off | User lists | Suspend | Unsuspend | Access |  Dns | Aliases | Remotes | Timers
.
.
 
 
 
 
.
50's are New Training Channel Operators
75's are New Channel Operators
100's are Channel Operators
400's are Userlist Adminstrators
450's are Trusted Channel Administrators
500's are Channel Managers
.Additional X commands:
 
 
 
 
.
,
.
 
.
 
Addchan | Join  | Part  | Remchan     .
 Clearmode | Modinfo | Access | Match | Rempass | Remuser | Status
Deop | Invite | Op
Ban
.
.
.
 

. 

View Ban list

It is a frequent command that all 400's use to find out who, what, when, and why someone has been banned. Either someone has asked you, or you may think that a previous person is jumping an existing ban and you need to compare the information in the ban list with someone's addy. Well, there are a few ways to check it out. The ban may be in either the channel ban list or the bot ban list.. or both. To check the channels ban list just double click on the channels window. (which I am sure you all know by now) Or you can type this in the channel and you will get all the info on the dummies screen. BTW, anyone even a non op can type this command to the bot.

/msg x ban list #mirc4dummies

-X- *!*AntiScrip@*.greencis.net
-X- SSGT!*AntiScrip@dial13.greencis.net
-X- nbc-nco!*AntiScrip@dial13.greencis.net
-X- GI--JOE!*AntiScrip@dial13.greencis.net
-X- Po_Pimp!*DrBugs@166-167-48.ipt.aol.com
-X- *!~amar79@novix.langara.bc.ca
-X- *!*amar79@novix.langara.bc.ca
-X- *!*~amar79@novix.langara.bc.ca
-X- *!*fuck@*.logos.cy.net
-X- magus69!*magus69@kenn439.3-cities.com
-X- *!*BITEME@*.ihug.co.nz
-X- #mirc4dummies: End of ban list

Or you can use this in your mirc popups/nicknames list ( I have this in my Control section) this one you will need to include the addy, like this  *!*abarron@*.ime.net or *!*@*ime.net and you will get a msg on your dummies window of any bans.  Note: what you type into the search pattern has to be *exactly* how the person was banned or the bot will not see it. If you can't find what your looking for type this in the search pattern *!*@*  and you will get everyone!

.LBanList:/msg X@channels.undernet.org lbanlist # $$?="Search Pattern?"

-X- *** Ban List for channel #mIRC4Dummies ***
-X- #mIRC4Dummies *!*Wolfpoint@208.198.63.104 Level: 499
-X- ADDED BY: momm!~luccetta@167-29-69.ipt.aol.com (Trashed the channel)
-X- SINCE: Tue May 12 01:18:35 1998 UCT
-X- EXP: 3 days, 06:54:01
-X- #mIRC4Dummies *!*stargazer@dialup99.atlantech.net Level: 499
-X- ADDED BY: momm!~luccetta@167-29-69.ipt.aol.com (Trashed the channel)
-X- *** END ***
 


 

 adduser

If you want to add a new nick | addy to the bot, this is called adduser.  Just type this syntax line in the active dummies channel and the bot *should* do as you wish. But remember one can only make adds, removes, modifications etc, on nicks with less of a level than their own. BTW, only an 400+ op in the bots data base can do this.

/msg x adduser #channelname nick | addy level password  (or look at the next line)
/msg x adduser #mirc4dummies girlybear *!*abarron@*.ime.net 500 abcdef

If the user already has an addy in the bots data base but you need to add a new mask (another isp or a numeric addy) and the user is not in the channel but you have the info just type the syntax below so that the bot doesn't recognize the old nick, otherwise you will get this msg from the bot..
.--X- This user is already present in the list.
--X- NICK: aivas^ MATCH: *!*~keward@*.mosquitonet.com ACCESS: 480

/msg x adduser #mirc4dummies aivas^^  *!*~keward@*207.490.282.* 480 abcdef
.


 

remuser

This one is self explanatory... if you want to take someone out of the bot's database just type the syntax below:
But remember to take out *all* the different nicks that are used for one op... :)  BTW, only an 400+ op in the bots data base can do this.
.
/msg x remuser #mirc4dummies aivas^
/msg x remuser #mirc4dummies aivas^^
.

.
 
 

.

 

autoop ON/OFF

The autoop feature is great. When the autoop is ON this will allow all ops  to automatically get op status when entering the channel... however, once an op gets to level 100, the autoop on can be turned OFF, and  they will be able to ask the bot for op status  by typing the syntax below: BTW, only an 400+ op in the bots data base can do this.

/msg x op girlybear   (if your an op on only one channel with X)
/msg x op #mirc4dummies girlybear (if your an op on more then one channel with X)
.

 
.
 
 
 
 

.
suspend/unsuspend .

This suspend/unsuspend command is pretty self explanatory also. It's not one we use much but it is good to know in case you want to stop one from getting op status until you can check with the higher op's or the channel manger on the status. That way you don't have to take the user out and then add them back again. Just type the syntax below: BTW, only an 400+ op in the bots data base can do this.

/msg x modinfo #channelname suspend nick hour level reason
/msg x modinfo #mirc4dummies suspend girlybear 1 500 not following channel rulz
.

 
 
 


 
 

.
DNS
/dns [nick|address]
Resolves an address. If mIRC sees a "." in the name you specify it assumes it's an address and tries to resolve it. Otherwise it assumes it's a nickname and does a /userhost to find the users address and then resolves it.  If you give it an IP address, it looks up the host name.  BTW, anyone even a non op can do this.

You can queue multiple /dns requests, and you can view the current queue by using /dns with no parameters. ie -> /dns nick

Note: This text is only displayed in your own window, it isn't sent to the server so no one else can see it.
 

 

.
.
 
 

.
User List
A user list is maintained by the 400's in the channel. This is used so op's know *who* is who and to keep people from taking over the channel. Then is an op comes in and asks for *op's* their isp address can be checked through their user list. You may use the following in your popups/nicklist folder. Then you may highlight the user when they enter the channel and use this popup to add them in your user list. Give them any level u wish. Then you can refer to your user list by clicking on any of the folders named aliases, popups or remotes then on *user* and you should see anyone that you have added to your user list. This user list is also neat to use with one liner scripts in your remotes. Like for auto opping and maybe sending private MSG's to different level users.  :)  BTW, anyone even a non op can use this.
 
These scripts are examples of two levels matching up with addy's in the user list. The first one will automatically send this welcome msg to anyone who is a 5 in the user list. The second one will automatically notify girlybear of the anyone who is a 7 in the user list.

5:ON JOIN:#:/notice $nick Welcome fellow op to $chan $nick
7:ON JOIN:#:/notice girlybear this person is on your enemy list = watch closely !
.
Users
In the Users section you can specify a list of users and their access levels using this format:
 

Now put your sunglasses on for the user list :))
menu Nicklist {
.ADDUSER/Lvl
..1All:/guser 1 $$1  | /notice $$1 you have been added at lvl 1 (channel regular)
..2chanReg:/guser 2 $$1 | /notice $$1 you have been added at lvl 2 (channel regular)
..3Ferret:/guser 3 $$1 | /notice $$1 you have been added to my userlist @ lvl 3 (ferrets)
..4Friend:/guser 4 $$1 | /notice $$1 you have been added to my userlist @ lvl 4 (friends)
..5OPs:/guser 5 $$1 | /notice $$1 you have been added to my user list @ lvl5 (ops)
..6BestF's:/guser 6 $$1 | /notice $$1 you have been added to my user list @ lvl6 (best friends)
..7Enemies:/guser 7 $$1 | /notice $$1 you have been added to my
{
 
 

.

 
 

.

Access Levels
Access levels are assigned both to a user and to an event and serve to limit a user's access to only certain events.

The default access level is 1 for users that are not listed in the Users list. All users can access level 1 events. The higher a user's access level is, the more events that user can access. You can change the default user level to allow unlisted users to access more commands.
 

 
 
 

.
 


 

.Simple Remotes (good to know but not a must)
The remote allows you to create scripts that react to IRC Server events, such as when a user joins a channel or sends you a message. This tool is the most complex part of mIRC and to use it you must already know how to use IRC Commands, how to create Aliases, and how to use Variables and Identifiers. BTW, anyone even a non op can do this.

The remote consists of three distinct sections:
The Users section
The Variables section
The Scripts section

Since Access Levels play an important part in the way scripts work, you should read about them carefully before proceeding. You should also take a look at remote commands, identifiers, and the internal address list. More info on this can be found by typing /help identifiers in any mirc active window.

Take a look at these and see if u can find all the identifiers and variables

1:ON ctcpreply:PING*:%pt = $ctime - $parm2 | /notice $nick  Auto-Ping-Reply ƒ $+ $nick $+ ƒ Your Ping Reply Is ƒ $+ %pt $+ ƒ Second(s) |  { %ping = $ctime - $parm2 | echo 4 $active $nick $+ 's Ping Reply Is " %ping " Second(s) | unset %ping }
 
5:ON CTCPREPLY:*ping*:%pt = $ctime - $parm2 | /notice $nick **TAG!! YOU'RE IT!** you have a %pt second ping time.**

2:ON TEXT: *ping me*:#mirc4dummies:/inc % nickname1 | /nick  $+ %nickname

1:ON INVITE:#:/ignore -iu120 $nick 3
.

.
 

.

 
 

.
Simple Aliases (good to know but not a must)

mIRC allows you to create aliases and scripts to speed up your IRC session or to perform repetitive functions more easily. To create aliases you must know some IRC commands. BTW, anyone even a non op can do this.

Aliases can be called from the command line, from other aliases, and from popup and remote scripts. An alias cannot call itself recursively mainly because this seems to cause more problems for users than it solves.

If you now type /gb this is the same as typing /join #gb.

/gb /join #girly^

We have now added a parameter string. If we type /j #girly^ this is the same as typing /join #girly^. The $1 refers to the first parameter in the line that you supply.

/j /join $1

If you now type /hi There! Hello the action command will be /me Hello There! The number after $ specifies the number of the parameter in the string that you entered.

/hi /me $2 $1
.

 
 
 
 

.

 
 

.Simple Timers (good to know but not a must)
Here are some simple timers you can view that I use in dummies. They are each numbered on and off, and set to repeat every 600 seconds. Put this in your tools/popups/view/nicknames or make and load it like a mrc. file ok? BTW, anyone even a non op can do this.

Timers can be fun too !! Like I use this one .--> /timer5 0 600 /notice girlybear get your butt of that darn chair and go get your dishes done! | /sound sillybuns.wav | /timer5 off  With this line *only* I can see it ...:)))

menu nicklist {
Timers
.NewbieNoticeOn:/timer1 0 600 /me says 9,1 Newbie Notice 13,1If you have a mIRC question just go ahead and ask...if we aren't too confused...we will be right with you..:)) 7,1 or just relax and learn while you watch ...thanks | /sound sounds\confused.wav
.NewbieNoticeOff:/timer1 off
.ShutRemotesOn:/timer2 0 600 /me says.. 11,1if you are 4,1not 11,1a channel operator.. 13,1please type /remotes off 11,1and or 9,1/timer off ....11,1 your constant running remotes make it very hard for working ops to monitor and help ppl.. thanks so much...:))
.ShutRemotesOff:/timer2 off
.RulzChannelOn:/timer3 0 600 /say 0,12Channel Rulz Are: This is a help channel, and we will teach you anything you want to know in mIRC...and would appreciate it if you experimented with your new knowledge privately for it causes lag and  interferes with op's helping in the channel...13,1thanks for your understanding. | /sound pinggg.wav
.RulzChannelOff:/timer3 off
.RulzpopupOn:/timer4 0 600 /say 7,1 For people who would like to play their newly found colored 11,1popups 7,1please 11,1/join 8,1#popinn ..13,1thanks so much!
.RulzpopupOff:/timer4 off
.QuestOn:/timer4 0 600 /say 15,12 ***Anyone who has a 12,9mIRC15,12 question, please ask ...** Someone here will help *you* asap, so till then just pull up a chair and join in with us!!
.QuestOn:/timer4 off
Best
}

  
 
450's
This adds the channel to x 's database and sets the channel default modes. If you do not use this command after you join x to your channel, they will not rejoin after a restart etc.

Addchan: syntax - /msg x addchan #mirc4dummies

This tells x to join your channel Ha, ha! duh!

Join: syntax - /msg x join #mirc4dummies

This tells x to part your channel (No kidding dick tracy!)
Part: syntax - /msg x part #channel
.
This removes your channel defaults from x's database. Useful when you want to change default modes. This is NOT the same as a purge of your channel. X will not rejoin unless you readdchan after. ok?

Remchan: syntax -/msg x remchan #mirc4dummies 

.

400's
..
This clears all channel modes. Useful when a channel has been locked up. (set +i or +k without your knowledge)

Clearmode: syntax - /msg x clearmode #mirc4dummies

This changes a user's access settings    Variable for Modinfo
The vaiables for modinfo are access, autoop, match and rempass

Modinfo: syntax - /msg x modinfo #mirc4dummies variable user newvalue

.
100's
 
.
This will deop one or more persons in your channel

Deop: syntax - /msg x deop #mirc4dummies nick [nick2] [nick3]

This can only be used when suspending/unsuspending someone lower then your own access level
Duration is s(econds) m(inutes) h(ours) d(ays)
Only suspend up to a max of 336 hours

Suspend: syntax - /msg x suspend #mirc4dummies nick | user@host duration [hour]

Unsuspend: syntax - /msg x unsuspend #mirc4dummies nick

.

75's
.
This bans a person on x's list for a specific number of hours. The maximum is 14 days or 336 hours.   You use the person's nick if they are online. Or specify a user@host if they are not. Level can be from 1 to your access level.

Ban: syntax - /msg x ban #mirc4dummies nick | user@host duration level reason

This bans a whole domain on x's list for a specific number of hours. The maximum is the same.
You don't need the persons nick and they don't have to be online. Level is your level. However! Please don't leave a domain ban on more then a few hours without a 400 or higher approval.

Domain: syntax - /msg x ban #mirc4dummies *!*@.ispname duration level reason

A level 20-74 ban prevents the user from having ops.
A 75+ keeps them from being in the channel at all.

You must at least have the same access level as the level of the ban to remove it.
 

 
 
.
And Then Some
.
Another duty (not necessary but is nice to do) is when a person shows interest in our channel to make note of it and see if that person keeps returning and if that person has asked about what she/he can do to become an op and is serious about becoming an op in Dummies. And if it seems that person is more then willing to work hard, learn from you, then pass that knowledge onto newbies, then please give them the * + *.

From that point on, please take that person under your wing as a responsibility of your status. Teach that person what they need to know to graduate from a + to a 50 op status level. And when you feel that + is ready for a @, please make a recommendation to the Manager.

Now, be careful  not to give this + sign to just anyone who likes to help in the channel, because lots of people love just helping out but do not necessarily want to take op status. This + sign is for people who have full intentions on becoming an *active* op in our channel. This is done by typing the following line in the active Dummies window:

/mode #mirc4dummies  +v nick

or this one to take it away:

/mode #mirc4dummies -v nick

or this one to do more then one at a time:

/mode #mirc4dummies + nick nick2 nick3

You may also put this script in your popups/nicknames list.

menu nicklist {
Voice
.Voice
...+v:/mode # +v $1
..-V:/mode # -v $1
.ADDUSER/Lvl
}
.

 
.
Loyalty To The Channel
.
Loyalty to the Channel: This means that when a *regular visitor* and or *op* (any level) needs help and or need direction (in the basic channel rulz) you are obligated to step in. This is not however required of levels below 400. Mainly because if need be... this 400 or higher can *take* control of the channel without much of a problem, if things get out of hand. Allot more responsibility comes to one who decides to accept that 400 level, because sometimes you may have to make an unpopular decision and not everyone will agree with your call. But *know this* if you are recommenced by an existing 499 to be raised to a 400 and accepted by *you* and then by he Manager, it will be pretty certain you can be relied upon to make those unpopular decisions when needed and then backed by your fellow op's and Manager. And there is NO shame for someone to not want to or refuse the 400 level. Not everyone wants nor is cut out for that type of status.
 .
 
.
This is what happens when pinnochio tells girly a lie !!
Don't let it happen to you... !!!
:)))
 
 
 
.
Loyalty To The Manager
...-
Loyalty to the Manger: This means that not only do you have to be supportive to the newop's and to the regular op's in dummies but also to the Manager. The Manager will expect total honesty and respect and your important input in regards to the well being of the channel. The Manger does not expect you to *tell* on others, but does rely on your good judgment on what is best for the channel. And gossip is not one of them...lol.  A good manager will take into consideration the *input* given .. and of course can't take into consideration any *not given*. If the Manager is able to rely on their 400's and higher for input on the status of the channel when the Manger is absent, then the best interests of the channel will not be in jeopardy.
.
.
 
500's (Manager)
A Manager's job is to be for sure one of the hardest jobs on the nets today. (especially in a busy help channel) She/he tries to make sure that the channel is running *in order* , the newbies are getting the help they need and that the channel operators are getting along. A truly hard job for one person. Now the rulz are different in each and every channel and channels like  #mirc4dummies does NOT have any stead fast CHARTER, so it can be hectic sometimes keeping the *peace* between channel operators. Each channel operator is unique in her/his own way. Each have their own views as to how a channel should be run. That is why for the most part, #mirc4dummies is run by a majority rule.  And a manager can't take into consideration someone's *opinion* if it is not given. Yes?
 

Following are some MORE syntax's for you to read... now you don't have to learn them.. unless you plan on being your own manager.. but you just might find them interesting enough. :)
 
 

This changes special X modes for the channel

SET MODES: syntax - /msg X set #mirc4dummies

NOTE: the variables AlwaysOp, UserFlags, MassDeopPro, NickFloodPro, URL and Description can be changed by someone with 450+ access on your channel.

Variables for SET

MassDeopPro: The maximum number of deops X will allow in a 15 second period. Any user exceeding this will be DeOped and Suspended. (If on the userlist)

NickFloodPro: The maximum number of nick changes that can be done in the channel in a 15 second period. Any user exceeding this number will be kicked from the channel and suspended. (If on the userlist) Note: The noclones patch makes this variable obsolete, since it will not allow rapid nick changes.

FloodNick changes: The maximum number of KICKS, TOPIC CHANGES and such that can be sent to the channel in a 15 second period. Any user exceeding this limit will be kicked and suspended. (If in the userlist) Note: This does NOT work against normal channel dialogue, since X is +d (deaf) to all channel text.

UserFlags: Set's default user settings that will be given to a new user on the channel. Default value is 0.

0 = Autoop OFF for new users
1 = Autoop ON for new users
 
NoOp: In this mode x will deop EVERYONE. Making her the only op in the channel. However, users may still access commands through X.

AlwaysOp: This variable insures that X will always have ops. She will op themselves if it is not given to her.

OpOnly: Make op the only chanop command available though X. Also, you can ONLY op yourself. Note: This does NOT prevent someone with ops in the channel from exercising op commands themselves.

StrictOp: In this mode only people on the userlist may have ops. If they are on the list, they must send their password before they are allowed to ops.

Lang: Changes default language for the channel.

                en (english)
                hl (dutch)
                fr (french)
                ge (deutsch)

Description: Sets the default channel topic. This does NOT affect the actual channel topic. The topic can be seen only in the chaninfo, or on the webpage.

URL: Sets the default channel URL. This can be seen from the chaninfo, or the webpage.

AutoTopic: This flag makes X reset the topic to the channel URL and Description every 30 minutes. Note that is if the channel is idle, the topic will not be reset during that time.
 

 
 
 
 
This page last updated on 5.30.98.
.
-
return to MAIN page
    go to the newops page