# Scripting in CoffeeMud 5.9
Introduction Script Structure Scripting Events all_greet_prog act_prog arrive_prog mask_prog bribe_prog buy_prog channel_prog cast_prog casting_prog close_prog cnclmsg_prog consume_prog damage_prog day_prog death_prog delay_prog drop_prog entry_prog execmsg_prog exit_prog fight_prog function_prog get_prog give_prog giving_prog greet_prog hitprcnt_prog imask_prog kill_prog level_prog lock_prog login_prog logoff_prog llook_prog look_prog once_prog open_prog quest_time_prog put_prog putting_prog rand_prog regmask_prog remove_prog social_prog sell_prog speak_prog speech_prog time_prog unlock_prog wear_prog Scripting Codes $ codes % codes Scripting Commands if, else, endif switch, case for, next <SCRIPT> mpacctattoo mpaffect mpalarm mpargset mpasound mpat mpbeacon mpbehave mpcallfunc mpcast mpcastext mpchannel mpchoose mpclose mpconfirm mpdamage mpdisable mpecho mpechoaround mpechoat mpenable mpendquest mpexp mpfaction mpforce mpplayerclass mpgoto mpgset mpheal mphide mpjunk mpkill mplink mploadquestobj mploadvar mplock mplog mpm2i2m mpmload mpmloadshop mpmoney mpnotrigger mpoload mpoloadroom mpoloadshop mpopen mppossess mppracs mpprompt mppurge mpput mpquestpoints mpquestwin mpqset mprejuv mpreset mpsavevar mpscript mpset mpsetclan mpsetclandata mpsetinternal mpsetvar mpslay mpspeak mpstartquest mpstop mptattoo mptitle mptrackto mptrains mptransfer mpunaffect mpunbehave mpunhide mpunloadscript mpunlock mpwhile mpwalkto mpunlink return Scripting Functions Logical Operators affected baseclass cansee canhear callfunc clan clandata clanrank clanqualifies class currency datetime deity eval exp expertise explored faction goldamt gstat has hasacctattoo hasnum hastattoo hastattootime hitprcnt inarea incontainer inlocale inroom ipaddress isable isalive isbehave isbirthday ischarmed iscontent isday isevil isfight isfollow isgood ishere ishour isimmort islike islocked ismonth ismoon isname isnpc isodd isopen ispc ispkill isquestmobalive isrecall isrlhour isrlday isrlmonth isrlyear isseason isservant isspeaking istime isweather isyear itemcount level math mobitem mood number numitemsmob numitemsroom numitemsshop nummobs nummobsinarea nummobsroom numpcsarea numpcsroom numraces numracesinarea position pracs questarea questobj questmob questpoints questroom questscripted questwinner qvar race racecat rand rand0num randnum roomitem roommob sex shophas shopitem stat strcontains strin trains value var worn wornon | ## Introduction to Scripting Scripting is the ability to makes something behave proactively, or respond to game stimuli, in a way specified by the game builders. A Script is the set of commands written by the builders to perform this function. In CoffeeMud, any object may be scripted. This means that rooms, areas, items, and especially MOBs can be scripted. Scripting is accomplished through the Scriptable Behavior. Giving an object this behavior makes it capable of running scripts on its behalf. The parameters of the Scriptable behavior define the source of the script itself. The most common parameter for the Scriptable behavior is the LOAD command, which specifies a text file containing the script. The syntax for this is as follows:
    load=path/file name
The starting path for the Scriptable behavior is the /resources/ directory in your CoffeeMud package. Any further paths will branch from that directory. The file specified is a text file containing the script. You can also specify more than one script in the Scriptable parameters by separating LOAD= commands with the ~ character like so:
    load=progs/mrinfo.script~load=progs/strangetrader.script~
A less common way to specify a script for the Scriptable behavior is to enter the script itself into the parameter. Scripts entered in this way differ from scripts entered into text files for the LOAD parameter in one significant sense: Every line of a script entered in this way must be terminated by a semicolon. Here is an example.
    RAND_PROG 50;bounce;say "hi!";~;
Scripts which are entered into text files for the LOAD parameter have their lines terminated by carriage returns (ENTER) instead of semicolons. The script syntax is, in all other ways, identical. If you need to put special characters (like ; ~ or LOAD=) into particular commands, you may need to escape those characters by putting a \ character before them, to tell the Scriptable behavior not to consider them line or script delimiters. When the Scriptable behavior loads a file using the LOAD= syntax, it automatically keeps a copy of it in memory for future use. This memory cache is called the CoffeeMud Resources. If you have a Scriptable prog you have entered using the LOAD= syntax, you can see its entry in the cache by using your Archon character to enter LIST RESOURCES from the CoffeeMud command line. Because the script files from disk are kept in memory for quick access, any changes or additions to your script on disk will not be immediately noticed by the CoffeeMud engine. To force the engine to notice your changes, you must first UNLOAD your script file from the Resources cache. This is done by using the Archon command UNLOAD. Check the ahelp entry for that command for more information on how to use it when developing Scriptable behavior files on disk. Those who are familiar with the mobprog scripting language in other mud codebases will have no trouble picking up on the CoffeeMud scripting language. In fact, most of your existing scripts will probably work without changes. ## Script Structure The CoffeeMud scripting language is an "event-based" language. Each script may contain one or more event "triggers". Each trigger defines the conditions of its occurrence on a single line. This line is followed by commands underneath it which are executed only when the trigger event occurs. Each event trigger/command grouping is terminated by a ~ character, which should appear on a line by itself. Putting this together, we have a high level syntax that looks like this:
    EVENT_TRIGGER parameter1 parameter2 ...
    command1
    command2
    ...
    commandN
    ~

    ANOTHER_EVENT_TRIGGER parameter1 parameter2 ...
    command1
    command2
    ...
    commandN
    ~
    etc.
## Scripting Events Below are a list of the valid event triggers, along with their parameters, and a description of the events or circumstances under which the events occur. * Note: Most triggers fire after a short delay, and only when the scripted mob is healthy and non-follower. See the MPSETINTERNAL command to change default global triggering behavior. These docs borrow heavily from the nicely written MOBPROG Tutorial at: http://www.pandapub.com/tutorial/MobprogTutorial.htm. ### all_greet_prog Usage:
    all_greet_prog [integer percentage]
This type of mobprog checks a percentage chance every time someone enters the room that the script mob, item, exit, or room is currently in. If the random number generated between 1 and 100 is equal to or below the percentage of the all_greet_prog, the prog is triggered. Note that all_greet_progs are triggered by both players and mobs, even sneaking ones, and a mob in a maze can actually sometimes end up triggering itself! This type of mobprog has all sorts of uses, ranging from giving in-zone quest information to people entering the room, creating aggressive progs, etc. EXAMPLES:
    all_greet_prog 25
This prog will be triggered 25% of the time when someone enters the room where the mob currently is.
    all_greet_prog 100
This prog will be triggered 100% of the time when someone enters the room where the mob currently is. This means every time. SPECIAL NOTES: You'll probably want to do a large number of if checks in all_greet_progs, specifically in the difference between mobs and player characters. Note that all_greet_progs will trigger even if a person is sneaking, though the mob must have detect invisibility to see invisible people, infravision to see people in the dark, sense sneaking to see sneakers, and will not see people if blinded. Also, be sure to check out arrive_prog, which is a nice counterpart to greet_prog. ### act_prog ### mask_prog Usage:
    act_prog [trigger message]
    act_prog p [trigger message]
This type of mobprog will trigger when the mob sees a certain string of text. When the 'p' is inserted into the trigger line, the string of text must be precise, while if it is not, any of the words in the list can trigger the mobprog. This type of mobprog has many uses, one of which is communication between mobs. There are a few socials which create a message only to the person performing them and to the one receiving them. You can use these and act_progs to safely have mobs trigger each other, without people seeing what is going on. Other uses include triggering off of people fleeing, moving out of the room, etc. The possibilities are endless. The act_prog will attempt to trigger off of the string exactly as third-partys see things, if possible. If third partys see nothing, the target view will be chosen. If only the source sees the event message, that will be chosen. Variables may not be used in trigger messages, so you will need to be ambiguous to get matches. For instance, if Bob hits Larry, the message that act_prog will see would be something like "Bob hits Larry hard!". To capture this for all possible sources and targets, your best hit then is to match on the word "hits" and then check $n and $t for the appropriate values. EXAMPLES:
    act_prog wolf dog coyote
This will trigger whenever the mob sees a segment of text containing any of the words wolf, dog, or coyote. If the string contains more than one of these, the prog will be triggered multiple times.
    act_prog p A wolf howls at the moon.
This will trigger the prog when it sees this precise message. Note that punctuation is stripped from both your message and the message matched against. MULTIPLE PROGS: You can have more than one act_prog on a mob, but you shouldn't have multiple act_progs that trigger off of the same message. SPECIAL NOTES: ANSI colors on objects don't seem to work well with act_progs, so avoid using ANSI colors in anything that may be part of your act_prog trigger. Variables and Codes are not used in act_progs, so do not try to use them; it won't work. ### arrive_prog Usage:
    arrive_prog [integer percentage]
This type of mobprog checks a percentage chance every time the scripted mob or item owner enters a new room, or when they enter the game. If the random number generated between 1 and 100 is equal to or below the percentage of the arrive_prog, the prog is triggered. This type of mobprog has all sorts of uses, ranging from giving in-zone quest information to people the mob stumbles upon, creating aggressive progs, etc. EXAMPLES:
    arrive_prog 25
This prog will be triggered 25% of the time when the mob enters a room.
    arrive_prog 100
This prog will be triggered 100% of the time when the mob enters a room. This means every time. SPECIAL NOTES: You'll probably want to make sure you understand the difference between the arrive_prog and greet_prog/all_greet_prog. Scripted Exits and Rooms will never trigger this event. ### bribe_prog Usage:
    bribe_prog [money value]
This type of mobprog is triggered when a value of money is given to the mob. If the amount of money is equal to or more than the money value of the bribe_prog, the prog will go off. If it is less than the value of the bribe_prog, or the money is not in the local currency, it will not go off. This type of prog is normally used for in-zone quests, perhaps bribing guards to let a prisoner free or bribing a bartender to give you some information. It can also be used for larger, special mob behavior, such as a ferryman who will move a player to another spot in the world for a fee. The money value is always expressed in absolute gold value of the default currency. See the Archon's Guide under currency if you don't know what that means. EXAMPLES:
    bribe_prog 1
This bribe_prog will trigger whenever the mob is given an amount of gold equal to or greater than 1 coin. Of course, this means that the prog will be triggered if any amount of money is given to the mob at all.
    bribe_prog 500
This bribe_prog will trigger if someone gives the mob an amount of money equal to or greater than 500 coins.) MULTIPLE PROGS: You can have multiple bribe_progs on the same mob. However, these must be listed in order from largest gold amount to smallest gold amount. So if you have a bribe_prog 250 and a bribe_prog 100, the 250 must be listed first, and then the 100. If you don't do this your larger sum bribe_progs will never be triggered. ### buy_prog Usage:
    buy_prog [keyword list]
    buy_prog p [keyword phrase]
    buy_prog all
This type of mobprog is triggered by buying an item from a shopkeeper. If the item being bought has any of the keywords of the buy_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the item must exactly match that of the buy_prog. If there is not, then any item with any of the keywords in the list in it will trigger it. If a buy_prog all is used, then the buy_prog will trigger for any item at all being bought. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    buy_prog orange apple banana
This will trigger if the item being bought has any of the keywords orange, apple, or banana. This means that it would be triggered by buying a banana, an apple pie, or even an orange shield.
    buy_prog p apple pie delicious
This will trigger if the item being bought has the exact keywords apple pie delicious. The prog would not be triggered by buying anything with keywords red apple or blackberry pie or anything except the exact order and wording of the keyword list.
    buy_prog all
This will trigger if any sort of item is bought. MULTIPLE PROGS: You can have more than one buy_prog on a mob. Generally it is best not to have buy_progs with the same keywords in them, unless they are a buy_prog p with different keyword lists but some of the same keywords – for example a buy_prog p apple red juicy and a buy_prog p apple red poisoned. ### cast_prog Usage:
    cast_prog [ability id list]
    cast_prog p [keyword list]
    cast_prog all
This type of mobprog is triggered by the mob having a spell or skill used on them by someone else. If the spell or skill matches the keywords of the give_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the name or id of the spell must exactly match that of the cast_prog. If a cast_prog all is used, then the cast_prog will trigger from any spell/skill at all being used on the mob. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    cast_prog fire ice
This will trigger if the fireball spell or any spell with fire or ice in its name is cast at the mob.
    cast_prog p Spell_Fireball
This will trigger only if the Fireball spell is cast at the mob.
    cast_prog all
This will trigger if any spell or skill is used on the mob. MULTIPLE PROGS: You can have more than one cast_prog on a mob. Generally it is best not to have cast_progs with the same keywords in them, unless they are a cast_prog p with different keyword lists but some of the same keywords – for example a cast_prog p Spell_Fireball and a cast_prog p Spell_FlamingHands ### casting_prog Usage:
    cast_prog [keyword list]
    cast_prog p [keyword list]
    cast_prog all
This type of mobprog is triggered by the mob casting a spell or skill on someone. If the spell cast on the mob matches the keywords of the cast_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the name or id of the spell must exactly match that of the cast_prog. If there is not, then any spell with any of the keywords in the list in it will trigger it. If a casting_prog all is used, then the casting_prog will trigger from any spell at all being cast on anyone by the mob. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    casting_prog fire ice
This will trigger if the mob casts an spell that has any of the keywords fire or ice. This means that it would be triggered by casting a Fireball spell or Ice Lance spell.
    casting_prog p Spell_Fireball
This will trigger if the mob casts the spell that has the exact ID of Spell_Fireball.
    cast_prog all
This will trigger if any spell or skill is cast by the mob MULTIPLE PROGS: You can have more than one casting_prog on a mob. Generally it is best not to have casting_progs with the same keywords in them, unless they are a casting_prog p with different keyword lists but some of the same keywords – for example a casting_prog p Spell_Fireball and a cast_prog p Spell_IceLance ### channel_prog Usage:
    channel_prog [channel name] [trigger words]
    channel_prog [channel name] p [trigger message]
This type of mobprog will trigger when the mob sees a certain string of text over the specified channel. When the 'p' is inserted into the trigger line, the string of text must be precise, while if it is not, any of the words in the list can trigger the mobprog. This type of mobprog has many uses, one of which is communication between mobs. The possibilities are endlessly finite. EXAMPLES:
    channel_prog help me
This will trigger whenever the mob sees a segment of text containing any of the words help or me. If the string contains more than one of these, the prog will be triggered multiple times.
    channel_prog p GOSSIP hello.
This will trigger the prog when it sees this message channeled. Note that punctuation is important here as well. MULTIPLE PROGS: You can have more than one channel_prog on a mob, but you shouldn't have multiple channel_progs that trigger off of the same message. SPECIAL NOTES: ANSI colors on objects don't seem to work well with channel_progs, so avoid using ANSI colors in anything that may be part of your channel_prog trigger. Variables and Codes are not used in channel_progs, so do not try to use them; it won't work. ### close_prog Usage:
    close_prog [keyword list]
    close_prog p [keyword list]
    close_prog all
This type of mobprog is triggered by closing a container or door. If the script is on a container-type object, such as a door or container item, it will trigger only if the object being closed is the scripted one. Otherwise, if the target matches the keywords of the close_prog, the prog is triggered. If there is a 'p' placed before the keyword list, the keywords of the object must exactly match that of the close_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If the scripted item is not a container or door, and a "close_prog all" is used, then the close_prog will trigger from any object at all being opened. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. As is normal, if the scripted object is a mob, this event will not trigger if the scripted mob is the originator of the activity. EXAMPLES:
    close_prog door gate
This will trigger if the object closed has any of the keywords door gate. This means that it would be triggered by closing a door or gate.
    close_prog p a large chest
This will trigger if the object closed has the exact keywords a large chest.. The prog would not be triggered by closing an object with keywords large or chest or anything except the exact order and wording of the keyword list.
    close_prog all
This will trigger if any object is closed. MULTIPLE PROGS: You can have more than one close_prog on an item, mob, or room. Generally it is best not to have close_progs with the same keywords in them, unless they are a close_progs p with different keyword lists but some of the same keywords - for example a close_progs p door gate and a close_prog p door to the gate. ### cnclmsg_prog Usage:
    cnclmsg_prog [message code] [commands/keyword list]
    cnclmsg_prog [message code] p [commands/keyword list]
    cnclmsg_prog [message code] all
This type of mobprog is definitely for those very familiar with CoffeeMud. In fact, I'd recommend at least a cursory knowledge of the Programmer's Guide to consider using it. The purpose of this trigger is that it executes before a particular event or "message" occurs in the mud. The kind of event is called the "message code". The trigger also requires either the word "all" to always execute before the desired message does, or a list of player command line words matches those typed by the player most recently to the arrival of this message. Since mobs, unlike players, do not enter commands on a command line, you should use the ALL form liberally. The body of the trigger executes before the given message occurs, and the fact that the trigger executes is no guarantee that the event will end up occuring at all. For instance, this trigger may execute when a player tries to leave the room while under the effects of the "Hold" spell, meaning the player will not actually be allowed to leave regardless of what is done in your trigger. However, this type of trigger is most useful as a means of testing and cancelling certain types of event messages; thus the name. To cause the triggered event to be cancelled, you need only add a RETURN CANCEL command to the body of this script. See also execmsg_prog. Valid message codes include the following: AREAAFFECT, PUSH, PULL, RECALL, OPEN, CLOSE, PUT, GET, UNLOCK, LOCK, WIELD, GIVE, BUY, SELL, DROP, WEAR, FILL, DELICATE_HANDS_ACT, VALUE, HOLD, NOISYMOVEMENT, QUIETMOVEMENT, WEAPONATTACK, LOOK, READ, NOISE, SPEAK, CAST_SPELL, LIST, EAT, ENTER, FOLLOW, LEAVE, SLEEP, SIT, STAND, FLEE, NOFOLLOW, WRITE, FIRE, COLD, WATER, GAS, MIND, GENERAL, JUSTICE, ACID, ELECTRIC, POISON, UNDEAD, MOUNT, DISMOUNT, OK_ACTION, OK_VISUAL, DRINK, HANDS, PARALYZE, WAND_USE, SERVE, REBUKE, ADVANCE, DISEASE, DEATH, DEPOSIT, WITHDRAW, EMOTE, QUIT, SHUTDOWN, VIEW, RETIRE, RETREAT,PANIC, THROW, EXTINGUISH, TELL, SITMOVE, KNOCK, PRACTICE, TEACH, REMOVE, EXPCHANGE, DAMAGE, HEALING, ROOMRESET, RELOAD, SNIFF, ACTIVATE, DEACTIVATE, FACTIONCHANGE, LOGIN, LEVEL, EXAMINE, ORDER, EXPIRE, BORROW, HUH, LIFE, BID, CLANEVENT, UNLOAD, DUELCHALLENGE, LEGALWARRANT, DIG, PREINVOKE, POSSESS, DISPOSSESS, POWERCURRENT, CONTEMPLATE, POUR, LOOKEXITS, LASER, SONIC, REPAIR, ENHANCE, INSTALL, COLLISION, AROMA, DUELLOSS, COMMANDFAIL , METACOMMAND And here are some general message code types that may also be used: TOUCH, MOVE, EYES, MOUTH, SOUND, GENERAL, MAGIC, DELICATE, MALICIOUS, CHANNEL, OPTIMIZE, CNTRLMSG, INTERMSG, UNINTENTIONAL For truly advanced users, you can also prefix a message code with some combination of the letters S, O, and T followed by an equal (=) sign to narrow matches to only those messages where your given code appears as the Source, Others, and Target codes respectively. For example, use a message code of ST=DEATH to match cases where the Source and Target message codes are DEATH and the Others code is ignored. You can also put the character < or > before the S, O, or Ts in order to narrowly check against the Major masks or the Minor type codes respectively. See the Programmer's Guide if you don't know what that stuff means. EXAMPLES:
    cnclmsg_prog hands p smile
     mpechoat $n No smiling is allowed here!
     return cancel
    ~
This will trigger if a player (not a mob) around the scripted object attempts to smile.
    cnclmsg_prog GET p get rock
     mpechoat $n You may not get the rock.
     return cancel
    ~
This will trigger if a player (not a mob) enters the command "get rock" at the command line, this will trigger and cancel he attempt..
    cnclmsg_prog >S=MAGIC ALL
     mpechoat $n You may not do your magic.
     return cancel
    ~
This will trigger if a player (not a mob) tries to use any spell. The CNCLMSG_PROG is especially useful for creating new command that only apply in particular rooms or with respect to particular mobs. This is because entering an incorrect command, which normally generates a "Huh?" message, can also be canceled and re-applied. For instance, suppose you wanted users to be able to enter "plastify sword" at some part in your quest and have it do something. In this case, you'd need to capture the HUH message as so:
    cnclmsg_prog HUH p plastify sword
     mpechoat $n The sword has been plastified! Thank you!
     return cancel
    ~
MULTIPLE PROGS: You can have more than one cnclmsg_prog, not only in the same script, but regarding the very same message codes if you like. ### consume_prog Usage:
    consume_prog [keyword list]
    consume_prog p [keyword list]
    consume_prog all
This type of mobprog is triggered eating or drinking from an object. If the object used matches the keywords of the consume_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the object must exactly match that of the consume_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If a consume_prog all is used, then the consume_prog will trigger from any object at all. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    consume_prog orange apple banana
This will trigger if the object eaten has any of the keywords orange, apple, or banana. This means that it would be triggered by eating a banana, an apple pie, or even an orange shield.
    consume_prog p apple pie delicious
This will trigger if the object eaten has the exact keywords apple pie delicious. The prog would not be triggered by eating an object with keywords red apple or blackberry pie or anything except the exact order and wording of the keyword list.
    consume_prog all
This will trigger if any object is ate or drank. MULTIPLE PROGS: You can have more than one consume_prog on a mob. Generally it is best not to have consume_progs with the same keywords in them, unless they are a consume_prog p with different keyword lists but some of the same keywords – for example a consume_prog p apple red juicy and a consume_prog p apple red poisoned. ### damage_prog Usage:
    damage_prog
This type of mobprog is triggered whenever the scripted mob is damaged, or the scripted item is used to deliver damage. The source and target mobs will be as you expect. The secondary item will be the weapon used to deliver the damage, if it was a physical item (spells are not items). The string returned in $g will be the amount of damage taken. EXAMPLES:
    damage_prog
This program will trigger when damage is taken by a mob, or given by the scripted item. ### day_prog Usage:
    day_prog [list of integer day of the month]
This type of mobprog triggers once per mud day, on the days of the month listed. This allows you to have a script which triggers very infrequently indeed. There are 30 days per month in CoffeeMud. EXAMPLES:
    day_prog 20 21 22
This will trigger if day of the month is 20, 21, or 22.
    day_prog 10
This will trigger on the 10th day of every month. ### death_prog Usage:
    death_prog
This mobprog type triggers on the mob's death. The death_prog has a wide range of uses. The death_prog is queued just before the mob dies, so it is considered to be the mob's last gasp. At the end of the death-prog, however, the mob dies. Even if the mob sets its hit points to full, it will die. Other than that, the mob can mpjunk equipment it has, mpgoto a new room to die, unlock a door, load an object of some kind, etc. MULTIPLE PROGS: You can have multiple death_progs on the same mob. ### delay_prog Usage:
    delay_prog [integer, minimum number of ticks] [integer, maximum number of ticks]
This kind of mobprog triggers after a random number of ticks have elapsed. The number of random ticks is between the two integers provided. This trigger is used to take some of the load off of rand_prog type programs. EXAMPLES:
    delay_prog 10 20
This delay_prog will be triggered after 10-20 ticks have elapsed.
    delay_prog 1 11
This delay_prog will be triggered after 1-11 ticks have elapsed. ### drop_prog Usage:
    drop_prog [keyword list]
    drop_prog p [keyword list]
    drop_prog all
This type of mobprog is triggered by dropping an object. If the object dropped matches the keywords of the drop_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the object must exactly match that of the drop_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If a drop_prog all is used, then the drop_prog will trigger from any object at all being dropped. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    drop_prog orange apple banana
This will trigger if the object dropped has any of the keywords orange, apple, or banana. This means that it would be triggered by dropping a banana, an apple pie, or even an orange shield.
    drop_prog p apple pie delicious
This will trigger if the object dropped has the exact keywords apple pie delicious. The prog would not be triggered by dropping an object with keywords red apple or blackberry pie or anything except the exact order and wording of the keyword list.
    drop_prog all
This will trigger if any object is dropped. MULTIPLE PROGS: You can have more than one drop_prog on a mob. Generally it is best not to have drop_progs with the same keywords in them, unless they are a drop_prog p with different keyword lists but some of the same keywords – for example a drop_prog p apple red juicy and a drop_prog p apple red poisoned. ### entry_prog Usage:
    entry_prog [integer percentage]
This type of prog checks a percentage chance every time the scripted mob moves into a new room, or if a scripted item owner mob enters a new room, or a scripted room or exit is entered . If the random number generated is equal to or below the percentage of the entry_prog when a mob steps into a new room, then the prog is triggered. This prog has a variety of uses, for instance, you can use it in conjunction with the inroom function to make sure a mob stays in the same room or never oversteps a boundary, or to have the mob attack players as it enters the room. There are many possibilities. EXAMPLES:
    entry_prog 25
This will trigger 25% of the time when the mob enters a room.
    entry_prog 100
This will trigger 100%, or every time, the mob enters a room. SPECIAL NOTES: This program is triggered on a normal delay unless it is multiply triggered, in which case it will occur once, but immediately. ### execmsg_prog Usage:
    execmsg_prog [message code] [commands/keyword list]
    execmsg_prog [message code] p [commands/keyword list]
    execmsg_prog [message code] all
This type of mobprog is definitely for those very familiar with CoffeeMud. In fact, I'd recommend at least a cursory knowledge of the Programmer's Guide to consider using it. The purpose of this trigger is that it executes while a particular and valid event or "message" occurs in the mud. The kind of event is called the "message code". The trigger also requires either the word "all" to always execute whenever the desired message does, or a list of player command line words matching those typed by the player most recently to the arrival of this message. Since mobs, unlike players, do not enter commands on a command line, you should use the ALL form liberally. See also cnclmsg_prog. Valid message codes include the following: AREAAFFECT, PUSH, PULL, RECALL, OPEN, CLOSE, PUT, GET, UNLOCK, LOCK, WIELD, GIVE, BUY, SELL, DROP, WEAR, FILL, DELICATE_HANDS_ACT, VALUE, HOLD, NOISYMOVEMENT, QUIETMOVEMENT, WEAPONATTACK, LOOK, READ, NOISE, SPEAK, CAST_SPELL, LIST, EAT, ENTER, FOLLOW, LEAVE, SLEEP, SIT, STAND, FLEE, NOFOLLOW, WRITE, FIRE, COLD, WATER, GAS, MIND, GENERAL, JUSTICE, ACID, ELECTRIC, POISON, UNDEAD, MOUNT, DISMOUNT, OK_ACTION, OK_VISUAL, DRINK, HANDS, PARALYZE, WAND_USE, SERVE, REBUKE, ADVANCE, DISEASE, DEATH, DEPOSIT, WITHDRAW, EMOTE, QUIT, SHUTDOWN, VIEW, RETIRE, RETREAT,PANIC, THROW, EXTINGUISH, TELL, SITMOVE, KNOCK, PRACTICE, TEACH, REMOVE, EXPCHANGE, DAMAGE, HEALING, ROOMRESET, RELOAD, SNIFF, ACTIVATE, DEACTIVATE, FACTIONCHANGE, LOGIN, LEVEL, EXAMINE, BORROW, HUH, LIFE, BID, CLANEVENT, UNLOAD, DUELCHALLENGE, LEGALWARRANT, DIG, PREINVOKE, POSSESS, DISPOSSESS, POWERCURRENT, CONTEMPLATE, POUR, LOOKEXITS, LASER, SONIC, REPAIR, ENHANCE, INSTALL, COLLISION, AROMA, DUELLOSS, COMMANDFAIL, METACOMMAND And here are some general message code types that may also be used: TOUCH, MOVE, EYES, MOUTH, SOUND, GENERAL, MAGIC, DELICATE, MALICIOUS, CHANNEL, OPTIMIZE, CNTRLMSG, INTERMSG, UNINTENTIONAL For truly advanced users, you can also prefix a message code with some combination of the letters S, O, and T followed by an equal (=) sign to narrow matches to only those messages where your given code appears as the Source, Others, and Target codes respectively. For example, use a message code of ST=DEATH to match cases where the Source and Target message codes are DEATH and the Others code is ignored. You can also put the character < or > before the S, O, or Ts in order to narrowly check against the Major masks or the Minor type codes respectively. See the Programmer's Guide if you don't know what that stuff means. EXAMPLES:
    execmsg_prog get all
     mpecho $n likes $p.
    ~
This will trigger if a player or a mob attempts to get something.
    execmsg_prog GET p get rock
     mpecho $n has gotten a rock!
    ~
This will trigger if a player (not a mob) enters the command "get rock" at the command line, this will trigger.
    execmsg_prog >S=MAGIC ALL
     mpechoat $n has done the magic.
    ~
This will trigger if a player (not a mob) tries to use any spell. MULTIPLE PROGS: You can have more than one execmsg_prog, not only in the same script, but regarding the very same message codes if you like. However, only the first one that triggers will count. ### exit_prog Usage:
    exit_prog [integer percentage]
This type of prog checks a percentage chance every time a mob moves out of a the room the scripted mob is in. If the random number generated is equal to or below the percentage of the exit_prog when the mob steps out of the room, then the prog is triggered. This prog has a variety of uses, for instance, you can use it in conjunction with the inroom function to make sure other mobs stay in the same room or never oversteps a boundary, or to have the mob attack remaining players when one leaves. There are many possibilities. EXAMPLES:
    exit_prog 25
This will trigger 25% of the time when a mob leaves the room.
    exit_prog 100
This will trigger 100%, or every time, a mob leaves the room. ### fight_prog Usage:
    fight_prog [integer percentage]
This type of mobprog checks a percentage chance every round of combat that the mob is in. If the random number generated between 1 and 100 is equal to or less than the percentage of the fight_prog, then it will be triggered. This type of mobprog is generally used to have the mob do certain things in combat, for instance, cast spells or use skills. Sometimes it is used to ensure a mob doesn't fight at all, or to perform special, more complicated actions in combat. EXAMPLES:
    fight_prog 10
This will trigger 10% of the time each round of combat the mob is in. That means that it is probable that this mobprog will go off every 10 rounds or so, although it is not guaranteed to do so.
    fight_prog 75
This will trigger 75% of the time each combat round. That means it's a safe bet that the trigger will go off 3 out of every 4 rounds. ### function_prog Usage:
    function_prog [string name of the function]
This type of prog provides a named placeholder for the series of commands that follows. This type of mobprog is never independently triggered, but instead relys on one of the commands, MPCALLFUNC, to trigger it manually. The usefulness of doing this will become apparent in the discussion of MPCALLFUNC. EXAMPLES:
    function_prog Destroy Everyone
This will trigger only when called by MPCALLFUNC. ### get_prog Usage:
    get_prog [keyword list]
    get_prog p [keyword list]
    get_prog all
This type of mobprog is triggered by getting an object. If the object picked up matches the keywords of the get_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the object must exactly match that of the get_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If a get_prog all is used, then the get_prog will trigger from any object at all being picked up. When running on a container item, the get_prog matches the item being retrieved from the container, not the container itself. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    get_prog orange apple banana
This will trigger if the object picked up has any of the keywords orange, apple, or banana. This means that it would be triggered by getting a banana, an apple pie, or even an orange shield.
     get_prog p apple pie delicious
This will trigger if the object picked up has the exact keywords apple pie delicious. The prog would not be triggered by getting an object with keywords red apple or blackberry pie or anything except the exact order and wording of the keyword list.
    get_prog all
This will trigger if any object is picked up. MULTIPLE PROGS: You can have more than one get_prog on a mob. Generally it is best not to have get_progs with the same keywords in them, unless they are a get_prog p with different keyword lists but some of the same keywords – for example a get_prog p apple red juicy and a get_prog p apple red poisoned. ### give_prog Usage:
    give_prog [keyword list]
    give_prog p [keyword list]
    give_prog all
This type of mobprog is triggered by the mob being given an object. If the object given to the mob matches the keywords of the give_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the object must exactly match that of the give_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If a give_prog all is used, then the give_prog will trigger from any object at all being given to the mob. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    give_prog orange apple banana
This will trigger if the object given to the mob has any of the keywords orange, apple, or banana. This means that it would be triggered by being given a banana, an apple pie, or even an orange shield.)
    give_prog p apple pie delicious
This will trigger if the object given to the mob has the exact keywords apple pie delicious. The prog would not be triggered by being given an object with keywords red apple or blackberry pie or anything except the exact order and wording of the keyword list.
    give_prog all
This will trigger if any object is given to the mob. MULTIPLE PROGS: You can have more than one give_prog on a mob. Generally it is best not to have give_progs with the same keywords in them, unless they are a give_prog p with different keyword lists but some of the same keywords – for example a give_prog p apple red juicy and a give_prog p apple red poisoned. SPECIAL NOTES: More often than not, you'll want to remember to have the mob use the mpjunk command to get rid of the object given so people cannot steal the item back and use it again. It does depend on what you are doing of course, but it is something to keep in mind. It is also not a bad idea to have a give_prog all to have the mob drop items other than the ones it will accept in other give_progs. ### giving_prog Usage:
    giving_prog [keyword list]
    giving_prog p [keyword list]
    giving_prog all
This type of mobprog is triggered by the mob giving someone an object. If the object given to the mob matches the keywords of the giving_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the object must exactly match that of the giving_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If a giving_prog all is used, then the giving_prog will trigger from any object at all being given to anyone by the mob. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    giving_prog orange apple banana
This will trigger if the mob gives an object that has any of the keywords orange, apple, or banana. This means that it would be triggered by giving a banana, an apple pie, or even an orange shield.)
    giving_prog p apple pie delicious
This will trigger if the mob gives an object that has the exact keywords apple pie delicious. The prog would not be triggered by giving an object with keywords red apple or blackberry pie or anything except the exact order and wording of the keyword list.
    giving_prog all
This will trigger if any object is being given by the mob MULTIPLE PROGS: You can have more than one giving_prog on a mob. Generally it is best not to have giving_progs with the same keywords in them, unless they are a giving_prog p with different keyword lists but some of the same keywords – for example a giving_prog p apple red juicy and a giving_prog p apple red poisoned. SPECIAL NOTES: More often than not, you'll want to remember to have the mob use the mpjunk command to get rid of the object given so people cannot steal the item back and use it again. It does depend on what you are doing of course, but it is something to keep in mind. It is also not a bad idea to have a giving_prog all to have the mob drop items other than the ones it will accept in other giving_progs. ### greet_prog Usage:
    greet_prog [integer percentage]
This type of mobprog checks a percentage chance every time someone enters the room that the scripted mob, item, room, or exit is currently in. If the random number generated between 1 and 100 is equal to or below the percentage of the greet_prog, the prog is triggered. Note that greet_progs are triggered by both non-sneaking players and mobs, and a mob in a maze can actually sometimes end up triggering itself! This type of mobprog has all sorts of uses, ranging from giving in-zone quest information to people entering the room, creating aggressive progs, etc. EXAMPLES:
    greet_prog 25
This prog will be triggered 25% of the time when someone enters the room where the mob currently is.
    greet_prog 100
This prog will be triggered 100% of the time when someone enters the room where the mob currently is. This means every time. SPECIAL NOTES: You'll probably want to do a large number of if checks in greet_progs, specifically in the difference between mobs and player characters. Note that greet_progs will trigger except if a person is sneaking. Also, the mob must have detect invisibility to see invisible people, infravision to see people in the dark, and will not see people if blinded. Lastly, make sure you check out arrive_prog, which is a useful counterpart to greet_prog ### hitprcnt_prog Usage:
    hitprcnt_prog [integer percentage]
This type of mobprog checks every round of combat to see if the mob's hit points are equal to or under the percentage given to the hitprcnt_prog. This type of prog is used mainly to have the mob do something at a certain percentage of hit points. Keep in mind, however, that this prog will trigger EVERY round of combat in which the mob's hit points are under the percentage. So if you want the mob to do only one thing, you will have to set up the mobprog that way with if checks. EXAMPLES:
    hitprcnt_prog 50
This will trigger if the mob's hit points are 50% or under every round of combat.
    hitprcnt_prog 100
This will trigger if the mob's hit points are 100% or under every round of combat. This means, more or less, every round of combat the mob will ever be in. ### imask_prog Usage:
    imask_prog [trigger message]
    imask_prog p [trigger message]
This type of mobprog will trigger when the mob does a thing that generates a certain string of text. When the 'p' is inserted into the trigger line, the string of text must be precise, while if it is not, any of the words in the list can trigger the mobprog. This type of mobprog has many uses, one of which is to have one action trigger another. The possibilities are almost endless, except that this trigger is meaningless unless the scripted object is a mob, since only mobs can generate events. EXAMPLES:
    imask_prog wolf dog coyote
This will trigger whenever the mob does something that generates a segment of text containing any of the words wolf, dog, or coyote. If the string contains more than one of these, the prog will be triggered multiple times.
    imask_prog p A wolf howls at the moon.
This will trigger the prog when mob does something that generates this precise message. Note that punctuation is important here as well. MULTIPLE PROGS: You can have more than one imask_prog on a mob, but you shouldn't have multiple imask_progs that trigger off of the same message. SPECIAL NOTES: ANSI colors on objects don't seem to work well with imask_progs, so avoid using ANSI colors in anything that may be part of your imask_prog trigger. Variables and Codes are not used in imask_progs, so do not try to use them; it won't work. ### kill_prog Usage:
    kill_prog
This mobprog type triggers when the mob causes death. The kill_prog has a wide range of uses. The kill_prog is queued just before the target dies, so it is considered to be the target's last gasp. At the end of the kill-prog, however, the target dies. Even if the target sets its hit points to full, it will die. Other than that, the mob can mpjunk equipment it has, mptrasnfer a new room to die, unlock a door, load an object of some kind, etc. MULTIPLE PROGS: You can have multiple kill_progs on the same mob. ### level_prog Usage:
    level_prog [integer percentage]
This type of mobprog checks a percentage chance every time a player gains a level anywhere in the game. If the random number generated between 1 and 100 is equal to or below the percentage of the level_prog, the prog is triggered. EXAMPLES:
    level_prog 25
This prog will be triggered 25% of the time when someone levels.
    level_prog 100
This prog will be triggered 100% of the time when someone levels. This means every time. SPECIAL NOTES: This program will trigger every time a player levels, regardless of whether they are in the same room, or even whether the scripted monster can see or detect the player. The exception to this is cloaked admins, which will not trigger. ### lock_prog Usage:
    lock_prog [keyword list]
    lock_prog p [keyword list]
    lock_prog all
This type of mobprog is triggered by locking a container or door. If the script is on a container-type object, such as a door or container item, it will trigger only if the object being locked is the scripted one. If the target matches the keywords of the lock_prog, the prog is triggered. If there is a 'p' placed before the keyword list, the keywords of the object must exactly match that of the lock_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If the scripted item is not a container or door, and a "lock_prog all" is used, then the lock_prog will trigger from any object at all being locked. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. As is normal, if the scripted object is a mob, this event will not trigger if the scripted mob is the originator of the activity. EXAMPLES:
    lock_prog door gate
This will trigger if the object locked has any of the keywords door gate. This means that it would be triggered by locking a door or gate.
    lock_prog p a large chest
This will trigger if the object locked has the exact keywords a large chest.. The prog would not be triggered by locking an object with keywords large or chest or anything except the exact order and wording of the keyword list.
    lock_prog all
This will trigger if any object is locked.) MULTIPLE PROGS: You can have more than one lock_prog on an item, mob, or room. Generally it is best not to have lock_progs with the same keywords in them, unless they are a lock_prog p with different keyword lists but some of the same keywords - for example a lock_prog p door gate and a lock_prog p door to the gate ### login_prog Usage:
    login_prog [integer percentage]
This type of mobprog checks a percentage chance every time someone enters the game. If the random number generated between 1 and 100 is equal to or below the percentage of the login_prog, the prog is triggered. EXAMPLES:
    login_prog 25
This prog will be triggered 25% of the time when someone enters the game.
    login_prog 100
This prog will be triggered 100% of the time when someone enters the game. This means every time. SPECIAL NOTES: This program will trigger every time a player enters the game, regardless of whether they are in the same room, or even whether the scripted monster can see or detect the player. The exception to this is cloaked admins, which will not trigger ### logoff_prog Usage:
    logoff_prog [integer percentage]
This type of mobprog checks a percentage chance every time someone leaves the game. If the random number generated between 1 and 100 is equal to or below the percentage of the logoff_prog, the prog is triggered. EXAMPLES:
    logoff_prog 25
This prog will be triggered 25% of the time when someone leaves the game.
    logoff_prog 100
This prog will be triggered 100% of the time when someone leaves the game. This means every time. SPECIAL NOTES: This program will trigger every time a player leaves the game, regardless of whether they are in the same room, or even whether the scripted monster can see or detect the player. The exception to this is cloaked admins, which will not trigger. ### llook_prog ### look_prog Usage:
    look_prog [keyword list]
    look_prog p [keyword list]
    look_prog all
    llook_prog [keyword list]
    llook_prog p [keyword list]
    llook_prog all
This type of mobprog is triggered by looking at the scripted item. The "llook" version triggers if the item is "examined". If the target matches the keywords of the lock_prog, the prog is triggered. If there is a 'p' placed before the keyword list, the keywords of the object must exactly match that of the look_prog. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. As is normal, if the scripted object is a mob, this event will not trigger if the scripted mob is the originator of the activity. EXAMPLES:
    llook_prog all
This will trigger if any the scripted item, room, or mob is examined.
    look_prog all
This will trigger if any the scripted item, room, or mob is looked at. MULTIPLE PROGS: It is generally useless to have more than one look_prog on an item, mob, or room. ### once_prog Usage:
    once_prog
This type of mobprog is triggered immediately by the script engine under all circumstances, but is never triggered again. This makes it useful for doing initialization or other tasks which only need to be done once after the mud boots. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    once_prog
This will trigger once, right away MULTIPLE PROGS: You can have only one once_prog on a mob. ### open_prog Usage:
    open_prog [keyword list]
    open_prog p [keyword list]
    open_prog all
This type of mobprog is triggered by opening a container or door. If the script is on a container-type object, such as a door or container item, it will trigger only if the object being opened is the scripted one. Otherwise, if the target matches the keywords of the open_prog, the prog is triggered. If there is a 'p' placed before the keyword list, the keywords of the object must exactly match that of the open_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If the scripted item is not a container or door, and a "open_prog all" is used, then the open_prog will trigger from any object at all being opened. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. As is normal, if the scripted object is a mob, this event will not trigger if the scripted mob is the originator of the activity. EXAMPLES:
    open_prog door gate
This will trigger if the object opened has any of the keywords door gate. This means that it would be triggered by opening a door or gate.
    open_prog p a large chest
This will trigger if the object opened has the exact keywords a large chest.. The prog would not be triggered by opening an object with keywords large or chest or anything except the exact order and wording of the keyword list.
    open_prog all
This will trigger if any object is opened. MULTIPLE PROGS: You can have more than one open_prog on an item, mob, or room. Generally it is best not to have open_progs with the same keywords in them, unless they are a open_progs p with different keyword lists but some of the same keywords - for example a open_prog p door gate and a open_prog p door to the gate. ### quest_time_prog Usage:
    quest_time_prog [quest name] [number of minutes remaining]
This kind of mobprog triggers only if the script is part of an official Quest, and only if the number of minutes remaining in the quest is equal to the number of minutes specified. This is used as part of a quest plot line, to allow the mobs to give warnings about a quest that is running out of time. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. EXAMPLES:
    quest_time_prog 'my quest' 20
This quest_time_prog will be triggered on the final 20th minute of the quest 'my quest'.
    quest_time_prog 'my quest' 1
This quest_time_prog will be triggered on the final minute of the quest 'that quest'. ### put_prog Usage:
    put_prog [keyword list]
    put_prog p [keyword list]
    put_prog all
This type of mobprog is triggered by observing something being put in a container, or by the scripted object being a matching container that something is being put into. It does not trigger if the scripted object is the thing being put into the container. Now, if the container involved matches the keywords of the put_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the object must exactly match that of the put_prog. If there is not, then any container with any of the keywords in the list in it will trigger it. If a put_prog all is used, then the put_prog will trigger from any container at all being used. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    put_prog chest bag drawer
This will trigger if the container used has any of the keywords chest, bag, or drawer. This means that it would be triggered by putting something into a chest, an awful bag, or even an chester drawers.
    put_prog p a large wooden chest
This will trigger if the container used up has the exact keywords a large wooden chest. The prog would not be triggered by putting anything into a container with keywords wooden chest or wooden sword or anything except the exact order and wording of the keyword list.
    put_prog all
This will trigger if any container is used. MULTIPLE PROGS: You can have more than one put_prog on a mob. Generally it is best not to have put_progs with the same keywords in them, unless they are a put_prog p with different keyword lists but some of the same keywords – for example a put_prog p apple red juicy and a put_prog p apple red poisoned. ### putting_prog Usage:
    putting_prog [keyword list]
    putting_prog p [keyword list]
    putting_prog all
This type of mobprog is triggered by putting a matched thing into a container. It does not trigger if the scripted object is the container itself, however. If the object being put into the container matches the keywords of the put_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the object must exactly match that of the putting_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If a putting_prog all is used, then the putting_prog will trigger from any item being put in any container at all. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    putting_prog key skeleton
This will trigger if an object with the keywords key or skeleton is being put into a container.
    putting_prog p the skeleton key
This will trigger if the item with exact keywords the skeleton key is being put into a container. The prog would not be triggered by items with keywords skeleton or the key or anything except the exact order and wording of the keyword list.
    putting_prog all
This will trigger if any item is being put somewhere. MULTIPLE PROGS: You can have more than one putting_prog on a mob. Generally it is best not to have putting_progs with the same keywords in them, unless they are a put_prog p with different keyword lists but some of the same keywords – for example a putting_prog p apple red juicy and a putting_prog p apple red poisoned. ### rand_prog Usage:
    rand_prog [integer percentage]
This kind of mobprog checks a percentage chance every tick. If the random number generated between 1 and 100 is equal to or below the percentage of the rand_prog, then it will be triggered. This type of mobprog can be triggered at any time, so long as the mob is alive, including while it is sleeping or fighting. They are very useful for setting up certain elements of your zone, or for giving personality to your mobs, such as having a blacksmith who pounds out a sword. This kind of mobprog ONLY goes off when a player is in the same zone that your mob is in. EXAMPLES:
    rand_prog 20
This rand_prog will be triggered 20% of each tick.
    rand_prog 75
This rand_prog will be triggered 75% of each tick. SPECIAL NOTES: While using rand_progs seems really easy, having a lot of them can slow down your zone. Having extremely long rand_progs on many, many mobs is generally not a good idea. If possible, consider other options, and only use rand_progs that go off at a high rate on mobs that will perform the rand_prog once and then never again, either because they have some sort of internal check, or because they go and mppurge themselves afterwards. ### regmask_prog Usage:
    regmask_prog [java regular expression]
    regmask_prog p [exact, case sensitive message]
This type of mobprog will trigger when the mob sees a certain string of text. When the 'p' is inserted into the trigger line, the string of text must be precisely the same, case included, as the string generated. If 'p' is not the first character, then the trigger will attempt to find the first match of the given java regular expression string. This type of mobprog has many uses, one of which is communication between mobs. There are a few socials which create a message only to the person performing them and to the one receiving them. You can use these and act_progs to safely have mobs trigger each other, without people seeing what is going on. Other uses include triggering off of people fleeing, moving out of the room, etc. The possibilities are endless. EXAMPLES:
    regmask_prog a*be
This will trigger whenever the mob sees a segment of text starting with the lowercase letter a, then containing 0 or more other letter as followed by the string "be". This would match aaaaabe
    regmask_prog p A wolf howls at the moon.
This will trigger the prog when it sees this precise message. Note that punctuation and case is important here as well. MULTIPLE PROGS: You can have more than one regmask_prog on a mob, but you shouldn't have multiple regmask_progs that trigger off of the same message. SPECIAL NOTES: ANSI colors on objects don't seem to work well with regmask_progs, so avoid using ANSI colors in anything that may be part of your regmask_prog trigger. Variables and Codes are not used in regmask_progs, so do not try to use them; it won't work. ### remove_prog Usage:
    remove_prog [keyword list]
    remove_prog p [keyword list]
    remove_prog all
This type of mobprog is triggered by removing an object. If the object removed matches the keywords of the remove_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the object must exactly match that of the remove_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If a remove_prog all is used, then the remove_prog will trigger from any object at all being removed by the mob. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    remove_prog orange apple banana
This will trigger if the object removed has any of the keywords orange, apple, or banana. This means that it would be triggered by removing a banana, an apple pie, or even an orange shield.
    remove_prog p apple pie delicious
This will trigger if the object removed has the exact keywords apple pie delicious. The prog would not be triggered by removing an object with keywords red apple or blackberry pie or anything except the exact order and wording of the keyword list.
    remove_prog all
This will trigger if any object is removed. MULTIPLE PROGS: You can have more than one remove_prog on a mob. Generally it is best not to have remove_progs with the same keywords in them, unless they are a remove_prog p with different keyword lists but some of the same keywords – for example a remove_prog p apple red juicy and a remove_prog p apple red poisoned. ### sell_prog Usage:
    sell_prog [keyword list]
    sell_prog p [keyword phrase]
    sell_prog all
This type of mobprog is triggered by selling an item to a shopkeeper. If the item being sold has any of the keywords of the sell_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the item must exactly match that of the sell_prog. If there is not, then any item with any of the keywords in the list in it will trigger it. If a sell_prog all is used, then the sell_prog will trigger for any item at all being sold. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    sell_prog orange apple banana
This will trigger if the item being sold has any of the keywords orange, apple, or banana. This means that it would be triggered by selling a banana, an apple pie, or even an orange shield.
    sell_prog p apple pie delicious
This will trigger if the item being sold has the exact keywords apple pie delicious. The prog would not be triggered by selling anything with keywords red apple or blackberry pie or anything except the exact order and wording of the keyword list.
    sell_prog all
This will trigger if any sort of item is sold. MULTIPLE PROGS: You can have more than one sell_prog on a mob. Generally it is best not to have sell_progs with the same keywords in them, unless they are a sell_prog p with different keyword lists but some of the same keywords – for example a sell_prog p apple red juicy and a sell_prog p apple red poisoned. ### social_prog Usage:
    social_prog [social name]
This type of mobprog is triggered by a social of the looked for name being done in the same room. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    social_prog smile
This will trigger if the smile social is done in the same room as the scripted object. MULTIPLE PROGS: You can have more than one social_prog on a mob. Generally it is best not to have social_progs with the same social trigger in them. ### speak_prog Usage:
    speak_prog [trigger message]
    speak_prog p [trigger message]
This type of mobprog is triggered by the scripted mob saying the trigger line, or if the scripted object is not a mob, it is the same as speech_prog below. If a 'p' is inserted in the prog as above, the line spoken must exactly match the trigger message; if it is not, then any of the keywords listed will trigger the mobprog. A keyword of ALL will trigger on any speech. This type of mobprog is useful for quests driven by player scripts or setting up passwords that must be spoken. This type of prog can also be used to have a mob trigger itself if you want to have multiple connected progs – see complex progs for details. Note that this kind of mobprog is only triggered by someone using the say command. EXAMPLES:
    speak_prog dog wolf coyote
This will trigger the prog whenever dog, wolf, or coyote is said by the scripted mob. If more than one of the keywords is spoken in the same line, the prog will trigger more than once.
    speak_prog p The dog barks at the cat
This will trigger the prog only if the exact expression is said. Note that punctuation counts, although you don't *have* to use it. MULTIPLE PROGS: You can have more than one speak_prog on a mob. It is generally not a good idea to have more than one speak_prog be triggered by the same expression. ### speech_prog Usage:
    speech_prog [trigger message]
    speech_prog p [trigger message]
This type of mobprog is triggered by someone other than the scripted mob saying the trigger line, be it mob or player, in the same room as the scripted object. If a 'p' is inserted in the prog as above, the line spoken must exactly match the trigger message; if it is not, then any of the keywords listed will trigger the mobprog. A keyword of ALL will trigger on any speech. This type of mobprog is useful for setting up internal quests, giving out background information to people exploring your zone, or setting up passwords that must be spoken. This type of prog can also be used to have a mob trigger itself if you want to have multiple connected progs – see complex progs for details. Note that this kind of mobprog is only triggered by someone using the say command. EXAMPLES:
    speech_prog dog wolf coyote
This will trigger the prog whenever dog, wolf, or coyote is said in the room with the mob. If more than one of the keywords is spoken in the same line, the prog will trigger more than once.
    speech_prog p The dog barks at the cat
This will trigger the prog only if the exact expression is said. Note that punctuation counts, although you don't *have* to use it. MULTIPLE PROGS: You can have more than one speech_prog on a mob. It is generally not a good idea to have more than one speech_prog be triggered by the same expression. ### time_prog Usage:
    time_prog [list of hours in the day]
This type of mobprog triggers once per mud hour, on the hours of the day listed. This allows you to have a script which triggers infrequently. There are 16 hours per day (0-15) in CoffeeMud. EXAMPLES:
    time_prog 10 1 2
This will trigger if hour of the day is 10, 1, or 2.
    time_prog 3
This will trigger on the 3rd hour of every day. ### unlock_prog Usage:
    unlock_prog [keyword list]
    unlock_prog p [keyword list]
    unlock_prog all
This type of mobprog is triggered by unlocking a container or door. If the script is on a container-type object, such as a door or container item, it will trigger only if the object being unlocked is the scripted one. If the target matches the keywords of the unlock_prog, the prog is triggered. If there is a 'p'; placed before the keyword list, the keywords of the object must exactly match that of the unlock_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If the scripted item is not a container or door, and a "unlock_prog all" is used, then the unlock_prog will trigger from any object at all being unlocked. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. As is normal, if the scripted object is a mob, this event will not trigger if the scripted mob is the originator of the activity. EXAMPLES:
    unlock_prog door gate
This will trigger if the object unlocked has any of the keywords door gate. This means that it would be triggered by unlocking a door or gate.
    unlock_prog p a large chest
This will trigger if the object unlocked has the exact keywords a large chest.. The prog would not be triggered by unlocking an object with keywords large or chest or anything except the exact order and wording of the keyword list.
    unlock_prog all
This will trigger if any object is unlocked. MULTIPLE PROGS: You can have more than one unlock_prog on an item, mob, or room. Generally it is best not to have unlock_progs with the same keywords in them, unless they are a unlock_prog p with different keyword lists but some of the same keywords - for example a unlock_prog p door gate and a unlock_prog p door to the gate. ### wear_prog Usage:
    wear_prog [keyword list]
    wear_prog p [keyword list]
    wear_prog all
This type of mobprog is triggered by wearing, wielding, or holding an item. If the object worn matches the keywords of the wear_prog, the prog is triggered. If there is a ‘p' placed before the keyword list, the keywords of the object must exactly match that of the wear_prog. If there is not, then any object with any of the keywords in the list in it will trigger it. If a wear_prog all is used, then the wear_prog will trigger from any object at all worn. This type of prog is usually used for in-zone quests and special mob behavior, and has a variety of uses. EXAMPLES:
    wear_prog orange apple banana
This will trigger if the object worn has any of the keywords orange, apple, or banana. This means that it would be triggered by wearing a banana, an apple pie, or even an orange shield.
    wear_prog p apple pie delicious
This will trigger if the object worn has the exact keywords apple pie delicious. The prog would not be triggered by wearing an object with keywords red apple or blackberry pie or anything except the exact order and wording of the keyword list.
    wear_prog all
This will trigger if any object is worn. MULTIPLE PROGS: You can have more than one wear_prog on a mob. Generally it is best not to have wear_progs with the same keywords in them, unless they are a wear_prog p with different keyword lists but some of the same keywords – for example a wear_prog p apple red juicy and a wear_prog p apple red poisoned. ## Scripting Codes Most commands in your scripts allow you to use variable-like scripting Codes instead of literals. A literal is a specific static string or number, such as 'the hairy blog' or 'green' or '72'. A scripting code, however, is a special string which represents a literal and stands for it in your scripts. Understanding scripting codes is absolutely necessary for you to write scripts successfully. When a DEATH_PROG triggers, for example, it is impossible for the commands that execute to guess the name of the mobs killer. Therefore the name of the killer is stored in a scripting code for you. In this case, that code is $n. This allows you to use the code $n in your DEATH_PROG commands and be sure that wherever you use it, it is referring to "the creature that killed me". Also, when using commands that cause strings to echo, you may want to use a pronoun to refer to the creature who triggers an event. Guessing, however, won't work here either. In the case of our DEATH_PROG example, we could use the code $m and be sure that, whever it appears, the word 'his', 'her', or 'it' will replace it appropriately. Below is a list of the simple scripting codes, along with their meaning. The term 'monster' below refers to whatever object, mob, item, room, exit, etc actually has the Scriptable behavior and is running the script. Otherwise, we also refer to the source of the trigger event and the target of the trigger event. For instance, when someone 'A' gets a sword off the ground in front of a mob 'B' with the Scriptable behavior, the MASK_PROG might trigger with the monster being the mob 'B', the source being the someone 'A', and the target being the sword.
$a | Name of the area the monsters in.
$b | Name of last mob or item loaded with MPMLOAD or MPOLOAD commands
$B | Display text of last mob or item loaded with MPMLOAD or MPOLOAD commands
$c | A random pc or npc inhabitants name
$C | A random pc or npc inhabitants name
$i | The Monsters name.
$I | The Monsters display text.
$n | The Source of the triggers name.
$N | The Source of the triggers name.
$t | The Target of the triggers name.
$T | The Target of the triggers name.
$r | A random pc inhabitants name.
$R | A random pc inhabitants name.
$j | The pronoun he/she of the monster.
$e | The pronoun he/she of the source of the trigger.
$f | Name of the person which the monster follows.
$E | The pronoun he/she of the trigger target.
$F | The he/she of the person which the monster follows.
$J | The pronoun he/she of a random pc inhabitant.
$k | The possessive pronoun his/her of the monster.
$h | The pronoun him/her of the monster.
$H | The pronoun him/her of a random pc inhabitant.
$l | A list of visible mobs (excluding monster). See "." syntax below.
$L | A list of visible Items in room. See "." syntax below.
$m | The pronoun his/her of the source of the trigger.
$M | The pronoun his/her of the target of the trigger.
$s | The pronoun him/her of the source of the trigger.
$S | The pronoun him/her of the target of the trigger.
$d | The title of the room of the scripted monster.
$D | The long description of the room of the scripted monster.
$K | The pronoun his/her of a random pc inhabitant.
$o | The name of item#1.
$O | The name of item#1.
$p | The name of item#2.
$P | The name of item#2.
$w | The name of the owner of item#1.
$W | The name of the owner of item#2.
$g | The lowercase form of the message or parameters from a MPCALLFUNC, MASK_PROG or SPEECH_PROG.
$G | The uppercase form of the message or parameters from a MPCALLFUNC, MASK_PROG or SPEECH_PROG.
$x | Displays a random (or specified) exit by the exits direction code (north, south, etc)
$X | Displays a random (or specified) exit by the exits direction name (door, etc etc)
$xN | Specified directions name (Where N may be N, S, E, W, U, or D). Will display the direction Code. Use $X for exit name.
$0 .. $9 | Temporary variables used by other commands, especially FOR, MPARGSET command.
$<[code] [var name]> | The variable of the given name, and the given code. Where code is $i, $n, $t, $o, $w, $W, or $p. See MPSETVAR below.
${[num] [*/quest name]} | A mob name from the given quest, if the quest is running. The number corresponds to the order in which mobs were designated in the quest script. Counting starts at 1.
$[[num] [*/quest name]] | An item name from the given quest, if the quest is running. The number corresponds to the order in which items were designated in the quest script. Counting starts at 1.
Any of the above codes may be followed by a period and a literal number to designate a particular word inside a string of many words. For instance, if $o evaluates to "a magic wand", then $o.1 would evalulate to "magic". If $l evaluated to "orc bob hassan", then $l.2 would give "hassan". This can be very useful when used with the $l or $L codes to iterate through the contents of a room. This syntax can also be used to generate substrings by following the number with two periods "..". For instance, of $l evaluates to "orc bob hassan", then $l.1.. would give "bob hassan". You can also add .LENGTH# to the end of a variable to return the number of words contained inside the string. The last code we are going to discuss is also the most powerful. It allows you to fill in a value from a function call. The format of this code is as follows:
$%[function name]([parameters])% | This will replace the code with a value from one of the internal functions listed below. While the names are the same as the eval functions used in IF statements, their parameters will be slightly different.
The [function name] must be the name of one of the functions listed in the following chart. All functions must have parenthesis after their names, and most functions require one or more parameters inside the parenthesis. The parameters usually include a [code]. This may be either the string name of either a mob or an item (whichever is appropriate to the function), or a code from the previous chart which represents a mob or an item. The description for each function will specify whether mob names or codes representing mobs are more appropriate, or whether item names or codes representing items are more appropriate. Here is an example of this code being used in a say statement:
    say I am $%isgood($i)% and my favourite number is $%rand()%.
This string would replace the $%.. codes with the results of the given function calls. Here is the list of accepted functions for the $% code. Where 'monster' is referred to below, you may assume this to be whatever object (mob, item, room, exit) which has the Scriptable behavior on it. Usually this is an npc mob. In the case of an item, it refers to a mob who takes the place of the item for scripting purposes. For this reason, using $i and $I codes, or using functions which only return information about the scripted monster when an item is being scripted is totally useless.
AFFECTED([code]) | Returns the name of a random spell affect on the given mob or item.
BASECLASS([code]) | Returns the base class of the given mob.
CALLFUNC([function name] [parms]) | Calls the FUNCTION_PROG of the given name, with the given parameters, and returns the value returned by the program using the RETURN statement.
CLAN([code]) | Returns the prominent rivalrous clan of the given mob.
CLANRANK([code]) | Returns the rank of the given mob in their prominent rivalrous clan.
CLANQUALIFIES([code]) | Returns a description of the qualifications for clan [code]
CLANDATA([clan code] [variable]) | Returns data about the given clan. See CLANDATA function below for variables.
CLASS([code]) | Returns the class of the given mob.
CURRENCY([code]) | Returns the native currency of the given mob or coins.
DATETIME([TYPE]) | Returns the hour, day, month, or year. For type, use HOUR, DAY, MONTH, or YEAR.
DEITY([code]) | Returns the deity of the given mob.
EVAL() | Not implemented -- do not use.
EXP([code]) | Returns the experience points of the given mob.
EXPERTISE([code] [id] [flag]) | Returns expertise num for mob, ability id, and expertise flag.
EXPLORED([code] [areaname or world]) | Returns the % the given mob has explored of the world or the specified area.
FACTION([mob code] [faction id]) | Returns the range name for the given mob within the given faction.
GOLDAMT([code]) | Returns the total value of the money the given mob has, or value of item, expressed in base gold.
GSTAT([code] [stat variable]) | Value of the given stat variable for the given mob or item. For example: $%GSTAT($i strength)% See the MPGSET command below for a complete list of variables.
HAS([code]) | Returns the name of a random item in the scripted monsters inventory.
HASNUM([code] [item name]) | Returns the number of a given item in the given mob or rooms inventory.
HASACCTATTOO([mob[) | Returns space delimited list of tattoos on the mobs player common account
HASTATTOO([mob code]) | Returns space delimited list of tattoos on the mob
HASTATTOOTIME([m] [t]) | Returns the ticks remaining on the tattooo for mob code [m] and tattoo name [t]
HASTITLE([code]) | Returns the selected title of the given player mob.
HITPRCNT([code]) | Return the % of hit points remaining for the given mob.
INAREA() | Returns the name of the area the scripted monster is in.
INCONTAINER([code]) | Teturns the name of the container of the given item, or the mount of the given mob, depending on the code.
INLOCALE() | Returns the name of the room type the monster is in (plains, city, mountains, hills, watersurface, etc).
INROOM() | Returns the raw id of the room the scripted monster is in.
IPADDRESS([code]) | Returns the ipaddress of the player.
ISABLE([code] [skill name]) | Returns the given mobs proficiency in the given skill/spell/ability.
ISALIVE([code]) | Returns the health of the given mob.
ISBEHAVE([code]) | Returns the class ids of the behaviors on the given mob or item.
ISBIRTHDAY([code]) | Returns a description of the given mobs birthday date.
ISCHARMED([code]) | Returns the name of the charm spell the mob is under.
ISCONTENT([code]) | Returns list of all content/riders in container/rideable code.
ISDAY() | Returns the day of the mud month
ISEVIL([code]) | Returns the short alignment string of the given mob.
ISFIGHT([code]) | Returns the name of the creature the given mob is fighting, or nothing otherwise.
ISFOLLOW([code]) | Returns the name of the creature the given mob is following, or nothing otherwise.
ISGOOD([code]) | Returns the alignment string of the given mob.
ISHERE() | Returns the name of the area the scripted monster is in.
ISHOUR() | Returns the mud hour number
ISIMMORT([code]) | not implemented.
ISLIKE([zapper mask]) | Returns human-readable description of the given mask.
ISLOCKED([code or direction]) | Returns the key name if the given container name or direction has a lock. The code may refer to an item container with a lock, or a direction name, such as north, south, east, etc.
ISMOON() | Returns the moon phase description.
ISMONTH() | Returns the month of the mud year
ISNAME([code]) | Returns the real/full name of the given object.
ISNEUTRAL([code]) | Returns the alignment number of the given mob (0-1000).
ISNPC([code]) | Not implemented -- do not use.
ISODD([number]) | Echoes back the number if it is an odd whole number.
ISOPEN([code or direction]) | Returns "true" if the container item is open, or the exit in the given direction name is open.
ISPC([code]) | Not implemented -- do not use..
ISQUESTMOBALIVE([quest name]) | Returns a list of all live mobs designated by the given quest.
ISRECALL([code]) | Returns the start room of the given mob.
ISRLHOUR() | Returns the real-life hour 0-23
ISRLDAY() | Returns the real-life day of the month 1-31
ISRLMONTH() | Returns the real-life month of the year 1-12
ISRLYEAR() | Returns the real-life year
ISSEASON() | Returns the name of the season.
ISSERVANT([code]) | Returns the name of the creature the given mob is serving, or nothing otherwise.
ISSPEAKING([code]) | Returns the language being spoken by the given mob, or Common.
ISTIME() | Returns the approximate time of day in words.
ISWEATHER() | Returns a description of the weather in a short sentence.
ISYEAR() | Returns the mud-year
ITEMCOUNT([code]) | Returns the complete individualized count of items on the object
LEVEL([code]) | Returns the level of the given mob.
MATH([expression]( | Returns result of evaluated mathematical expression. Use +, -, *, or \
MOBITEM([code] [integer number]) | Returns the nth item owned by the given mob.
MOOD([code]) | Returns the mood of the given mob.
NUMBER([integer number or code]) | Returns the numeric value of the given argument.
NUMITEMSMOB([code]) | Returns the number of items the given mob has.
NUMITEMSROOM() | Returns the number of items in the room.
NUMITEMSSHOP([code]) | Returns the number of items in the shop inventory of the given shop code.
NUMMOBS([name]) | Returns the number of mobs in the world matching the given mob name.Can also use MASK=<zapper mask> to pick out certain kinds of mobs.
NUMMOBSINAREA([name]) | Returns the number of mobs in the scripted monsters area matching the given mob name.Can also use MASK=<zapper mask> to pick out certain kinds of mobs.
NUMMOBSROOM([*/name]) | Returns the number of mobs in the same room as the scripted monster, including the monster, whose name or display text matches the name pattern. Can also use MASK=<zapper mask> to pick out certain kinds of mobs.
NUMPCSAREA() | Returns the number of pcs in the same area as the scripted monster.
NUMPCSROOM() | Returns the number of pcs in the same room as the scripted monster.
NUMRACEINAREA([race name]) | Returns the number of mobs in the same area as the scripted monster whose race matches the given string.
NUMRACES([race name]) | Returns the number of mobs in the world whose race matches the given string.
POSITION([code]) | Returns the sitting/standing/sleeping position name of the given mob.
PRACS([code]) | Returns the number of practices the given mob has.
QUESTAREA([quest name]_ | Returns a list of all unique areas that have had rooms specified by the given quest.
QUESTOBJ([quest name]) | Returns a list of all items designated by the given quest.
QUESTMOB([quest name]) | Returns a list of all mobs designated by the given quest.
QUESTPOINTS([code]) | Returns the number of quest points the given mob has.
QUESTROOM([quest name]) | Returns a list of all room ids designated by the given quest.
QUESTSCRIPTED[code] | Returns a list of the quests the given mob is scripted for (is on).
QUESTWINNER([code]) | Returns a list of the quests the given mob has won.
QVAR([*/quest name] [var]) | Returns value of one of the internal Quest variable strings, See MPQSET for more info.
RACE([code]) | Returns the name of the race of the given mob.
RACECAT([code]) | Returns the racial category of the given mob.
RAND() | Returns random number between 1 and 100.
RAND0NUM([integer number or code]) | Returns a random number from 0..given value-1.
RANDNUM([integer number or code]) | Returns a random number from 1..given value.
ROOMITEM([integer number]) | Returns the name of the nth item in the same room as the scripted monster.
ROOMMOB([integer number]) | Returns the name of the nth mob in the same room as the scripted monster.
SEX([code]) | Returns the sex of the given mob.
SHOPHAS([code]) | Returns a random item from the shop inventory of the given shopkeeper code. Sets $9 to price.
SHOPITEM([code] [integer number]) | Returns the nth item from the shop inventory of the given shopkeeper code. Sets $9 to price.
STAT([code] [stat variable]) | Returns the value of the given stat for the given object, mob, or item. See MPSET in the section on Commands for more information.
STRIN([string] [string]) | Returns the word number (0..n) where the second string appears in the first. This function deals in whole words only.
TRAINS([code]) | Returns the number of training points the given mob has.
VALUE([code] [currency name]) | Returns the base value of the mob or coins but only in the given currency.
VAR([code] [variable name]) | Returns the value of the given variable. See MPSETVAR in the section on Commands for more information.
WORN([code]) | The name of a random worn item in the given mobs inventory.
WORNON([code] [loc string]) | List of all items worn by code mob on location "loc string".
## Scripting Commands Commands inside your scripts should each be terminated by a carriage return (ENTER) or a semicolon, depending upon the manner in which your script is presented. Commands are of two general types: MUD Commands, and MOBPROG (MP) Commands. MUD Commands you should already be familiar with, as they include commands such as GET, PUT, SAY, DROP, etc. It is not within the scope of this document to list or describe the standard MUD Commands. The help files inside the mud itself can do a far better job. It is sufficient to say that issuing the command in your script cause the scripted mob to attempt to perform the command exactly as it is written. If you enter a script line such as:
    get sword
.. and there is a sword, the mob will get it. If there is NO sword, the mob will not appear to be doing anything at all. MP Commands are what we will be discussing in more detail here. Like MUD Commands, they each have a syntax and structure which must be followed.
    commandword parameter1 parameter2 ... parametern
Like MUD Commands, MP Commands all have a key command word followed by one or more parameters. As in MUD Commands, those parameters are delimited by spaces. If you need to specify a single parameter which contains a space, you would put double quotes (") around the parameter.
    say "the scary monster" hi!
In an MP Command, however, this is not true. In an MP Command, the single quote (') is used around a parameter when it contains spaces. Keep this difference in mind when writing your scripts, lest you run into problems. This difference is actually more important with MP Functions. This is because most MP Commands only have one parameter, so that parameter word grouping using quotes is usually not necessary. ### if, else, endif Usage:
    if [condition]
    [commands]
    else
    [commands]
    ...
    endif
The if command is the cornerstone of Scripting, and the only other condition mechanism outside of the MPWHILE command. The way the if command works is by deciding whether or not the condition that is given is true, and if so, executing the commands following the if condition. When the condition is not true, the commands before an endif statement or, (if given), an else statement are not executed. If an else statement lies between an if statement and the endif statement, then the statements between the else statement and the endif statement will be executed whenever the condition is false, but not ever if the condition is true. Either way, statements after an endif statement are executed regardless. Every if statement MUST have a corresponding endif statement somewhere after it. The else statement is completely optional, but if it is used, it must be between the if statement and the endif statement. A BREAK statement may be included inside an IF..ENDIF block to skip the remaining statements in that block. Of course, everything that happens or doesn't happen in an if condition depends on the condition itself. Every condition consists of a valid function name followed by an open parenthesis, followed by any parameters required by that function, and a close parenthesis. A simple example is below:
    if sex($n == M)
In this example, the sex function is called to determine whether $n (which is a variable representing the cause of a trigger) is male. If the mob who caused the trigger is male, the condition is true. Otherwise it is false. In the particular function above, the '==' symbols mean 'equal to'. Conditional statements may be negated using the "!" character as follows:
    if !sex($n == M)
In this case, the condition evaluates to false if the mob who caused the trigger is male, and true otherwise. Conditional statements may contain more than one function call if they are separated by the key words 'and' or 'or'. In the case of an 'and' key word, the condition evaluates to true if the functions on either side both evaluate to true, and it evaluates to false otherwise. In the case of the 'or' key word, the condition evaluates to true if either of the functions on either side evaluate to true, and false otherwise. Here are some examples of those in use:
    if sex($n == F) or race($n == Harpy)
    if sex($n == M) and isevil($n)
Lastly, conditional statements may group together their function calls using parenthesis. This can be used to ensure that certain sets of function calls are evaluated together, while others are not. For instance:
    if sex($n == M) or isevil($n) and race($n == Harpy)
    if ( sex($n == M) or isevil($n) ) and race($n == Harpy)
In these examples, if $n happens to refer to a Good Male Gnome, then the first statement would evaulate to true, while the second statement would evaluate to false. This is because the parenthesis force the sex and isevil checks to be evaulated first in the second example. Please see the section below on functions for a list of the conditional functions and their uses. ### switch, case, default, endswitch Usage:
    switch [variable]
    case [value]
    [commands]
    case [value]
    [commands]
    case [value]
    [commands]
    ...
    endswitch
The switch command is an alternative to the if/endif syntax above for comparing a single variable to many different variables. A switch statement is essentially a stand-in for this syntax:
    if VAR($i MYVAR == 'value1')
     [commands1]
    else
     if VAR($i MYVAR == 'value2')
     [commands2]
     else
     if VAR($i MYVAR == 'value3')
     [commands3]
     else
     [commands4]
     endif
     endif
    endif
Notice how, in the above example, we are comparing the same variable over and over again to different values, and doing something different depending on that value. This is what the switch command allows you to do without having to nest so many if-statements. Here would be the equivalent switch statement to the above:
    switch $%VAR($i MYVAR)%
    case 'value1'
    [commands1]
    case 'value2'
    [commands2]
    case 'value3'
    [commands3]
    default
    [commands4]
    endswitch
In the above switch statement, we declare the value we wish to check after the key word switch, which is the value of the variable $i MYVAR. In the ensueing case statements, we declare what we want the value of $i MYVAR to be equal to in order for the commands which follow the case statement to be executed. Each case statement defines its own value which $i MYVAR must be equal to in order for its following commands to be executed. The default statement is a special case is executed only if a value of $i MYVAR did not match any of the previous case values. Finally, the endswitch declares that no more cases will be given. Consider another example:
    switch $%RANDNUM(5)%
    case 1
     [commands1]
    case 2
     [commands2]
    case 3
     [commands3]
    case 4
     [commands4]
    case 5
     [commands5]
    endswitch
In this example, we are comparing a randomly generated number from 1-5 to each of the possible values in our case statements. Since we have covered all possible values of $%RANDNUM(5)%, we do not need to include a default case. ### for, next Usage:
    for $[digit] = [number] to [number]
    [commands]
    ...
    next
The for command is the simplest way to execute one or more other commands numerous times. It allows you to specify a numeric range for the scripting engine to count from and to, executing the commands after the for statement (and before the next statement) as many times as is required to complete the counting. The value of the current digit during counting is stored in one of the temporary variables $0, $1, $2, $3, ... $9. Here's an example:
    for $0 = 1 to 10
     mpecho I have done this $0 times!
    next
If you execute the above script, you will see the mpecho command repeated 10 times, which is one time for every digit between 1 and 10. Each time it executes the mpecho command, the value of the temporary variable $0 will be incremented. That's the basics, simple huh? For loops can be nested, so long as all of the outer for loops are using different temporary variables than the inner ones. Since there are 10 temporary variables, this gives you a limit of a nested depth of 10. The two number expressions can be literal numbers as shown above, or any expression which might evaluate to a number, such as $% syntax. Here's an example of what I mean:
    for $0 = 1 to '$%NUMMOBSROOM(*)%'
     mpecho '$%ROOMMOB($0)%' is here.
    next
You'll see that the NUMMOBSROOM() function is used here to return the number of mobs in the room, so we can count them. Each one we count, we can pass the $0 variable used in this loop to the ROOMMOB() function to get their name. Please see the section below on functions for a list of the functions and their uses. For Zero-based counting, there is the alternate syntax that replaces the 'to' key word with 'to<'. This will force the for-loop to count up to, but not including, the last number. For instance:
    for $0 = 0 to< 5
     mpecho $0
    next
The above would display 0 1 2 3 4, whereas, with a normal 'to' key word, it would have counted 0 1 2 3 4 5. ### <SCRIPT> This command denotes the beginning of a section of ECMA Javascript. Any lines of text following this command, and before the adjoining </SCRIPT> command will be assumed to be executable Javascript. These commands can only be embedded in standard event handlers as described above. Javascript is a wholly different language than the standard Scriptable/MOBPROG language described in this document. You should read the JavaScripting section of the CoffeeMud Programming Guide for more information, as well as the following web sites which discuss the usage and syntax of the Javascript language itself: http://www.mozilla.org/js/ and http://www.mozilla.org/rhino/. Even though the languages are very different, you will still be able to use all of the MOBPROG commands, functions, and even the special string versions of the functions described in the green table above. When using a command in JavaScript, make sure to always surround the parameters to the command with parenthesis, and make sure all parameters are separated by commas instead of spaces. For example, in MOBPROG, you might write:
            if IsPC ($n)
                MPEcho "The ground beneath $%InArea()% shakes!"
            endif
However, in Javascript, the exact same effect is generated by writing:
            if( ISPC("$n") )
            {
                MPECHO("The ground beneath " + INAREA$() + " shakes!");
            }
Notice that, while case is not sensitive for command or function names in MOBPROG, in JavaScript, all MOBPROG commands and functions are in uppercase only. Also notice that, when calling a string function from the green table above, the name of the function must end with a "$" character, to differentiate it from the boolean function calls (eg ISPC above). After you've read the above documentation, there are still a few small details to be aware of before getting started. One is that the Scriptable behavior will provide certain methods for accessing important event-related objects from inside your Javascript. These include the object functions source(), target(), host(), monster(), item1(), item2(), and message(). Another important detail is that Javascript variables defined will be lost from execution to execution, even of the same script. For this reason, additional methods String getVar(String host, String variableName), and void setVar(String host, String variableName, String value) have been provided to save the variables globally. The last important detail relates to semicolon characters. It is lucky that Javascript does not require them, because the Scriptable behavior will strip them out as part of its command parsing process. For this reason, if you absolutely must keep a semicolon ANYWHERE in your javascript, whether as part of a displayable string, or a line delimeter, it must be escaped: \; Here is an example:
    GREET_PROG 100
    mpecho Greetings $n! This command is mpecho, a mobprog command!

    <SCRIPT>
    var greetedBefore=getVar(source().Name(),"GREETEDBEFORE");
    source().tell("However, this greeting comes from Javascript!");
    if(greetedBefore == 'true')
     source().tell("We've met before\; we will meet again!!");
    else
     setVar(source().Name(),"GREETEDBEFORE","true");
    </SCRIPT>

    if var($n GREETEDBEFORE == true)
     mpecho The variable set in Javascript can be read here in mobprog land also!
    endif
    ~
### mpacctattoo Usage: mpacctattoo [target] (-)[tattoo name] If your mud even uses the common account system, this command grants or removes from the target's common player account a tattoo of the given name. This is useful for permanently flagging accounts in some way which can be checked and acted on elsewhere, for instance using the HASACCTATTOO function. The tattoo must begin with the character - to denote removal. See MPTATTOO for the similar command that applies to regular player mobs instead of their accounts. When adding new tattoos, you can prefix the name with a number to create a temporary tattoo that disappears in the given number of ticks. EXAMPLES: mpacctattoo $n smurfkiller mpacctattoo $n -smurfkiller mpacctattoo $n '50 smurfkiller' ### mpaffect Usage:
    mpaffect [spell name] [target] [parameters]
This command will put the target under the affect of the given spell, chant, prayer, song, skill, or CoffeeMud property. This is not the same as someone casting the given spell on the target. Instead, this command causes the target simply to come under the affect (as if the whole casting process were skipped). This means that not all spells will work with this command. Fireball, for instance, since it has no effect after casting, would do nothing under this command. The parameters given apply specifically to CoffeeMud properties, and are unnecessary for most spells, chants, etc. EXAMPLES:
    mpaffect Invisibility $n
    mpaffect Prop_PracticeDummy $n KILLABLE
### mpalarm Usage:
    mpalarm [ticks] [command]
This very simple command will wait the given number of ticks (4 second intervals) before executing the command given in the parameters. This command does NOT end execution. Any commands after mpalarm will be executed immediately. It is only the command given in the mpalarm parameters that will be executed after the delay. It is for this reason that the trigger type function_prog exists: namely to allow you to execute the group of instructions in the function_prog after some delay. EXAMPLES:
    mpalarm 10 say umm.. what was the question?
    mpalarm 30 mpecho You think you heard something.
    mpalarm 30 mpcallfunc myfunction
### mpargset Usage: mpargset [$var] [value or $var] This powerful but complex command is used to change one of the internal object variables, such as $n, $i, $t, $o, $p, $d, $0..$9, to point to a different object. This can then affect subsequent commands that refer to them. While $0..$9 may be set to any value, the standard $n..$d variables must be set to an object of the same kind. EXAMPLES:
    mpargset $o $p
    mpargset $0 $n
    mpargset $1 $0
    mpargset $0 'my value'
### mpasound Usage:
    mpasound [text string]
This command will echo the text string to all of the rooms adjacent to the one the mob is in, much like the echo when a mob yells. This can be useful for creating dramatic deaths from mobs, or for use with mobs such as a wandering minstrel or the like. EXAMPLES:
    mpasound You hear a scream from nearby!
    mpasound A delightful music fills the air from somewhere near here.
    mpasound The drunken hollering of $n can be heard nearby.
    mpasound The earth thunders as $n's corpse falls to the ground nearby.
SPECIAL NOTES: Keep in mind that mpasound does not echo to those in the room with the mob, only to rooms adjacent to it. So if you want people in the room to hear the mpasound too, you'll need to use an mpecho as well. ### mpat Usage:
    mpat [destination] [command]
Performs the desired command at a designated location. The destination can be either a room id, a key word from the room description, or the name of a mob. If you need to be need to find mobile mobs or items, you can include the mob or item name, followed by @ followed by a room id or area name. The command can be just about anything you want it to be. This command is very useful for doing slight of hand kind of tricks with mobs by performing actions away from the player, or doing things elsewhere in the zone for you. It has many potential uses. EXAMPLES:
    mpat MyArea#1232 unlock door
    mpat guardone poke guardone
    mpat 'a lovely pool' mpechoat $n You feel weakened from your escape.
    mpat Sewers#1252 drop all
SPECIAL NOTES: When using mpat, it is not a bad idea to give your mobs specific, unique keywords so they can be manipulated with no error. The command is usually essential for zones that have complicated quests, and can be used to trigger other mobs, unlock and open doors and chests away from the mob, and a variety of other things. ### mpbeacon Usage:
    mpbeacon [destination] [target]
This command changes the recall/start room of the target, which must be a player. EXAMPLES:
    mpbeacon MyArea#1232 all
    mpbeacon guardone $n
    mpbeacon 'a lovely pool' $n
### mpbehave Usage:
    mpbehave [behavior id] [target] [parameters]
This command will put the target under the affect of the given CoffeeMud behavior. The parameters given apply specifically to CoffeeMud behaviors. The Archon may use LIST BEHAVIORS, and AHELP [behavior name] for more information. EXAMPLES:
    mpbehave Aggressive $n
    mpbehave Mobile $n
    mbehave Scriptable $n ONCE_PROG;say hello;~;
### mpcallfunc Usage:
    mpcallfunc [function name] [parameters]
This command allows you to execute a group of other predefined commands without typing them all again. This is done by first defining a group of commands using the trigger function_prog. Once it is defined, the commands inside the function_prog may be executed by placing mpcallfunc followed by the function_prog's name parameter into another set of commands. This is useful for executing a set of commands that would normally have to be typed identically into your triggers over and over again. It is especially useful when used in conjunction with commands like mpalarm. The parameters passed into the mpcallfunc can be referenced using the $g and $G codes. EXAMPLES:
    mpcallfunc CompleteTask $n 'my house'
    mpcallfunc MyFunction
### mpcast Usage:
    mpcast [spell] [target]
This command causes the host mob to cast the given spell, chant, prayer, song, or use the given skill against the given target. Unlike using the mundane cast command, this scripting form does not require the mob to actually have the skill. Although there is still the 1-in-20 chance of failure of any skill, and the level of the host will affect the probability of success. EXAMPLES:
    mpcast fireball $r
    mpcast 'stinking cloud'
### mpcastext Usage: mpcastext [spell] [target] [arguments] This command causes the host mob to cast the given spell, chant, prayer, song, or use the given skill against the given target. Unlike using the mundane cast command, this scripting form does not require the mob to actually have the skill. And unlike MPCAST, it also allows you to spell out all of the arguments to the spell, for cases where the spell requires that. Remember that in targeted spells, the first argument is usually the targets name, so specifying that name again can be useful. Also, if you need to separate arguments, be sure to use double-quote "" instead of single quotes, since those strings will be parsed by the coffeemud engine instead of the mobprog engine. Although there is still the 1-in-20 chance of failure of any skill, and the level of the host will affect the probability of success. EXAMPLES: mpcast brainwash '$r' "$r" "I'm a pretty princess" ### mpchannel Usage: mpchannel [channel name] [message] mpchannel ![channel name] [message] This command causes the host mob to send a message to the given public channel, overriding any read-only restrictions which may be established. If the channel name is preceded by a !, then the message will be unattributed, a system message. EXAMPLES: mpchannel gossip Hello all! mpchannel !info Somewhere, a script is running. ### mpchoose Usage: mpchoose [pc name] [variable] [choices] [default choice] [prompt string] This command blocks the current coffeemud thread and waits for the player character denoted by the pc name variable to enter a one-letter choice from among the list of choices. This command will then store the chosen value in a variable of the given name under the pc name's context. If the pc name variable does not denote an online player, this command is skipped. The choices are a series of uppercase letters the player may choose from, like 'NSEW' or 'YN'. The default choice will be selected if the player simply hits ENTER instead of entering a choice. The choice is then stored in the variable of the given name as if the script command MPSETVAR [pc name] [variable] [result] was executed (see MPSETVAR). ** WARNING ** This command BLOCKS its current thread. It is therefore NOT appropriate to use this command off any trigger that operates off a tick thread, such as ONCE_PROG (unless executed during Character Creation), TIME_PROG, or similar triggers. It is OK to trigger this off an event trigger, such as GREET_PROG, EXECMSG_PROG and others, so long as you are certain the trigger leading to this prompt came from a command entered by a player-user (as opposed to a MOB generated event, which ultimate comes from tick threads). In short, BE CAREFUL! EXAMPLES:
    mpchoose $n MYDIRECTION NSEW N Which direction, enter N S E or W:
    mpechoat $n You chose $<$n MYDIRECTION>.
### mpclose Usage:
    mpclose [target]
This command closes a lid on a container, or the door on an exit. This command has no effect if there is no lid or door, or it is already closed. EXAMPLES:
    mpclose $xN
    mpclose the magic door
### mpconfirm Usage: mpconfirm [pc name] [variable] [default value] [prompt string] This command blocks the current coffeemud thread and waits for the player character denoted by the pc name variable to enter either yes or no, Y or N. This command will then store the chosen value in a variable of the given name under the pc name's context. If the pc name variable does not denote an online player, this command is skipped. The default choice will be selected if the player simply hits ENTER instead of entering a choice, and should be either the letter Y or the letter N (uppercase). The choice (also letter Y or N) is then stored in the variable of the given name as if the script command MPSETVAR [pc name] [variable] [result] was executed (see MPSETVAR). ** WARNING ** This command BLOCKS its current thread. It is therefore NOT appropriate to use this command off any trigger that operates off a tick thread, such as ONCE_PROG (unless executed during Character Creation), TIME_PROG, or similar triggers. It is OK to trigger this off an event trigger, such as GREET_PROG, EXECMSG_PROG and others, so long as you are certain the trigger leading to this prompt came from a command entered by a player-user (as opposed to a MOB generated event, which ultimate comes from tick threads). In short, BE CAREFUL! EXAMPLES:
    mpconfirm $n MYCHOICE N Are you a dork (Y/N):
    mpechoat $n You chose $<$n MYCHOICE>.
### mpdamage Usage:
    mpdamage [target] [min amount] [max amount]
    mpdamage [target] [min amount] [max amount] kill
This command does damage to a mob or item specified as the target. The amount of damage will be randomly between the min and max amounts. This command, by default, will never ever kill the target UNLESS the parameters are followed by the word kill as shown in the example below. Also, this command will treat any items that do not normally display a condition (like mundane items, wands, etc) as having 1 hit point. Other items (weapons, armor) will have a number of hit points equal to their condition. This command is useful not only for hurting mobs, but for scratching up their armor when acid falls from the ceiling or something similar. EXAMPLES:
    mpdamage $r 1 10 KILL
    mpdamage $n 10 50
### mpdisable Usage:
    mpdisable [target] [spell]
    mpdisable [target] [expertise]
This command causes the target mob to lose the spell, skill, prayer, expertise, etc specified. It does nothing if the mob does not have the skill. Skills can be granted using the mpenable command. EXAMPLES:
    mpdisable $n fireball
    mpdisable $n pass door
    mpdisable $n STEALTHY3
### mpecho Usage:
    mpecho [text string]
Quite simply, the mpecho command sends a message to the room of the mob. This message can be anything you like. It supports all of the character codes the mud uses, and can also use variables set by the mpsetvar command. This has a wide range of uses, from setting background noise to a mob, to allowing the mob to express itself safely as if speaking. The mpecho command does not set off speech_progs, although it does set off act_progs. EXAMPLES:
    mpecho $i says, ‘Hey how's it going?'
    mpecho A blast of strong wind rushes into the room suddenly!
    mpecho $i hisses, ‘So, $n, you've come to face me…'
    mpecho A dagger flashes into $i's hand, and $j snickers softly.
SPECIAL NOTES: Using mpecho $i says, ‘blah' is a safe way to have a mob talk. Anytime you want to have a mob say something, you should use this, unless you want it to trigger speech_progs. Also, remember that whatever is mpechoed is seen be everyone in the room exactly the same. So if you want a message that targets a specific person, see the mpechoat and mpechoaround commands. ### mpechoaround Usage:
    mpechoaround [target] [text string]
This command is similar to the mpecho command, but instead of echoing to everyone in the room, can be used to echo to everyone BUT the targeted person. Why would you do this? If used in conjunction with the mpechoat command, you can create text strings which look right to everyone involved. The way to make mpechoaround do this is to use the mpat command. EXAMPLES:
     mpechoaround $n You hear voices speaking all around you.
     mpechoaround $n $N cringes as a poisoned dart strikes $s chest!
     mpechoaround $n A pile of rocks rains down upon $n!
     mpechoaround $n A circle of light surrounds $n, and then $e vanishes.
### mpechoat Usage:
    mpechoat [target] [text string]
This command functions similar to the mpecho command, but can be used in such a way that only the targeted person or place sees the text string. This is useful for cutting down on spam from greet_prog mpechos, for example, as well as personalizing the text string for all parties involved in conjunction with the mpechoaround command. It also allows mobs to emulate the announce command. The target may be a local mob name, the word "world", the word "area", a room id, or an area name. If you need to be need to find mobile mobs or items, you can include the mob or item name, followed by @ followed by a room id or area name. EXAMPLES:
    mpechoat $n You hear voices speaking all around you.
    mpechoat $n You cringe as a poisoned dart strikes you in the chest!
    mpechoat $n A pile of rocks rains down upon you!
    mpechoat $n A circle of light surrounds you, and you are transported.
### mpenable Usage:
    mpenable [target mob] [ability] [integer proficiency] [parameters]
    mpenable [target mob] [expertise name]
    mpenable [target mob] [ability] [++integer proficiency] [parameters]
    mpenable [target mob] [ability] [--integer proficiency] [parameters]
This command grants a skill, spell, prayer, chant, song, expertise, or other ability to the target mob, or can be used to modify the proficiency of an existing skill. This acts like a forced 'GAIN' command, giving the target the skill permanently. The proficiency parameter should be between 0 and 100 when adding a new skill, or ++ followed by an adjustment integer, or -- followed by an adjustment integer. The final parameters are optional. Abilities can be removed with the mpdisable command. EXAMPLES:
    mpenable $n Fireball 100
    mpenable $n 'Summon Elemental' 0 EARTH
    mpenable $n 'Summon Elemental' ++20
    mpenable $n 'Summon Elemental' --5
    mpenable $n STEALTHY3
### mpendquest Usage:
    mpendquest [quest name]
    mpendquest [target mob]
When giving a quest name, this command forces a Quest which is in progress to shut itself down gracefully, removing its specific mobs, items, and properties from your map. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. When giving a target mob (or item for that matter) parameter, and if the running script was granted either directly or indirectly by a Quest, this command will remove any scripts associated with that quest (even the one running) from the target. When used in this way, the implementing quest is NOT stopped, shut down, or cleaned up gracefully. EXAMPLES:
    mpendquest smurfocide
    mpendquest $n
### mpexp Usage:
    mpexp [target] [exp amount]
    mpexp [target] [pct exp to next level%]
This command gives an amount of experience to the target, or a percentage of the experience they need to the next level. This is a useful command to use to award players for completing in zone quests, etc. that you have set up. If you want to award more experience than the capped amount, you can have the mob give several experience awards in a row. It is best when you award an experience award to give some sort of message to the player about why they are receiving the award. EXAMPLES:
    mpexp $n 500
    mpexp $n 10%
SPECIAL NOTES: Players can level off of these experience awards, just as if they had killed something. Be careful with this command. You don't want to give out awards for every little thing characters do, nor do you want to give large awards for menial tasks. You also will, of course, not want to make it so a mob can accidentally give the same award over and over endlessly, or something equally abusable. ### mpfaction Usage:
    mpfaction [target mob] [faction id] [new value, range, or +--change]
This command forces the victim to gain the given faction, and the given value within it. The target can be a character variable or a keyword of a mob. The faction id is the Faction to give to the player or mob. The new value, difference, or range may be a positive numeric value, a negative numeric value, it may be the name of one of the faction ranges, or it may be a difference expressed by +number or by --number (two - characters are required to distinguish a negative difference from a single negative numeric value). This command can be used to introduce a player to a faction they otherwise would not be able to gain, or it can be used in combination with the FACTION function to modify the value of a faction. EXAMPLES:
    mpfaction $n alignment.ini 1000
    mpfaction $n alignment.ini -50000
    mpfaction $i alignment.ini 'pure goodness'
    mpfaction $n alignment.ini +1
    mpfaction $n alignment.ini -1
### mpforce Usage:
    mpforce [target] [command]
This command forces the victim to do the designated command. The target can be a character variable or a keyword of a mob. This command has a lot of uses, but is mostly use in combat to do particularly nasty things, like force the player to heal the mob, etc. It can also be used to trigger other mobs by forcing them to perform a specific action which triggers an act_prog. EXAMPLES:
    mpforce $n flee
    mpforce $i sleep
    mpforce guardtwo poke self
    mpforce $n cast "heal serious" $i
SPECIAL NOTES: Remember that whatever you force something to do, it needs to be typed out exactly as if they were typing the command themselves. That means if you want a player, for example, to be forced to cast ‘heal serious' on your mob, you need to make sure you observe the double-quote rule for word groupings, as opposed to the single quote rule for mobprog commands. ### mpgoto Usage:
    mpgoto [destination]
Quite simply, this command will move the mob to the designated location. The destination can be a room id, keyword from a room description , or keyword of a mob. If you need to be need to find mobile mobs or items, you can include the mob or item name, followed by @ followed by a room id or area name. There is no message given to this command, so if you want there to be one, you need to include an mpecho in your mobprog. This command is a good way to move your mob around your zone should you need to. EXAMPLES:
    mpgoto Area#10076
    mpgoto guardthree
### mpgset Usage:
    mpgset [target] [variable] [value]
This powerful command lets you change all kinds of aspects of the target mob or item or whatever. Valid variable names for items include: "CLASS", "USES", "LEVEL", "ABILITY", "NAME", "DISPLAY", "DESCRIPTION", "SECRET", "PROPERWORN", "WORNAND", "BASEGOLD", "ISREADABLE", "ISDROPPABLE", "ISREMOVABLE", "MATERIAL", "AFFBEHAV", "DISPOSITION", "WEIGHT", "ARMOR", "DAMAGE", "ATTACK", "READABLETEXT", "MINRANGE", "MAXRANGE", "WEAPONTYPE", "WEAPONCLASS", "AMMOTYPE", "AMMOCAPACITY", "HASLOCK", "HASLID", "CAPACITY", "CONTAINTYPES", "NOURISHMENT", "RIDEBASIS", "MOBSHELD", "SENSES", "DISPOSITION", "LEVEL", "ABILITY", "REJUV", "WEIGHT", "HEIGHT", "ARMOR", "DAMAGE", "ATTACK" Additional variable names for items above the official ones include: "MATERIALNAME", "RESOURCENAME", "DISPOSITIONSTR", "SENSESSTR", and "LIQUIDREMAINING" Valid variable names for mobs include: "CLASS", "RACE", "LEVEL", "ABILITY", "NAME", "DISPLAY", "DESCRIPTION", "MONEY", "ALIGNMENT", "DISPOSITION", "SENSES", "ARMOR", "DAMAGE", "ATTACK", "SPEED", "AFFBEHAV", "ABLES", "INVENTORY", "TATTS", "EXPS", "RIDEBASIS", "MOBSHELD", "WHATISELL", "PREJUDICE", "BANKCHAIN", "COININT", "LOANINT", "IGNOREMASK", "POSTCHAIN", "POSTMIN", "POSTLBS", "POSTHOLD", "POSTNEW", "POSTHELD", "ITEMINT", "HITS", "MANA", "MOVE", "HUNGER", "THIRST", "FATIGUE", "STRENGTH", "INTELLIGENCE", "DEXTERITY", "CONSTITUTION", "CHARISMA", "WISDOM", "GENDER", "PARALYSIS SAVE", "SAVE VS FIRE", "SAVE VS COLD", "SAVE VS WATER", "SAVE VS GAS", "SAVE VS MIND", "GENERAL SAVE", "JUSTICE SAVE", "SAVE VS ACID", "SAVE VS ELECTRICITY", "SAVE VS POISON", "SAVE VS UNDEAD", "SAVE VS MAGIC", "SAVE VS DISEASE", "SAVE VS TRAPS", "MAX STRENGTH ADJ.", "MAX INTELLIGENCE ADJ.", "MAX DEXTERITY ADJ.", "MAX CONSTITUTION ADJ.", "MAX CHARISMA ADJ.", "MAX WISDOM ADJ.", "SENSES", "DISPOSITION", "LEVEL", "ABILITY", "REJUV", "WEIGHT", "HEIGHT", "ARMOR", "DAMAGE", "ATTACK", "HITS", "MANA", "MOVE", "HUNGER", "THIRST", "FATIGUE", "BASEHITS", "BASEMANA", "BASEMOVE", "BASEHUNGER", "BASETHIRST", "BASEFATIGUE" Additional variable names for mobs above the official ones include: "QUESTPOINTS", "FOLLOWERS", "TRAINS", "PRACTICES", "STINK", "CHARCLASS", "ALIGNMENT", "INCLINATION", "FACTIONID", "FACTIONAMT", "DEITY", "MATTRIB", "CLAN", "CLANROLE", "OBJATTRIB", "CLANROLE", "DISPOSITIONSTR", "SENSESSTR" Valid variable names for player mobs also include: "FRIENDS", "IGNORE", "TITLES", "ALIAS","LASTIP","LASTDATETIME", "CHANNELMASK", "COLORSTR", "PROMPT", "POOFIN", "POOFOUT", "TRANPOOFIN", "TRAINPOOFOUT", "ANNOUNCEMSG", "NOTES", "WRAP", "BIRTHDAY", "ACCTEXPIRATION", "INTRODUCTIONS" Whenever a value of ++ is given for any stat, it will increment that stats value by 1. A value of -- will decrement by one. EXAMPLES:
    mpgset $n CHARISMA 10
    mpgset $n NAME my name is mud
SPECIAL NOTES: Be very careful with this command when dealing with players. If used poorly it can cause bad things to happen to them, so make sure you have good checks to ensure they get affected correctly and fairly. ### mpheal Usage:
    mpheal [target] [min amount] [max amount]
This command heals a mob or item specified as the target. The amount of healing will be randomly between the min and max amounts. This command will ignore any items that do not normally display a condition (like mundane items, wands, etc). Other items (weapons, armor) will have a number of hit points equal to their condition. This command is useful not only for healing mobs, but for repairing their armor when acid falls from the ceiling or something similar. EXAMPLES:
    mpheal $r 1 10
    mpheal $n 10 50
### mphide Usage:
    mphide [target]
This command makes the target totally and completely undetectable by any means, magical or mundane. This is useful for making something "go away", but not really. mpunhide can restore such a hidden thing to sight. EXAMPLES:
    mphide $n
### mpjunk Usage:
    mpjunk [object]
This command destroys the object that the mob is referring to. The object must be in the mob's inventory or part of its equipment. You can also have a mob mpjunk all, which destroys everything on their person. You can also do things such as mpjunk all.sword or mpjunk all.bread, and can use the character variable $o. The command gives no message about its use, so it is a good way to secretly handle the junking of items. It is useful for getting rid of quest items given to the mob for give_progs, or if you have more complicated mobs where you must perform some sort of action in order to get its equipment, for example. EXAMPLES:
    mpjunk chalice
    mpjunk greatsword
    mpjunk all.arrow
    mpjunk all
SPECIAL NOTES: This command is very good for give_progs where you want to destroy the thing given so it can load again or not be used again by the same people. It is a good idea to give quest objects like that unique keywords so there is no mistaking what the mob is mpjunking. ### mpkill Usage:
    mpkill [victim]
This command basically causes the mob to attack the victim. The only real benefit of using this command is if your mob is low level or attacking someone under the affect of an awe spell. Other than that, there is no difference between this command and say, kill. EXAMPLES:
    mpkill $n
    mpkill guardfour
    mpkill $r
    mpkill giant
SPECIAL NOTES: Really, this command doesn't get used much. It was built for other MUD's which might have level requirements for kill, etc. You can use it, but it more or less works exactly the same as kill, murder, hit, etc. ### mplink Usage: mplink [direction] [target room] [exit class id] ([exit name]) This command allows a standard exit to be created from the room in which the scripted object is currently in, to another room in the same area, provided the script is only operating in its origin area. It will NOT overwrite/obliterate any existing exit in the same direction. EXAMPLE: mplink UP 'My Area#12322' OpenNameable my name ### mploadquestobj Usage:
    mploadquestobj [questname] [variable expression/name] [$var]
This command reads in a named object or string value for the given quest, and stores it in the internal temp variable object referred to by $var. $var may be $n, $o, $p, $i, $t, $d, $0..$9. Normally, this command only works when the object returned is of the same type as the $var, however, since the $0..$9 variables can hold any type of data, it is usually best to use one of those. Either way, this command can profoundly effect subsequent commands that use the $var specified. The quest name may be the name of a loaded quest, or * if this Scriptable object was loaded directly by a Quest script. The variable expressions may be one of these standard string values (non-objects): "CLASS", "NAME", "DURATION", "EXPIRATION", "WAIT", "MINPLAYERS", "PLAYERMASK", "RUNLEVEL", "DATE", "MUDDAY", "INTERVAL" The variable expressions may also be based on one of these quest objects: "LOADEDMOBS", "LOADEDITEMS", "AREA", "ROOM", "MOBGROUP", "ITEMGROUP", "ROOMGROUP", "ITEM", "ENVOBJ", "STUFF" or one of the following Mystery quest objects: "FACTION", "FACTIONGROUP", "AGENT", "AGENTGROUP", "ACTION", "ACTIONGROUP", "TARGET", "TARGETGROUP", "MOTIVE", "MOTIVEGROUP", "WHEREHAPPENED", "WHEREHAPPENEDGROUP", "WHEREAT", "WHEREATGROUP", "WHENHAPPENED", "WHENHAPPENEDGROUP", "WHENAT", "WHENATGROUP", "TOOL", "TOOLGROUP". Some of these objects are actually groups of objects, such as STUFF, LOADEDMOBS, LOADEDITEMS, and the ones that end with ..GROUP. The ones that end in group can be used as-is to load the group of objects into one of the $0..$9 vars. However, you can also tack on a "#" to the end of the name to return the number of items in the group instead of the group itself. After that, you can tack on a number like "#n" to return the nth item in the group. Lastly, tacking "#$" will return just the names of the items, and "#?" will return a random element in the group. See the examples for more information on some of these. EXAMPLES:
    mploadquestobj 'myquest' 'MOB' $t
    mploadquestobj 'myquest' 'TOOLGROUP#' $0
    for $1 = 1 to $0
     mploadquestobj 'myquest' 'TOOLGROUP#$1' $2
     mpecho $2 is now the $1th tool of $0 total in the myquest toolgroup.
    next
### mploadvar Usage:
    mploadvar [mob name] [variable name]
This command loads a variable stored in the database using the given parameters. The variable is then available to the VAR function, as well as the $< syntax. The mob name can for a variable can be a literal name string or a code like $n or $i. The variable name must be a literal string. EXAMPLES:
    mploadvar $n KILLS
    mploadvar guardfour RESCUES
### mplock Usage:
    mplock [target]
This command locks the target item or exit. If the target is already locked, or does not have a door or lock, nothing happens EXAMPLES:
    mplock $xN
    mplock east
    mplock chest
### mplog Usage: mplog error [module] [message] mplog info [module] [message] mplog debug [module] [message] This command outputs the given message to the coffeemud log file. For debug style messages to appear, the appropriate DBGMSGS entry in the coffeemud.ini file must be turned on. EXAMPLE: mplog info MyQuest $n has successfully completed my quest. ### mpm2i2m Usage:
    mpm2i2m [target]
This strange command turns a target mob into an item, and an item back into a mob. The target may be a mob, or an item which was created with mpm2i2m or the Cage skill. EXAMPLES:
    mpm2i2m $n
SPECIAL NOTES: If anyone comes up with a practical use for this command in an actual script, please let me know! ### mpmload Usage:
    mpmload [mob name]
    mpmload fromfile [cmare filename] [mob name]
    mpmload fromfile [cmare filename] any
    mpmload fromgenfile [random-gen xml filename] [mob name] [mob tag name] [id=value]...
This command loads the mob designated by name into the room. If you want the mob loaded somewhere besides the room the mpmloading mob is located, you'll need to use the mpat command. This command gives no message to the world, so if you want one, you'll use the mpecho command. This command is useful for loading mobs to assist the calling mob in combat, load in-zone quest mobs, etc. The mob of that name will be searched for throughout the map, so if you want to make sure the mob is available for this command, he should be carefully hidden. The fromfile syntax will allow you to load a mob from a cmare file created using the Archon EXPORT MOBS command. The fromgenfile syntax will allow you to generate a random mob from a random-generation formatted xml file, with the mob name followed by the mob tag to search for, with optional id=value definitions after the item tag. EXAMPLES:
    mpmload the nasty bat
    mpmload fromfile mymobs.cmare the nasty bat
    mpmload fromfile mymobs.cmare any
    mpmload fromgenfile /resources/randareas/example.xml bee forest_mobs level_range=10 aggrochance=1
SPECIAL NOTES: Remember that this newly loaded mob may not have interacted with the world just yet, so having your mob, for example, mpforce it to kill $n will not work, since the new mob has no idea who $n is. ### mpmloadshop Usage:
    mpmloadshop [mob name]
    mpmloadshop [mob name] PRICE=[cost to buy]
    mpmloadshop fromfile [cmare filename] [mob name]
    mpmloadshop fromfile [cmare filename] any
    mpmloadshop fromgenfile [random-gen xml filename] [mob name] [mob tag name] [id=value]...
This command loads the mob designated by name into the current shopkeeper inventory. If you want the mob loaded somewhere besides the scripted shopkeeper the mpmloading mob script is on, you'll need to use the mpat command. The mob of that name will be searched for throughout the map, so if you want to make sure the mob is available for this command, he should be carefully hidden. The fromfile syntax will allow you to load a mob from a cmare file created using the Archon EXPORT MOBS command. The fromgenfile syntax will allow you to generate a random mob from a random-generation formatted xml file, with the mob name followed by the mob tag to search for, with optional id=value definitions after the item tag. The PRICE= syntax may be used at the end of ANY of the syntaxes to set the price of the mob, otherwise a default price will be used. When this method completes, the value of $9 is automatically set to a string description of the final price. EXAMPLES:
    mpmloadshop the nasty bat PRICE=40
    mpmloadshop fromfile mymobs.cmare the nasty bat
    mpmloadshop fromfile mymobs.cmare any
    mpmloadshop fromgenfile /resources/randareas/example.xml bee forest_mobs level_range=10 aggrochance=1
### mpmoney Usage:
    mpmoney [target] +[amount]
    mpmoney [target] -[amount]
This command changes the amount of money owned by the target. This is a useful command to use to award players for completing in zone quests, etc. that you have set up. The amounts are always as expressed in base local currency. You can optionally specify the name of the currency as part of the amount. EXAMPLES:
    mpmoney $n +500 gold coins
    mpmoney $n -10 copper
### mpnotrigger Usage:
    mpnotrigger [trigger name] [time in miliseconds]
This command will prevent a scriptable event with the given trigger name on the same creature to trigger for the given amount of time. Where trigger name may be any of the above scriptable triggers, such as "greet_prog" or "level_prog" or any other. After the amount of time has passed, the trigger will be allowed. EXAMPLES:
    mpnotrigger greet_prog 10000
SPECIAL NOTES: This command is useful mainly to most easily prevent a greet_prog from firing for an entire group, or in cases where someone leaves and re-enters very quickly. ### mpoload Usage:
    mpoload [item name]
    mpoload fromfile [cmare filename] [item name]
    mpoload fromfile [cmare filename] any
    mpoload [item name] into [container name]
    mpoload fromgenfile [random-gen xml filename] [item name] [item tag name] [id=value]...
This command loads an item of the designated name into the inventory of the mob. If you want to load an item into a room, you must use the mpoloadroom command. This command gives no message to the world, so if you want one you'll have to use the mpecho command. This command is very useful for loading in-zone quest objects, mob pelts, portals, etc. It has many, many uses. The item of that name will be searched for throughout the map, so if you want to make sure the item is available for this command, it should be carefully hidden. The fromfile syntax will allow you to load an item from a cmare file created using the Archon EXPORT ITEMS command. The fromgenfile syntax will allow you to generate a random item from a random-generation formatted xml file, with the item name followed by the item tag to search for, with optional id=value definitions after the item tag. Finally, the into syntax will allow you to load the item into a pre-existing container, even if the container is in the room. EXAMPLES:
    mpoload the baseball bat
    mpoload fromfile myitems.cmare the baseball bat
    mpoload fromfile myitems.cmare any
    mpoload fromfile myitems.cmare any into wooden chest
    mpoload fromgenfile /resources/randareas/example.xml any dungeon_junk level_range=10 theme=random
SPECIAL NOTES: You can do a lot with this command. There is no max on items loaded in this way, so keep that in mind. ### mpoloadroom Usage:
    mpoloadroom [item name]
    mpoloadroom fromfile [cmare filename] [item name]
    mpoloadroom fromfile [cmare filename] any
    mpoloadroom [item name] into [container name]
    mpoloadroom fromgenfile [random-gen xml filename] [item name] [item tag name] [id=value]...
This command loads an item of the designated name into the same room as the mob. If you want to load an item into a mobs inventory, you must use the mpoload command. This command gives no message to the world, so if you want one you'll have to use the mpecho command. This command is very useful for loading in-zone quest objects, mob pelts, portals, etc. It has many, many uses. The item of that name will be searched for throughout the map, so if you want to make sure the item is available for this command, it should be carefully hidden. The fromfile syntax will allow you to load an item from a cmare file created using the Archon EXPORT ITEMS command. The fromgenfile syntax will allow you to generate a random item from a random-generation formatted xml file, with the item name followed by the item tag to search for, with optional id=value definitions after the item tag. Finally, the into syntax will allow you to load the item into a pre-existing container in the room. SPECIAL NOTES: You can do a lot with this command. There is no max on items loaded in this way, so keep that in mind. Using this command along with the mppurge command can create shifting portals and the like. ### mpoloadshop Usage:
    mpoloadshop [item name]
    mpoloadshop [item name] PRICE=[price of item]
    mpoloadshop fromfile [cmare filename] [item name]
    mpoloadshop fromfile [cmare filename] any
    mpoloadshop fromgenfile [random-gen xml filename] [item name] [item tag name] [id=value]...
This command loads an item of the designated name into the shopkeeper inventory of the scripted mob. If you want to load an item into another shops inventory, you must use the mpat command. The item of that name will be searched for throughout the map, so if you want to make sure the item is available for this command, it should be carefully hidden. The fromfile syntax will allow you to load an item from a cmare file created using the Archon EXPORT ITEMS command. The fromgenfile syntax will allow you to generate a random item from a random-generation formatted xml file, with the item name followed by the item tag to search for, with optional id=value definitions after the item tag. Finally, the price syntax may be added to the end of the any of the others to designate the price of the item, otherwise a default value will be used. When this method completes, the value of $9 is automatically set to a string description of the final price. ### mpopen Usage:
    mpopen [target]
This command opens a lid on a container, or the door on an exit. This command has no effect if there is no lid or door, or it is already open. EXAMPLES:
    mpopen $xN
    mpopen the magic door
### mpplayerclass Usage:
    mpplayerclass [target] [char class id] ([level] [char class id] [level] ...)
This command allows you to change the current character class of a player, to add new character classes to a player, and to modify specific class levels all with one command. The first parameter is the player or mobs code. The next parameter must be a valid character class id, such as Fighter or Necromancer. This will instantly set that class as the targets current class, adding it if necessary. This may be optionally followed by a level integer, which will change the class level of that current class. The level parm may then be followed by another character class id, which will change the players current class again, and may be followed again by a level integer to change the new current character class level, and so on. This command only works when the total class levels is equal to the players overall level. Otherwise, the engine will engage in an automatic correction. Keep this in mind when changing class levels. Any positive levels *added* to a class must first be taken away from some other class so that everything ends up equal. EXAMPLES:
    mpplayerclass $n Fighter
    mpplayerclass $n Thief 20
    mpplayerclass guardtwo Fighter 10
    mpplayerclass $n Thief 20 Fighter 10 Mage 5
### mppossess Usage: mppossess [player] [target mob] This command forces the target mob to be controlled by the given player. EXAMPLES: mppossess $s eagle ### mppracs Usage:
    mppracs [target] [amount]
    mppracs [target] ++[amount]
    mppracs [target] --[amount]
This command sets the mobs number of practices to the given number, or adjusts their existing practices by an amount upwards or downloads depending on syntax. A number alone will change their existing number of practices to the given number. The ++ syntax followed by a number will raise their amount by the given number. The -- syntax followed by a number will lower their amount by the given number. This is a useful command to use to award players for completing in zone quests, etc. that you have set up. It is best when you reward a player using this command that you alsogive some sort of message to the player about why they are receiving the award. EXAMPLES:
    mppracs $n 0
    mppracs $n ++3
    mppracs $n --1
SPECIAL NOTES: Be careful with this command. You don't want to give out awards for every little thing characters do, nor do you want to give large awards for menial tasks. You also will, of course, not want to make it so a mob can accidentally give the same award over and over endlessly, or something equally abusable. ### mpprompt Usage: mpprompt [pc name] [variable] [prompt string] This command blocks the current coffeemud thread and waits for the player character denoted by the pc name variable to enter either a string value. This command will then store the value in a variable of the given name under the pc name's context. If the pc name variable does not denote an online player, this command is skipped. ** WARNING ** This command BLOCKS its current thread. It is therefore NOT appropriate to use this command off any trigger that operates off a tick thread, such as ONCE_PROG (unless executed during Character Creation), TIME_PROG, or similar triggers. It is OK to trigger this off an event trigger, such as GREET_PROG, EXECMSG_PROG and others, so long as you are certain the trigger leading to this prompt came from a command entered by a player-user (as opposed to a MOB generated event, which ultimate comes from tick threads). In short, BE CAREFUL! EXAMPLES:
    mpprompt $n MYVALUE 'Why are you smiling?'
    mpechoat $n You said $<$n MYVALUE>.
### mppurge Usage:
    mppurge [argument]
    mppurge room [argument]
    mppurge my [argument]
This command destroys the argument item or mob. This argument can be a mob keyword, item keyword, character variable, or the keyword self. You can also make this command more safe by preceding an item purge with the keyword room to specify only items on the ground, or the keyword my to specify only items in the scripted mobs inventory. If you are going to have a mob mppurge itself, it must be the last command the mob does, or bad things will happen. Also, never ever mppurge oneself as part of a death_prog. This is a very useful command. With it you can destroy charmed mobs, switch portals and the like, and clear out mobs and objects you may have loaded. EXAMPLES:
    mppurge portalone
    mppurge guardthree
    mppurge my sword
    mppurge room portal
    mppurge $n
    mppurge self
SPECIAL NOTES: It is a good idea to have unique keywords for mobs and items you are sure you are going to be mppurging. That way there is no mistake what you are trying to mppurge. Also, you should avoid mppurging players, as it basically causes them to be ejected from the game. Use this command for mobs that set up special quests and then go away, so each zone reset you'll have a fresh zone for adventurers to pillage. ### mpput Usage:
    mpput [item code] [container code]/NONE
    mpput [mob code] [rideable code]/NONE
This command can be used to put an item into a container, remove an item from a container (using the NONE container), mount a wagon to a horse, or mount a player on a horse. EXAMPLES:
    mpput $i 'the horse'
    mpput $o 'the sack'
### mpqset Usage:
    mpqset [questname] [variable] [value]
This command is used to set one of the internal quest variables. These variables can be one of the standard Quest settings, such as: "CLASS", "NAME", "DURATION", "EXPIRATION","WAIT", "MINPLAYERS", "REMAINING", "PLAYERMASK", "RUNLEVEL", "DATE", "MUDDAY", or "INTERVAL". More commonly though, they are user-defined variables which are only available for the duration of the quest, and reset each time the quest is started. Questname may be the name of a quest, or it may be * if this Scriptable object was assigned by a Quest. These variables can be read with the QVAR function. MPQSET also supports a special Scriptable-only variable called QUESTOBJ. Set this variable to an object created with mpmload fromfile or mpoload fromfile to ensure that the quest will clean up the item or mob when the quest ends. You can also set a Scriptable-only variable called STATISTICS to either ACCEPTED, SUCCESS, or FAILED to help CoffeeMud keep tabs on your quests. EXAMPLES:
    mpqset 'myquest' 'myspecialquestvariable' $n
### mpquestpoints Usage:
    mpquestpoints [target] [amount]
    mpquestpoints [target] ++[amount]
    mpquestpoints [target] --[amount]
This command sets the mobs number of quest points to the given number, or adjusts their existing quest points by an amount upwards or downloads depending on syntax. A number alone will change their existing number of quest points to the given number. The ++ syntax followed by a number will raise their amount by the given number. The -- syntax followed by a number will lower their amount by the given number. This is a useful command to use to award players for completing in zone quests, etc. that you have set up. It is best when you reward a player using this command that you alsogive some sort of message to the player about why they are receiving the award. EXAMPLES:
    mpquestpoints $n 0
    mpquestpoints $n ++3
    mpquestpoints $n --1
SPECIAL NOTES: Be careful with this command. You don't want to give out awards for every little thing characters do, nor do you want to give large awards for menial tasks. You also will, of course, not want to make it so a mob can accidentally give the same award over and over endlessly, or something equally abusable. ### mpquestwin Usage:
    mpquestwin [mob name] [quest name]
This command declares the given mob as the winner of the quest of the given name. This makes the mob available to the QUESTWINNER function. This command is absolutely necessary to ensuring that players do not repeatedly win the same quests over and over again. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. EXAMPLES:
    mpquestwin $n smurfocide
### mprejuv Usage:
    mprejuv area
    mprejuv room
    mprejuv [area name]
    mprejuv [room id]
    mprejuv area items
    mprejuv room items
    mprejuv [area name] items
    mprejuv [room id] items
    mprejuv area mobs
    mprejuv room mobs
    mprejuv [area name] mobs
    mprejuv [room id]
This command allows you to force the system to restore dead mobs, missing rejuvenating items, or both from an area or a room. The keywords area and room will refer to the scripted objects current area and room. Otherwise, the name of the area, or the full roomID can be specified. Mobs and items will only be restored if their REJUV property has been set properly. Therefore, this commands primary purpose is to speed up something which will happen eventually anyway. EXAMPLES:
    mprejuv area
SPECIAL NOTES: This is a quick and useful command when scripting special events that require a room or areas default mobs or items to be present. ### mpreset Usage:
    mpreset area
    mpreset room
    mpreset [area name]
    mpreset [room id]
    mpreset [mob code]
    mpreset [item code]
This command allows you to force the system to reload an area or a room from the database. The keywords area and room will refer to the scripted objects current area and room. Otherwise, the name of the area, or the full roomID can be specified. It also allows you to reset the durability of an item and remove it from any container. For mobs, this will reset the targets hit points, mana, and movement back to maximum, assuming they are alive and targetable. EXAMPLES:
    mpreset area
SPECIAL NOTES: Be very careful with this command when dealing with players in the area. It will end their combat, clean up items in the rooms they are in, and otherwise freeze them up while the reset process completes. This process can be time consuming for large areas, so take that into consideration. ### mprpexp Usage:
    mprpexp [target] [exp amount]
    mprpexp [target] [pct exp to next level%]
This command gives an amount of Role Play experience to the target, or a percentage of the experience they need to the next level. This is a useful command to use to award players for doing special in character things. If you want to award more experience than the capped amount, you can have the mob give several experience awards in a row. It is best when you award an experience award to give some sort of message to the player about why they are receiving the award. EXAMPLES:
    mprpexp $n 500
    mprpexp $n 10%
SPECIAL NOTES: Players can level off of these experience awards. Be careful with this command. You don't want to give out awards for every little thing characters do. ### mpsavevar Usage:
    mpsavevar [mob name] [variable name]
This command saves a variable to the database using the given parameters. This will ensure that the variable, if reloaded later using mploadvar, survives reboots, resets, and other catastrophes. The variable specified must be one created by the MPSETVAR command. The mob name can for a variable can be a literal name string or a code like $n or $i. The mob name can also be *, which will save the value of every existing variable of the given variable name. Likewise, the variable name can also be *, which will save the value of every existing variable for the given mob. EXAMPLES:
    mpsavevar $n KILLS
    mpsavevar guardfour RESCUES
### mpscript Usage:
    mpscript [target] [optional flags] [scriptable script]
This command appends a new Scriptable script to the given target. Unlike using mpbehav to add the Scriptable behavior, this command can be used to add more than one unrelated script to the target, and gives some finer controls making this command more suitable for building personal quests. The target can for a variable can be a literal name string or a code like $n or $i, $o, $p, $0, etc. The optional flags include the following: SAVABLE, to make the script a permanent database savable feature of the target (default is not savable), GLOBAL, to force the script to use the global script variables scope, INDIVIDUAL to force the script to use its very own local variable scope (which will then case those variables to be saved along with the target), and EXECUTE to force the script to execute its ONCE_PROG, and then be immediately removed from the target. The scriptable script is exactly like the parameters found for the behavior Scriptable. See AHELP SCRIPTABLE for more information on how to specify a script. EXAMPLES:
    mpscript $n SAVABLE LOAD=progs/myquestscript.quest
    mpscript guardfour GLOBAL GREET_PROG 100\;mpecho hi!\;~\;
### mpset Usage:
    mpset [target] [variable] [value]
This powerful command lets you change all kinds of aspects of the target mob or item or whatever. This command differentiates between generic and standard items and mobs. Standard items and mobs do not have as many changeable properties as generic items do. For the maximum range of available variables, use mpgset. Valid variable names are identical to those listed under mpgset. Please see that command above for a list of valid variables. Whenever a value of ++ is given for any stat, it will increment that stats value by 1. A value of -- will decrement by one. EXAMPLES:
    mpset $n CHARISMA 10
    mpset $n NAME my name is mud
SPECIAL NOTES: Be very careful with this command when dealing with players. If used poorly it can cause bad things to happen to them, so make sure you have good checks to ensure they get affected correctly and fairly. ### mpsetclan Usage:
    mpsetclan [target] [clan] [role]
This command allows you to add or remove the target to/from the given clan. A role of -1 will remove the target from the clan. A valid clan role will add them. EXAMPLES:
    mpsetclan $i 'Groovy Clan' 0

    mpsetclan $i 'Groovy Clan' Boss
### mpsetclandata Usage:
    mpsetclandata [clan] [variable] [value]
This powerful command lets you change several aspects of the given clan based on the given variable. The clan code may be either a mob code to denote that mobs clan, or a clan name. Valid variables for setting are: ACCEPTANCE, DONATEROOM, EXP, GOVT, MORGUE, POLITICS, PREMISE, RECALL, STATUS, TAXES, TROPHIES, TYPE, AREAS, MEMBERLIST, TOPMEMBER, CLANLEVEL, CATEGORY, RIVALROUS,MINMEMBERS, CLANCHARCLASS, NAME EXAMPLES:
    mpsetclandata 'Groovy Clan' EXP 0
    mpecho Groovy Clans experience is now gone!
    mpset $n PREMISE my premise is new.
    mpecho Whoever $n is, their clan now has a new premise!
SPECIAL NOTES: Be very careful with this command, to ensure no damage is done to clan records. ### mpsetinternal Usage:
    mpsetinternal [variable] [value]
This command is used to set one of the internal scripting engine variables. The variables included, and their meaning, is as follows: SCOPE: Manually changes the scope of variable resolution. * is global/default. NODELAY: Whether a 1 tick delay is seen before some triggers fire. Values are true or false. ACTIVETRIGGERS: Whether a mob will always trigger, despite being unhealthy or a follower. Values are true or false. DEFAULTQUEST: Changes which quest this script is registerd with. Affects only the Quest related MP commands. SAVABLE: Determines if this script will be saved as a permanent part of the host. Values are true or false. PASSIVE: Whether this script keeps triggering RAND_PROG or other tick-based triggers even when the area is passive. Values are true or false. ### mpsetvar Usage:
    mpsetvar [mob name] [variable name] [value]
    mpsetvar [mob name] [variable name] ++
    mpsetvar [mob name] [variable name] --
    mpsetvar [mob name] [variable name] +[number]
    mpsetvar [mob name] [variable name] -[number]
    mpsetvar [mob name] [variable name] *[number]
    mpsetvar [mob name] [variable name] /[number]
This command creates a variable for a mob or player and stores a value in it. You can mpsetvar any name that you choose to, and the value can be a specific text string, an integer, or an expanded character variable. The value can even be mathematical expression as shown above. The starting value of the variable will be affected by the expression given instead of merely set to it. The mob name can be a literal name string or a code like $n or $i. The mob name can also be *, which will change the value of every existing variable of the given variable name. Likewise, the variable name can also be *, which will change the value of every existing variable for the given mob. A value is normally required, but not giving a value removes that variable from memory, so if you want a variable to remain in memory so as to be accessible to * syntax, you will need to include some value. For quests, this command has special considerations. First, it is impacted by the variable Scope that was assigned to the script. The scope can be global (the default), individual, which means the variables are inaccessible outside of each instance of the script, or a named scope, where all scripts with the same scope name can access each others variables. There is also the special case that player scripts, even those with individual scopes, can have their variables that were assigned to the players name accessed from outside scripts, so long as they share the same quest origin. This last is useful when special player progress variables are stored in the players script, and need to be accessed by global scripts. EXAMPLES:
    mpsetvar $i bugcount 1
    mpsetvar $i bugcount ++
    mpsetvar 'frog boy' 'my victim' The guard
    mpsetvar $n 'my victim' var-actor
    mpsetvar $i bugcount $<$n bugcount>
    mpsetvar * bugcount
    mpsetvar $i * null
SPECIAL NOTES: Variables rock. You can do almost anything you ever wanted to do once you get the hang of them. ### mpslay Usage:
    mslay [victim]
This command kills the victim dead. EXAMPLES:
    mpslay $n
    mpslay ogre
### mpspeak Usage:
    mpspeak [target] [language name]
This command will force the target mob to speak the given language, even if they don't know it. Simple. EXAMPLES:
    mpspeak $n Elvish
### mpstartquest Usage:
    mpstartquest [quest name]
This command causes the given Quest name to start running. If the Quest is already running, nothing will happen. This command is useful for having scripted mobs start quests for you. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. EXAMPLES:
    mpstartquest smurfocide
### mpstop Usage:
    mpstop [target]
This command forces the target to stop fighting. If the target happens to be in the middle of working with a common skill, it will stop that too. You may specify a target of ALL to make everything in the room stop. EXAMPLES:
    mpstop $n
    mpstop ogre
### mptattoo Usage:
    mptattoo [target] (-)[tattoo name]
This command grants or removes from the target a tattoo of the given name. This is useful for permanently flagging players in some way which can be checked and acted on elsewhere, for instance using the HASTATTOO function. The tattoo must begin with the character - to denote removal. When adding new tattoos, you can prefix the name with a number to create a temporary tattoo that disappears in the given number of ticks. EXAMPLES:
    mptattoo $n smurfkiller
    mptattoo $n -smurfkiller
    mptattoo $n '50 smurfkiller'
### mptitle Usage:
    mptitle [target] (-)[title string]
This command grants or removes from the target a title given. Title strings are are name replacements for player mobs in which any * character in the string is replaced with the players name. The player uses the TITLE command to select which of any granted titles they may use. This command is completely case sensitive. EXAMPLES:
    mptitle $n '*, slayer of smurfs'
    mptitle $n '-*, slayer of smurfs'
### mptrackto Usage:
    mptrackto [mob name]
    mptrackto [room id]
    mptrackto [area name]
This command causes the mob to begin walking towards the given target. If there are doors in his way, he will open them. If they are locked, he will unlock them. If there are no-mob areas in the way, he will walk through them. Nothing short of combat will stop him from getting to the target room. This command is identical to the mpwalkto command, except that this command will allow paths through the air or water if those paths are shorter. This command should never be chosen over mpwalkto, unless the tracking mob is a fish or a bird. EXAMPLES:
    mptrackto the master guildsmith
    mptrackto myArea#123
    mptrackro Smurf Villiage
### mptrains Usage:
    mptrains [target] [amount]
    mptrains [target] ++[amount]
    mptrains [target] --[amount]
This command sets the mobs number of training sessions to the given number, or adjusts their existing training sessions by an amount upwards or downloads depending on syntax. A number alone will change their existing number of training sessions to the given number. The ++ syntax followed by a number will raise their amount by the given number. The -- syntax followed by a number will lower their amount by the given number. This is a useful command to use to award players for completing in zone quests, etc. that you have set up. It is best when you reward a player using this command that you alsogive some sort of message to the player about why they are receiving the award. EXAMPLES:
    mptrains $n 0
    mptrains $n ++3
    mptrains $n --1
SPECIAL NOTES: Be careful with this command. You don't want to give out awards for every little thing characters do, nor do you want to give large awards for menial tasks. You also will, of course, not want to make it so a mob can accidentally give the same award over and over endlessly, or something equally abusable. ### mptransfer Usage:
    mptransfer [victim] [destination]
This command sends the victim to a designated destination. The victim can be either a mob keyword or a character variable. The destination can be a room id, room name or description, a mob keyword, or a character variable. If you need to be need to find mobile mobs or items, you can include the mob or item name, followed by @ followed by a room id or area name. If there is no destination given, the mob transfers the victim to the same room that it is in. There is no message given to this command, so if you want there to be one, you need to include an mpecho in your mobprog. This command is a good way to move players around your zone or into other zones. EXAMPLES:
     mptransfer $n myarea#10049
     mptransfer $n
     mptransfer guardeight myarea#1252
     mptransfer guardten $n
SPECIAL NOTES: You need to be careful with this command. First of all, you should never transfer a character variable that is a mob. Why not? Because you may actually end up transferring a different mob entirely with a keyword that is the same. You can mptransfer mobs if they have unique keywords. Also, be sure to be careful about mptransfering mobs to players. If a player recalls or dies, you will end up transferring a mob into town. ### mpunaffect Usage:
    mpunaffect [target] [affect id]
This command dispels the given affect from the target. If no affect name is given, or ALL is given, then all non-permanent affects will be removed. Any affects listed by name will always be removed, even if they are permanent. You should check out the list of skills, spells, and properties for a list of valid ids to give. EXAMPLES:
    mpunaffect $n
    mpunaffect $n Spell_Sleep
    mpunaffect $n Skill_Track
### mpunbehave Usage:
    mpunbehave [behavior id] [target]
This command removes the given behavior from the target. You should check out the list behaviors by entering LIST BEHAVIORS on the command line. EXAMPLES:
    mpunbehave Mobile $n
### mpunhide Usage:
    mpunhide [target]
This command reverses the affects of mphide, making the target (possibly) visible again. EXAMPLES:
    mpunhide $n
### mpunlink Usage: mpunlink [direction] This command allows an exit created using the MPLINK command to be removed and destroyed. EXAMPLE: mpunlink UP ### mpunloadscript Usage: mpunloadscript [file name] This command accepts only the name of a Scriptable script file that has already been loaded from the filesystem by a Scriptable behavior and parsed for processing. The parameter MUST resolve to a valid file in your CoffeeMud file system, and is usually the result of putting a LOAD=<filename> parameter on a Scriptable behavior. Remember that, since this is a Scriptable filename, that /resources/ is implied. The purpose of this command is to allow the script writer to de-cache his scripts automatically for cases where scripts are being dynamically built, so that they can be re-read and re-processed by the CoffeeMud Scripting Engine. EXAMPLES: mpunloadscript progs/myscript.script ### mpunlock Usage:
    mpunlock [target]
This command unlocks the given container or exit. This command has no effect if the target does not have a lid, does not have a lock, or is already unlocked or open. No key is required. EXAMPLES:
    mpunlock $xN
    mpunlock chest
### mpwhile Usage:
    mpwhile ([condition]) [command]
This command repeatedly executes the given command, so long as the given condition remains true. This is the only mechanism for looping in Scripts, so it should be used carefully, although a safeguard is in place to prevent an mpwhile loop from ever running longer than 4 seconds. The [condition] must be enclosed in parenthesis, and is subject to the same rules listed under the IF command above. Since only one command parameter is allowed, it is necessary for you to use MPCALLFUNC and FUNCTION_PROG in order to execute more than one command during a loop cycle. EXAMPLES:
    mpwhile (VAR($n bittlock < 1)) MPCALLFUNC myprogram $<$n bittlock>
### mpwalkto Usage:
    mpwalkto [mob name]
    mpwalkto [room id]
    mpwalkto [area name]
This command causes the mob to begin walking towards the given target. If there are doors in his way, he will open them. If they are locked, he will unlock them. If there are no-mob areas in the way, he will walk through them. Nothing short of combat will stop him from getting to the target room. This command is identical to the mptrackto command, except that this command only finds land-surface paths, ignoring possible paths through the air or over water. This command should always be used instead of mptrackto, unless the tracking mob is a fish or a bird. EXAMPLES:
    mpwalkto the master guildsmith
    mpwalkto myArea#123
    mpwalkto Smurf Villiage
### return Usage:
    return ([string])
This command causes the current script block to immediately cease executing. If this statement is used inside of a FUNCTION_PROG triggered script, it will return a value from the function. This value can be accessed only if the FUNCTION_PROG was called using the CALLFUNC scripting function (see below). EXAMPLES:
    return
    return $<$n myvariable>
## Scripting Functions Functions are what make your IF checks work. They can be fairly simple, and they can be massively complicated. There are quite a few of them, but knowing how and where to use them is rewarding if you want to have truly unique and intelligent scripts. ### Logical Operators These operators are found in many of the functions below. Here are their meanings:
    == This operator means ‘equal to'
    != This operator means ‘not equal to'
    > This operator means ‘greater than'
    < This operator means ‘less than'
    >= This operator means ‘equal or greater than'
    <= This operator means ‘equal or less than'
### affected Usage:
    affected(character spellid)
This checks whether the character is under the effects of the given spell. The spellid must be the full Java name of the spell, skill, prayer, property, chant, or whatever. EXAMPLE:
    if affected($n, Spell_Sleep)
     mpecho The actor triggering me is asleep.
    else
     mpecho The actor triggering me is not under the effects of the sleep spell.
    endif
### baseclass Usage:
    baseclass(character == baseclassname)
This checks whether the character is a class which is part of the given baseclass. Where '==' may be another logical operator from above. Valid baseclasses include Archon, Artisan, Fighter, Druid, Mage, Cleric, Thief, or Bard. EXAMPLE:
    if baseclass($n == Archon)
     mpecho The actor triggering me is an Archon.
    else
     mpecho The actor triggering me is not an Archon.
    endif
### canhear Usage: canhear(chaaracter soundmaker) This checks whether the character can hear sounds made by the second argument. EXAMPLE: if canhear($n 'the boombox') mpecho The actor triggering me can hear the boombox else mpecho The actor triggering me can not hear the boombox endif ### cansee Usage: cansee(chaaracter object) This checks whether the character can see the second argument. EXAMPLE: if cansee($n $1) mpecho The actor triggering me can see me else mpecho The actor triggering me can not see me endif ### callfunc Usage:
    callfunc(myfunctionname parm1 parm2...parmn)
This function, similar to the MPCALLFUNC statement above, will cause the script block with the trigger type FUNCTION_PROG and the given name to execute. The parameters passed into the callfunc can be referenced using the $g and $G codes. See the MPCALLFUNC statement above for more information on creating functions. The callfunc function returns true ONLY if the FUNCTION_PROG includes a RETURN statement that includes a non-empty string parameter which is not CANCEL. EXAMPLE:
    function_prog myfunc
    return $g
    ~

    once_prog
    if callfunc(myfunc ASTRING)
     mpecho This callfunc function will always return true.
     mpecho This is because myfunc just returns the parameter it is given.
     mpecho And this callfunc is passing in a non-empty string as a parameter.
    endif

    if !callfunc(myfunc)
     mpecho This callfunc function will always return false, since my parameters are empty.
    endif
    ~
### clan Usage:
    clan(character == clanname)
This checks the name of the prominent rivalrous clan of the character variable. Where '==' may be ==, != to check the prominent clan, or "in" or "notin" to check membership in a clan. EXAMPLE:
    if clan($n in 'The Unholy Goobers')
     mpecho The actor triggering me appears to be an Unholy Goober.
    else
     mpecho The actor triggering me appears not to be a Goober.
    endif
### clandata Usage:
    clandata(clan variable == value)
This checks the value of a piece of datum about the given clan. The clan parameter may be either a mob to denote the mobs clan, or a clan name. Where variable should be one of the following ACCEPTANCE, DETAIL, DONATEROOM, EXP, GOVT, MORGUE, POLITICS, PREMISE, RECALL, SIZE, STATUS, TAXES, TROPHIES, TYPE, AREAS, MEMBERLIST, TOPMEMBER, CLANLEVEL, CATEGORY, RIVALROUS,MINMEMBERS, CLANCHARCLASS, NAME or TOPMEMBER. Where '==' may be another logical operator from above. The value may be any numeric, string, or literal. EXAMPLE:
    if clandata($n SIZE <= 1)
     mpecho The actor triggering me appears to be the only solitary member of the clan.
    else
     mpecho The actor triggering me appears to be part of a clan larger than 1 member.
    endif
### clanrank Usage:
    clanrank(character == integer)
This checks the rank of the character in their prominent rivalrous clan. Where '==' may be another logical operator from above. Valid values include: APPLICANT=0, MEMBER=1, STAFF=2, ENCHANTER=3, TREASURER=4, LEADER=5, BOSS=6 EXAMPLE:
    if clanrank($n == 0)
     mpecho The actor triggering me appears to be an APPLICANT.
    else
     mpecho The actor triggering me appears not to be an APPLICANT.
    endif
### clanqualifies Usage:
    clanqualifies(character clanname)
This checks the given character to see if they qualify to be a new member of the given clan. EXAMPLE:
    if clanqualifies($n 'MyClan')
     mpecho The actor triggering me appears qualify.
    else
     mpecho The actor triggering me appears not to qualify.
    endif
### class Usage:
    class(character == classname)
This checks the class of the character variable. For players, this is their class, or in the case of a multi-classed character, the class they multied into. For disguised characters, this is the class they appear to be. Where '==' may be another logical operator from above. EXAMPLE:
    if class($n == Gaian)
     mpecho The actor triggering me appears to be a Gaian.
    else
     mpecho The actor triggering me appears not to be a Gaian.
    endif
### currency Usage:
     currency(character == currencyname)
This compares the player character or coin item native currency to the string. The '==' may also be '!='. EXAMPLE:
    if currency($n == 'COPPER')
     mpecho You are using the bits currency.
    else
     mpecho You must be using something else.
    endif
### datetime Usage: datetime(type == value) This evaluates the time, day, month, or year. Use one of those words as the type (time, day, month, or year). Where '==' may be any other logical operator from above. EXAMPLE:
    if datetime(time < 4)
     mpecho It is before the 4th hour.
    else
     mpecho It is the 4th hour or later.
    endif
### deity Usage:
    deity(character == deityname)
This checks the name of the deity of the character variable. Where '==' may be another logical operator from above. EXAMPLE:
    if deity($n == 'Gothon')
     mpecho The actor triggering me appears to worship an Unholy Goober.
    else
     mpecho The actor triggering me appears not to worship Gothon.
    endif
### eval Usage:
    eval(expression == expression)
This powerful function compares the first expression to the second expression. Expressions may be codes, literal strings, or literal numbers. This function also allows you to compare variables. Where '==' may be any other logical operator from above. This is an extremely powerful function that can, if used properly, take care of all of the evaluation needs which other functions do not provide. Examine carefully the section on codes above to see all the different things you can evaluate. EXAMPLE:
    if eval($n == an orc) or eval('$<$i VAR>' != 7)
     mpecho Evaluates to true.
    else
     mpecho Evaluates to false.
    endif
### exp Usage: exp(character > amount) This evaluates the total amount of experience that the character variable has earned. Where '==' may be any other logical operator from above. EXAMPLE: if exp($n < 10000) mpecho The actor has less than 10000 experience else mpecho The actor has 10000 experience endif ### expertise Usage:
    expertise(character abilityid expertiseflag == number)
This function compares the expertise for the given character, ability id, and expertise flag to the number given. The '==' may also be any of the logical operators from above. A character is list $n, $i, the name of a monster, etc. The ability id can be obtained by doing LIST ABILITIES on the command line, and is the internal name of a skill. The expertiseflag is one of: X1, X2, X3, X4, X5, LEVEL, TIME, MAXRANGE, LOWCOST, XPCOST, LOWFREECOST. EXAMPLES:
    if expertise($i Thief_Trap LEVEL > 3)
     mpecho I have a power level in trapping type expertises greater than 3
    else
     mpecho I have a power level in trapping type expertises below or equal to 3.
    endif
### explored Usage:
    explored(character areaname == number)
    explored(character world == number)
This function compares the percentage of the given area or of the world which the given mob has explored. The number should always be between 0 and 100, reflecting what percentage of the area or world that the character has explored. Where '==' may be any other logical operator from above. Remember that percentage exploration is only stored for players, not for NPC mobs. EXAMPLES:
    if explored($n $a > 10)
     mpecho You have explored more than 10% of this area.
    else
     mpecho You have explored less than 10% of this area.
    endif

    if explored($n world > 10)
     mpecho You have explored more than 10% of the world.
    else
     mpecho You have explored less than 10% of the world.
    endif
### faction Usage:
    faction(character factionid == value)
This function checks to see if the player or mob given has the given faction. If it does not, the value will always be empty string. Otherwise, it compares the value of the players faction with the value. If the value is numeric, it will compare the numeric value of the players faction. If the value is non-numeric, it will compare the name of the range into which the player falls in the given faction with the value given. EXAMPLE:
    if faction($n alignment.ini >500 ) or faction($n alignment.ini == 'Pure Goodness')
     mpecho The actor is either just north of neutral, or very very good.
    else
     mpecho The actor is some other alignment.
    endif
### goldamt Usage:
    goldamt(character > amount)
This evaluates the total amount of money that the character variable has on hand, or the value of the item if an item code is used instead of a character code. Where '==' may be any other logical operator from above. The value is always expressed in base gold, regardless of currency or denomination. EXAMPLE:
    if goldamt($n < 10000)
     mpecho The actor has less than 10000 coins on hand
    else
     mpecho The actor has 10000 coins or more on hand
    endif
### gstat Usage:
    gstat(target variable == value)
This is another powerful function which allows you to make comparisons based on numerous characteristics of the target. The target may be any code, including mobs or items. The variable may be any of those listed above under MPGSET in the section on Scriptable Commands, as well as some special codes, such as BASESTRENGTH, BASEDAMAGE, etc.. . The '==' may be any of the above logical operators, and the value any expression, including codes. EXAMPLES:
    if gstat($n CHARISMA > 10)
     mpecho The actor has a charisma greater than 10.
    endif
### has Usage:
    has(character item)
This checks whether the character has the given item in their inventory or on their person. EXAMPLE:
    if has($n a long sword)
     mpecho The actor has a long sword.
    else
     mpecho The actor does not have anything called 'a long sword'.
    endif
### hasacctattoo Usage: hasacctattoo(character tattoo) If your mud even uses the common account system, this command checks whether the character's common player account has had the given tattoo assigned to them. EXAMPLE: if hasacctattoo($n beastmark) mpecho The actor's account has the tattoo called beastmark. else mpecho The actor's account does not have the tattoo called beastmark. endif ### hasnum Usage:
    hasnum(character item > value)
This checks whether the character has some number of the given item in their inventory or on their person. The character may also be the code for a room. EXAMPLE:
    if hasnum($n 'a long sword' > 1)
     mpecho The actor has several long swords.
    else
     mpecho The actor does not have anything called 'a long sword', or only has 1.
    endif
### hastattoo Usage:
    hastattoo(character tattoo)
This checks whether the character has had the given tattoo assigned to them. EXAMPLE:
    if hastattoo($n beastmark)
     mpecho The actor has the tattoo called beastmark.
    else
     mpecho The actor does not have the tattoo called beastmark.
    endif
### hastattootime Usage: hastattootime([character] tattoo == amount) This checks whether the character has an amount of time remaining on a temporary tattoo assigned to them. Where '==' may be any logical operator from above. EXAMPLE: if hastattootime($n beastmark < 15) mpecho There is less than 1 minute left on the beastmark! endif ### hitprcnt Usage:
    hitprcnt(character == amount)
This checks compares the character's percentage of hitpoints remaining with the amount give. Where '==' may be any logical operator from above. The amount must evaluate to something between 1 and 100. EXAMPLE:
    if hitprcnt($n <= 20)
     mpecho The actor has 20% of their hit points or less remaining.
    else
     mpecho The actor has more than 20% of their hit points less.
    endif
### inarea Usage: Usage:
    inarea(target == areacode)
This checks to see if the target is in the area specified by the area code. The area code may be a area name, a mob name, or text from a local rooms name or description. The '==' may also be '!='. EXAMPLES:
    if inarea($i == Midgaard)
     mpecho This means I am in Midgaard.
    else
     mpecho I am not in Midgaard.
    endif

    if inarea($i != $f)
     mpecho I am not with the leader.
    else
     mpecho I am in room with the leader.
    endif
### incontainer Usage:
    incontainer(character container/mount)
This checks whether the character is on the given mount, or, if the character is an item, whether the first item with the given name is in the first container of the given name. EXAMPLES:
    if incontainer($n a chair)
     mpecho The actor is sitting on a chair
    else
     mpecho The actor is not sitting on a chair
    endif

    if incontainer($p a sack)
     mpecho The item is in a sack.
    else
     mpecho The item is not in a sack.
    endif
### inlocale Usage:
    inlocale(character roomclass)
This checks whether the character is presently standing in a room of a given class. The roomclass must be a specific Java name for a Room class. Values like CaveMaze, Jungle, InTheAir, Plains, etc are what we are after here. EXAMPLES:
    if inlocale($n InTheAir)
     mpecho The actor either flying or falling.
    else
     mpecho The actor is not up in the air.
    endif
### inroom Usage:
    inroom(target == roomcode)
This checks to see if the target is in the room specified by the room code. The room code may be a room id, a mob name, or text from the rooms name or description. If you need to be need to find mobile mobs or items, you can include the mob or item name, followed by @ followed by a room id or area name. The '==' may also be '!='. EXAMPLES:
    if inroom($i == a bathroom)
     mpecho This means I am in a bathroom.
    else
     mpecho I am not in a bathroom.
    endif

    if inroom($i != MyArea#20001)
     mpecho I am not in room MyArea#20001.
    else
     mpecho I am in room MyArea#20001.
    endif
### ipaddress Usage:
    ipaddress(character == string)
This compares the player characters ipaddress to the string. The '==' may also be '!='. EXAMPLE:
    if ipaddress($n == '127.0.0.1')
     mpecho You are logging on from the mud server
    else
     mpecho You must be someone else.
    endif
### isable Usage:
    isable(character spellid)
This checks whether the character has the given spell. The spellid may be any key word from any spell, skill, prayer, property, chant, or whatever. EXAMPLE:
    if isable($n Write)
     mpecho The actor has the writing skill.
    else
     mpecho The actor triggering me does not have the writing skill.
    endif
### isalive Usage:
    isalive(character)
This checks whether the character is alive. EXAMPLE:
    if isalive($i)
     mpecho I am not yet dead!
    endif
### isbehave Usage:
    isbehave(character behaviorid)
This checks whether the character has a given behavior. The behaviorid must be the full Java name of the behavior. EXAMPLE:
    if isbehave($n Mobile)
     mpecho The actor triggering me is mobile.
    else
     mpecho The actor triggering me is not mobile.
    endif
### isbirthday Usage: isbirthday(character) This checks to see if the characters birthday is today (on the global clock). EXAMPLE: if isbirthday($n) mpecho Happy Birthday $n. else mpecho Happy Un-Birthday $n! endif ### ischarmed Usage:
    ischarmed(character)
This checks to see if the character variable is charmed. EXAMPLE:
    if ischarmed($n)
     mpecho This means the person triggering me is charmed.
    else
     mpecho This person triggering my prog is not charmed.
    endif
### iscontent Usage: iscontent(container itemname) This checks to see if the first container (or rideable) of the given name contains an item of the given name (or rider). EXAMPLE: if iscontent($o 'a dagger') mpecho This means the container $o contains a dagger. else mpecho The container $o is not a container, or does not contain a dagger. endif ### isday Usage:
    isday(number)
This checks whether the current day of the month is the one given. EXAMPLE:
    if isday(10)
     mpecho It is the 10th of the month.
    endif
### isevil Usage:
    isevil(character)
This checks whether the character is evil. EXAMPLE:
    if isevil($i)
     mpecho I am evil!
    else
     mpecho I am either neutral or good.
    endif
### isfight Usage:
    isfight(character)
This checks to see if the character variable is in combat. EXAMPLE:
    if isfight($i)
     mpecho I am fighting right now.
    else
     mpecho I am not fighting.
    endif
### isfollow Usage:
    isfollow(character)
This checks to see if the character variable's master (the person they are following) is in the room. EXAMPLE:
    if isfollow($i)
     mpecho I am following someone and they are in the room with me.
    else
     mpecho I am not following someone, or they are not in the room.
    endif
### isgood Usage:
    isgood(character)
This checks whether the character is good. EXAMPLE:
    if isgood($i)
     mpecho I am good!
    else
     mpecho I am either neutral or evil.
    endif
### ishere Usage:
    ishere(name)
This checks whether a mob or item of the given name is in the room. Obviously, checking for $i will always return true when a mob is being scripted, so the best choice for an argument is a literal string. EXAMPLE:
    if ishere(a happy frog)
     mpecho A happy frog is in the room.
    else
     mpecho A happy frog is not in the room.
    endif
### ishour Usage: ishour(integer) This function is used to check the mud hour of the day. EXAMPLE: if ishour(5) mpecho It is nighttime. else mpecho It must be dawn, dusk, or daytime. endif ### isimmort Usage:
    isimmort(character)
This checks to see if the character variable is immortal. In CoffeeMud, that means they have the security code IMMORT, which makes them unable to die. EXAMPLE:
    if isimmort($n)
     mpecho The person triggering my prog is an immortal or lord.
    else
     mpecho The person triggering my prog is a mortal.
    endif
### islike Usage: islike(target mask) This checks whether a mob or item target of the given name meets the criterium described by the given mask. The format of the mask is described in the online help under ZAPPERMASKS, which is why the masks are still referred to as "zapper mask syntax". EXAMPLE:
    if islike($n '-TATTOO +KILLERBOY')
     mpecho The person has the killerboy tattoo.
    else
     mpecho The person does not have the killerboy tattoo.
    endif
### islocked Usage:
    islocked(target)
    islocked(direction)
This checks to see if the target container or exit is closed and locked. The target may be either an item, or an item code ($o, $p), or a direction name (north, south, east, west, etc.), or a direction code ($x, $xN, $xS, etc..) EXAMPLE:
    if islocked(the chest)
     mpecho The chest is locked.
    else
     mpecho The chest is not locked.
    endif
### ismonth Usage: ismonth(integer) This function is used to check the mud month number. EXAMPLE: if ismonth(1) mpecho It is month 1. endif ### ismoon Usage:
    ismoon()
    ismoon(phase)
If no parameter is given, this function checks whether the moon can be seen by the monster. Typically this means that it is nighttime, they are outside, and the sky is clear. With a parameter, this function only checks the phase of the moon, regardless of whether or not it can be seen. Accepted phases are: "NEW", "WAXCRESCENT", "WAXQUARTER", "WAXGIBBOUS", "FULL", "WANEGIBBOUS", "WANEQUARTER", "WANECRESCENT", or "BLUE". EXAMPLE:
    if ismoon(waxquarter)
     mpecho There is a waxing quarter moon in the sky.
    else
     mpecho There is not a waxing quarter moon in the sky.
    endif
### isname Usage:
    isname(character keyword)
This function returns whether the keyword appears in the name of the character. EXAMPLES:
    if isname($n goober)
     mpecho The actor who caused the trigger is named goober.
    else
     mpecho The actor who caused the trigger is not named goober.
    endif

    if isname($n $i)
     mpecho I, or someone with my name, am/is the actor!
    else
     mpecho Someone else is the actor.
    endif
### isneutral Usage:
    isneutral(character)
This checks whether the character is neutral. EXAMPLE:
    if isneutral($i)
     mpecho I am neutral!
    else
     mpecho I am either good or evil.
    end
### isnpc Usage:
    isnpc(character)
This checks to see if a character variable is a mob. EXAMPLE:
    if isnpc($n)
     mpecho The actor setting my prog off is a mob.
    else
     mpecho The actor setting my prog off is a player character.
    endif
### isodd Usage:
    isodd(number)
This checks to see if the number provided is an odd whole number. Where number may be any literal or variable. EXAMPLE:
    if isodd('7') and isodd($0)
     mpecho Seven and $0 are odd.
    else
     mpecho Well, either Seven or $0 are not odd -- I'm guessing it's $0
    endif
### isopen Usage:
    isopen(target)
    isopen(direction)
This checks to see if the target container or exit is open. The target may be either an item, or an item code ($o, $p), or a direction name (north, south, east, west, etc.), or a direction code ($x, $xN, $xS, etc..) EXAMPLE:
    if isopen(the chest)
     mpecho The chest is open.
    else
     mpecho The chest is not open.
    endif
### ispc Usage:
    ispc(character)
This checks to see if a character variable is a player character. EXAMPLE:
    if ispc($n)
     mpecho The actor setting my prog off is a player character.
    else
     mpecho The actor setting my prog off is not a player character.
    endif
### ispkill Usage:
    ispc(character)
This checks to see if a character has their pkill flag set. Only really matters with pcs, so it is best to use this function in conjunction with ispc(character). EXAMPLE:
    if ispc($n) and ispkill($n)
     mpecho The actor setting my prog off is a player killer.
    else
     mpecho The actor setting my prog off is not a player killer.
    endif
### isquestmobalive Usage:
    isquestmobalive(number questname)
    isquestmobalive(mobname questname)
This function only works if the script was assigned to a mob as part of the ADDBEHAVIOR quest command. It checks to see if a mob of the given number or name is alive. The numbers refer to the order in which they were designated in the quest script. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. If the questname given is "ALL", then all running quests will be searched. EXAMPLE:
    if isquestmobalive(1 myquest)
     mpecho The first set mob in the quest myquest is still alive.
    else
     mpecho He's not dead yet.
    endif
### isrecall Usage: isrecall(target == roomcode) This checks to see if the target is originally from the room specified by the room code. The room code may be a room id, a mob name (to compare start rooms), or text from the rooms name or description. If you need to be need to find mobile mobs or items, you can include the mob or item name, followed by @ followed by a room id or area name. The '==' may also be '!='. EXAMPLES:
    if isrecall($i == a bathroom)
     mpecho This means I am from a bathroom.
    else
     mpecho I am not from a bathroom.
    endif

    if isrecall($i != MyArea#20001)
     mpecho I am not from room MyArea#20001.
    else
     mpecho I am from room MyArea#20001.
    endif
### isrlhour ### isrlday ### isrlmonth ### isrlyear Usage: isrlhour(integer) This checks the real-life hour of the day (0-23), day of the month (1-31), month of the year (1-12), or year against the given integer value.. EXAMPLES: if isrlday(15) mpecho This means it is the 15th of the month. endif ### isseason Usage:
    isseason(seasonname)
This function is used to check the season of the year. Valid seasonnames include "WINTER", "SPRING", "SUMMER", or "FALL". EXAMPLE:
    if isseason(summer)
     mpecho Yea, its summertime!
    else
     mpecho Boo! It's not summer yet.
    endif
### isservant Usage:
    isservant(character)
This function is used to check whether the given player or mob is serving anyone in the room. EXAMPLE:
    if isservant($i)
     say I greet my master.
    else
     say I await my master.
    endif
### isspeaking Usage:
    isspeaking(character language)
This function returns whether the given character is speaking the given language. You can also enter NONE as a language name to check for Common. EXAMPLES:
    if isspeaking($n Elvish)
     mpecho The actor who caused the trigger is speaking Elvish.
    else
     mpecho The actor who caused the trigger is not speaking Elvish.
    endif
### istime Usage:
    istime(integer)
    istime(todword)
This function is used to check the time. You may either specify a numeric hour of the day, or a time of day description, such as "DAY", "DAWN", "DUSK", or "NIGHT". EXAMPLE:
    if istime(night)
     mpecho It is nighttime.
    else
     mpecho It must be dawn, dusk, or daytime.
    endif
### isweather Usage:
    isweather(weathername)
This function is used to check the weather where the monster is at. If the monster is indoors, this function will only return true for "CLEAR". Other valid weathernames include: "CLOUDY", "WINDY", "RAIN", "THUNDERSTORM", "SNOW", "HAIL", "HEAT", "SLEET", "BLIZZARD", "DUST", "DROUGHT", "COLD" EXAMPLE:
    if isweather(rain)
     mpecho Rain, rain go away...
    else
     mpecho We can play! No Rain!
    endif
### isyear Usage: isyear(integer) This function is used to check the mud year. EXAMPLE: if isyear(1) mpecho It is year 1. endif ### itemcount Usage:
    itemcount(object == number)
This checks the total count of items in the given variable, which includes stack-counts. An item object will check the stack count, a container will check the stack count of the contents, and ditto for rooms, mobs, or areas. Where '==' may be any of the logical operators mentioned above. EXAMPLES:
    if item($o >= 15)
     mpecho That is a stack of 15 items or more
    else
     mpecho That is a stack of less than 15 items
    endif
### level Usage:
    level(character == number)
This checks the total level of the character variable. Where '==' may be any of the logical operators mentioned above. EXAMPLES:
    if level($n <= 15)
     mpecho The actor triggering me is 15th level or less.
    else
     mpecho The actor triggering me is above 15th level.
    endif

    if level($n > $%level($i)%)
     mpecho The actor triggering me is higher level than me.
    else
     mpecho The actor triggering me is my level or under.
    endif
### math Usage: math(expression == expression) This function compares the total results of evaluating two very simple mathematical expressions. Variables can be included in the expressions via the normal $ code syntax, but the only operators allowed are +, -, *, or \. You may also use () to group expressions within an expression, or the ? to separate a random range. The '==' may also be any of the logical operators from above. EXAMPLES: if math('1+1' != '2') mpecho There is something wrong with the universe! endif if math('1?5' > 3) mpecho Ahh, I did not pick a random number from 1-5 that was greater than 3. Darn! endif ### mobitem Usage:
    mobitem(character number keywords)
This infrequently used function checks whether the numberth item in characters inventory has keywords in its name. EXAMPLE:
    if mobitem($n 1 sword) or mobitem ($n $g.1 sword)
     mpecho Either the actors first item is a sword,
     mpecho or an item whose cardinality is represented by the code
     mpecho $g.1 is a sword.
    else
     mpecho Neither of those items is a sword.
    endif
### mood Usage: mood(character == GRUMPY) This checks the mood of the character variable. Where '==' may be another logical operator from above. EXAMPLE:
    if mood($n == 'LONELY')
     mpecho The actor triggering me appears to be lonely.
    else
     mpecho The actor triggering me appears not to be lonely.
    endif
### number Usage:
    number(string)
This function returns whether the string given is a number. EXAMPLES:
    if number($g.2)
     mpecho The second parameter to this function_prog is a number.
    else
     mpecho The second parameter to this function_prog is not a number.
    endif
### numitemsmob Usage:
    numitemsmob(character == number)
This function compares the total number of items in the characters inventory to the number given. This function only counts items not in a container, or sheathed. It does count worn items. The '==' may also be any of the logical operators from above. EXAMPLES:
    if numitemsmob($n > 10)
     mpecho The actor has an inventory size greater than 10.
    else
     mpecho The actor has an inventory size less than or equal to 10.
    endif
### numitemsroom Usage:
    numitemsroom( == number)
This function compares the total number of items in the same room as the monster to the number given. This function only counts items not in a container. The '==' may also be any of the logical operators from above. EXAMPLES:
    if numitemsroom( > 10)
     mpecho There are more than 10 items in this room.
    else
     mpecho There are 10 or less items in the room.
    endif
### numitemsshop Usage:
    numitemsshop(shopkeeper == number)
This function compares the total number of items in the shopkeepers inventory to the number given. The '==' may also be any of the logical operators from above. EXAMPLES:
    if numitemsshop($n > 10)
     mpecho The shop has an inventory size greater than 10.
    else
     mpecho The shop has an inventory size less than or equal to 10.
    endif
### nummobs Usage:
    nummobs(name == number)
    nummobs('MASK=zappermask' == number)
This function compares the total number of mobs with the given name to the number. The second syntax allows you to substitute a zapper mask for the name, provided it starts with the MASK= string. See help on ZAPPERMASKS for more information on how to format a zapper mask. This function counts every single mob in the whole world, whether they are seen or detectable or not. The '==' may also be any of the logical operators from above. EXAMPLES:
    if nummobs(goobers > 10)
     mpecho There are more than 10 goobers in the world.
    else
     mpecho There are 10 or less goobers in the world.
    endif
### nummobsinarea Usage:
    nummobsinarea(name == number)
    nummobsinarea('MASK=zappermask' == number)
This function compares the total number of mobs with the given name to the number. The second syntax allows you to substitute a zapper mask for the name, provided it starts with the MASK= string. See help on ZAPPERMASKS for more information on how to format a zapper mask. This function counts every single mob in the same area as the scripted monster or object, whether they are seen or detectable or not. The '==' may also be any of the logical operators from above. EXAMPLES:
    if nummobsinarea(goobers > 10)
     mpecho There are more than 10 goobers in this area.
    else
     mpecho There are 10 or less goobers in this area.
    endif
### nummobsroom Usage:
    nummobsroom(pattern == number)
    nummobsroom('MASK=zappermask' == number)
This function compares the total number of mobs in the same room as the monster, whose names or display texts match the given pattern to the number given. A pattern of * may be used to count all mobs of any name. The second syntax allows you to substitute a zapper mask for the name pattern, provided it starts with the MASK= string. See help on ZAPPERMASKS for more information on how to format a zapper mask. This function counts players, npcs, and the hidden and undetectable. The '==' may also be any of the logical operators from above. EXAMPLES:
    if nummobsroom(* > 10)
     mpecho There are more than 10 mobs in this room.
    else
     mpecho There are 10 or less mobs in the room.
    endif
### numpcsarea Usage:
    numpcsarea( == number)
This function compares the total number of players in the same area as the monster to the number given. This function counts players only, including the hidden and undetectable. The '==' may also be any of the logical operators from above. EXAMPLES:
    if numpcsarea( > 10)
     mpecho There are more than 10 pcs in this area.
    else
     mpecho There are 10 or less pcs in the area.
    endif
### numpcsroom Usage:
    numpcsroom( == number)
This function compares the total number of players in the same room as the monster to the number given. This function counts players only, including the hidden and undetectable. The '==' may also be any of the logical operators from above. EXAMPLES:
    if numpcsroom( > 10)
     mpecho There are more than 10 pcs in this room.
    else
     mpecho There are 10 or less pcs in the room.
    endif
### numraces Usage:
    numraces( race == number)
This function compares the total number of mobs with the given race to the number. This function counts every single mob in the whole world, whether they are seen or detectable or not. The '==' may also be any of the logical operators from above. EXAMPLES:
    if numraces(Goblin > 10)
     mpecho There are more than 10 goblins in the world.
    else
     mpecho There are 10 or less goblins in the world.
    endif
### numracesinarea Usage:
    numracesinarea(race== number)
This function compares the total number of mobs with the given race to the number. This function counts every single mob in the same area as the scripted monster or object, whether they are seen or detectable or not. The '==' may also be any of the logical operators from above. EXAMPLES:
    if numracesinarea(Goblin > 10)
     mpecho There are more than 10 goblins in this area.
    else
     mpecho There are 10 or less goblins in this area.
    endif
### position Usage:
    position(character == posword)
This checks the position of the character variable. The position is a word, either SITTING, STANDING, or SLEEPING. The '==' may also be another of the logical operators from above. EXAMPLES:
    if position($n == STANDING)
     mpecho This means that the actor is standing.
    else
     mpecho This means the actor is not standing.
    endif
### pracs Usage:
    pracs(character == number)
This checks the number of practice points the mob variable has. Where '==' may be any of the logical operators mentioned above. EXAMPLES:
    if pracs($n <= 15)
     mpecho The actor triggering me has fewer than 16 practices.
    else
     mpecho The actor triggering me has more than 15 practices.
    endif

    if pracs($n > $%pracs($i)%)
     mpecho The actor triggering me has more practices than me.
    else
     mpecho The actor triggering me has the same or fewer practices than me.
    endif
### questarea Usage: questarea(areaname questname) This checks whether the given areaname has been designed by the given quest using, for instance, SET ROOM, or SET ROOMGROUP. This is typically a way of telling which quests are using the given area. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. EXAMPLES: if questarea('$%INAREA($n)%' myquestname) mpecho This means that the actor is in an area designed by quest myquestname. else mpecho This means that the actor is NOT in an area designed by quest myquestname. endif ### questobj Usage:
    questobj(item questname)
This checks whether the given item is an official item created by a quest of the given questname. This means the quest script used the SET ITEM, SET ITEMGROUP, or a similar command for the given item. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. If the questname given is "ALL", then all running quests will be searched. EXAMPLES:
    if questobj($o myquest)
     mpecho This means that item is a quest item for quest myquest.
    else
     mpecho This means the item is not a quest item for quest myquest.
    endif
### questmob Usage:
    questmob(character questname)
This checks whether the given character is an official mob created by a quest of the given questname. This means the quest script used the SET MOB, SET MOBGROUP, or a similar command for the given mob. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. If the questname given is "ALL", then all running quests will be searched. EXAMPLES:
    if questmob($n myquest)
     mpecho This means that the actor is a quest mob for quest myquest.
    else
     mpecho This means the actor is not a quest mob for quest myquest.
    endif
### questpoints Usage:
    questpoints(character == number)
This checks the number of quest points the mob variable has. Where '==' may be any of the logical operators mentioned above. EXAMPLES:
    if questpoints($n <= 15)
     mpecho The actor triggering me has fewer than 16 quest points.
    else
     mpecho The actor triggering me has more than 15 quest points.
    endif

    if questpoints($n > $%questpoints($i)%)
     mpecho The actor triggering me has more quest points than me.
    else
     mpecho The actor triggering me has the same or fewer quest points than me.
    endif
### questroom Usage:
    questroom(roomid questname)
This checks whether the given roomid has been designed by the given quest using, for instance, SET ROOM, or SET ROOMGROUP. This is typically a way of telling which quests are using the given room. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. EXAMPLES:
    if questroom('$%INROOM($n)%' myquestname)
     mpecho This means that the actor is in a room designed by quest myquestname.
    else
     mpecho This means that the actor is NOT in a room designed by quest myquestname.
    endif
### questscripted Usage:
    questscripted(character questname)
This checks whether the given character has a script assigned by a quest on them at the given moment. This is typically a way of telling which quests are in progress for the given character. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. If a quest name of ALL is given, then every running quest will be checked. EXAMPLES:
    if questscripted($n myquestname)
     mpecho This means that the actor is on the quest myquestname.
    else
     mpecho This means the actor is not on the quest myquestname.
    endif
### questwinner Usage:
    questwinner(character questname)
This checks whether the given character has been declared a winner of the quest in the past via the MPQUESTWIN command. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. The questname may also be set to 'previous' to check whichever quest is previous to this one on the scripted objects list of quest scripts. If the current script is the first, then questwinner will always be true. It requires that the script using this syntax be associated with a quest. EXAMPLES:
    if questwinner($n myquest)
     mpecho This means that the actor has been a winner of the quest myquest.
    else
     mpecho This means the actor has not been a winner of the quest myquest.
    endif
### qvar Usage: qvar(questname varname == value) This is used to evaluate one of the official or user-defined quest variables. User-defined quest variables are defined using MPQSET. Official variables names include: "CLASS", "NAME", "DURATION", "EXPIRATION", "WAIT", "MINPLAYERS", "PLAYERMASK", "RUNLEVEL", "DATE", "MUDDAY", "REMAINING", or "INTERVAL". Official object variables include: "AREA", "MOBTYPE", "MOBGROUP", "ITEMTYPE", "LOCALE", "ROOM", "MOB", "ITEM", "ITEMGROUP", "ROOMGROUP", "LOCALEGROUP", "ROOMGROUPAROUND", "LOCALEGROUPAROUND", "PRESERVE", "AREAGROUP", "FACTION", "FACTIONGROUP", "AGENT", "AGENTGROUP", "ACTION", "ACTIONGROUP", "TARGET", "TARGETGROUP", "MOTIVE", "MOTIVEGROUP", "WHEREHAPPENED", "WHEREHAPPENEDGROUP", "WHEREAT", "WHEREATGROUP", "WHENHAPPENED", "WHENHAPPENEDGROUP", "WHENAT", "WHENATGROUP", "TOOL", "TOOLGROUP". For the objects, you may also add the extension "_ROOMID" to return the official room id of the location of the object (if available), or "_CLASS" to return the CoffeeMud Class ID, or the Java class name, whichever is appropriate. If the Scriptable behavior was granted as part of a Quest, then * may be substituted for the questname. Where '==' may be any of the logical operators mentioned above. EXAMPLES:
    if qvar(myquest myvarname == 'myvalueformyvarname')
     mpecho This means that the user defined variable 'myvarname' has been previously set.
    else
     mpecho This means the user defined variable 'myvarname' has not been previously set.
    endif
### race Usage:
    race(character == race)
This function compares the race of the character variable with the race name given. For a list of race names, do LIST RACES from the command line in the mud. The '==' may also be another of the logical operators from above. EXAMPLE:
    if race($n == Goblin)
     mpecho The actor is a goblin.
    else
     mpecho The actor is not a goblin.
    endif
### racecat Usage:
    race(character == category)
This function compares the racial category of the race of the character variable with the racial category given. For a list of racial categories, do LIST RACES from the command line in the mud. The '==' may also be another of the logical operators from above. EXAMPLE:
     if racecat($n == Elf)
     mpecho The actor is an Elf, or Elf-kin.
     else
     mpecho The actor is not an Elf-Kin.
     endif
### rand Usage:
    rand(integer)
This generates a random number and checks to see if it is under the integer. This is best used for random events where there are only two outcomes. EXAMPLE:
    if rand(40)
     mpecho This is under 40% chance for me to echo this.
    else
     mpecho Not under 40%.
    endif
### rand0num Usage:
    rand0num(integer == integer)
This generates a random number from 0 to the first integer given minus 1, and checks to see if it is under the value give in the second integer. This is best used not in its pure function form, but as a string variable (see the $% format above). It allows one to randomly grab an item in a string list. See the example below. EXAMPLE:
    if rand0num(2 == 0)
     MPSETVAR $i GREETINGLIST hi howdy hello greetings ho
     say I just wanted to say $<$i GREETINGLIST>.$%RAND0NUM(5)%!
    endif
### randnum Usage:
    randnum(integer == integer)
This generates a random number from 1 to the first integer given, and checks to see if it is under the value give in the second integer. This is best used for random events where there are only two outcomes. EXAMPLE:
    if rand(1000 == 5)
     mpecho This is under a 5 in 1000 chance for me to echo this.
    else
     mpecho Not under 5 in 1000.
    endif
### roomitem Usage:
    roomitem(number keywords)
This infrequently used function checks whether the numberth item in the room has keywords in its name. EXAMPLE:
    if roomitem(1 sword) or roomitem ($g.1 sword)
     mpecho Either the rooms first item is a sword,
     mpecho or an item whose cardinality is represented by
     mpecho the code $g.1 is a sword.
    else
     mpecho Neither of those items is a sword.
    endif
### roommob Usage:
    roommob(number keywords)
This infrequently used function checks whether the numberth mob in the room has keywords in its name. EXAMPLE:
    if roommob(1 joe) or roommob($g.1 joe)
     mpecho Either the rooms first mob is named joe,
     mpecho or a mob whose cardinality is represented by
     mpecho the code $g.1 is joe.
    else
     mpecho Neither of those mobs is joe.
    endif
### sex Usage:
    sex(character == letter)
This compares the sex of the character variable to the letter given. The letter may be "M", "F", or "N". The '==' may also be another of the logical operators from above. EXAMPLES:
    if sex($n == M)
     mpecho The actor triggering me is a male.
    else
     mpecho The actor triggering me is not a male.
    endif

    if sex($n != $%sex($n)%)
     mpecho The actor triggering me is not the same sex as me.
    else
     mpecho The actor triggering me is the same sex as me.
    endif
### shophas Usage:
    shophas(character item)
This checks whether the shopkeeper has the given item in their shop inventory. If this function returns true, it will also set the value of $9 to a string description of the price of the item. EXAMPLE:
    if shophas($n a long sword)
     mpecho This shop has a long sword for sale.
    else
     mpecho The shop does not sell anything called 'a long sword'.
    endif
### shopitem Usage:
    shopitem(shopkeeper number keywords)
This infrequently used function checks whether the numberth item in the shopkeepers inventory has keywords in its name. If this function returns true, it will also set the value of $9 to a string description of the price of the item. EXAMPLE:
    if shopitem($n 1 sword) or shopitem ($n $g.1 sword)
     mpecho Either the shops first item is a sword,
     mpecho or a shop item whose cardinality is represented by the code
     mpecho $g.1 is a sword.
    else
     mpecho Neither of those shop items is a sword.
    endif
### stat Usage:
    stat(target variable == value)
This is a powerful function which allows you to make comparisons based on numerous characteristics of the target. The target may be any code, including mobs or items. The variable may be any of those listed above under MPGSET in the section on Scriptable Commands. The '==' may be any of the above logical operators, and the value any expression, including codes. This function is like gstat, with one important difference: stat respects only the variables which the target has available. For Generic mobs and items, this will be many more than for Standard mobs and items. For this reason, it is almost always preferable to use gstat. EXAMPLES:
    if stat($n CHARISMA > 10)
     mpecho The actor, if a generic mob, has a charisma greater than 10.
    endif
### strcontains Usage: strcontains(string words) This function searches the first string to see if the set of words described by the second string is contained therein. The search is case-insensitve, and ignores all punctuation. The set of words may be double-quoted to include spaces. Each word or word grouping must be separated by one of three special characters: word1 word2 means the string contains word1 which is immediately followed by word2 word1 & word2 means the string must contains word1 and word2 in any order word1 | word2 means the string contains word1 or word2 word1 > word2 means the string contains both word1 and word2, but word2 comes after word1 in the string (though other words may separate them) word1 < word2 means the string contains both word1 and word2, but word1 comes after word2 in the strong You may also use parenthesis to group word checks together. EXAMPLE:
    if strcontains('one two three four' '(one > four) & (two three)')
     mpecho The string meets my word criteria
    else
     mpecho The string does not meet my word criteria.
    endif
### strin Usage:
    strin(string string)
This function searches the first string to see if the second string appears as a whole word within it. If so, this function returns true. The first string can also be grouped into phrases using double quotes, which can be useful when giving a list of roomids or other descrete things to search for. In fact, to fascilitate this, the second argument may be the special code string '$$r' to search for the scripted objects current room location. EXAMPLE:
    if strin('one two three four' 'three')
     mpecho The word three appears in the list of words.
    else
     mpecho Since no variables were used in the example, this is technically impossible.
    endif

    if strin('"Area Name#1" "MyArea#2" "The Area#444"' '$$r')
     mpecho I am in one of those rooms
    else
     mpecho I am not in any of those rooms
    endif
### trains Usage:
    trains(character == number)
This checks the number of training sessions the mob variable has. Where '==' may be any of the logical operators mentioned above. EXAMPLES:
    if trains($n <= 15)
     mpecho The actor triggering me has fewer than 16 trains.
    else
     mpecho The actor triggering me has more than 15 trains.
    endif

    if trains($n > $%trains($i)%)
     mpecho The actor triggering me has more trains than me.
    else
     mpecho The actor triggering me has the same or fewer trains than me.
    endif
### value Usage:
    value(character currency > amount)
    value(coinitem currency > amount)
This evaluates the total amount of money that the character variable has on hand in the given currency, or the value of the coins of the given currency. Where '==' may be any other logical operator from above. The value is always expressed in base gold for comparison purposes only. If a coin item is not of the given currency, the value will always be 0. EXAMPLE:
    if value($n 'COPPER' < 10000)
     mpecho The actor has less than 10000 base-gold with of money in the 'COPPER' currency on hand
    else
     mpecho The actor has plenty
    endif
### var Usage:
    var(character variable == value)
This function compares the variable belonging to the character to the given value. The character is almost always a code of some sort, where the variable is almost always a literal string. The value may be anything necessary. Where '==' may be any of the above logical operators. See MPSETVAR for information on settings variables, on how to use them with quests, and on variable scopes. EXAMPLE:
    if var($n KILLS > 10)
     mpecho The actor's KILLS variable is greater than 10.
    else
     mpecho The actor's KILLS variable is equal to or less than 10.
    endif
### worn Usage:
    worn(character item)
This function checks whether the character is wearing an item of the given name. EXAMPLE:
    if worn($n brass shirt)
     mpecho The actor is wearing a brass shirt somewhere.
    else
     mpecho The actor is not wearing a brass shirt.
    endif
### wornon Usage: wornon(character location item) This function checks whether the character is wearing an item of the given name on the given location. The name can be a substring or partial match. Valid locations include: 'inventory', 'head', 'neck', 'torso', 'arms', 'left wrist', 'right wrist', 'left finger', 'right finger', 'feet', 'held', 'wield', 'hands', 'floating nearby', 'waist', 'legs', 'eyes', 'ears', 'body', 'mouth', 'back' EXAMPLE: if wornon($n feet 'purple shoes') mpecho The actor is wearing a purple shoes on his feet. else mpecho The actor is not wearing purple shoes on his feet. endif