http://wiki.cleftofdimensions.net/api.php?action=feedcontributions&feedformat=atom&user=PascalCleft of Dimensions Wiki - User contributions [en]2026-04-25T23:46:15ZUser contributionsMediaWiki 1.39.3http://wiki.cleftofdimensions.net/index.php?title=Fossil_Roo&diff=4308Fossil Roo2021-06-09T01:05:33Z<p>Pascal: </p>
<hr />
<div>{{AreaStats | color = #3c3 | picture = fossilroo.png | name = Fossil Roo | source = Final Fantasy IX | builder = Cooper | level range = 56-60 | linked = Yes | caption = "Time to die." }}<br />
<br />
Fossil Roo is an old excavation site that was closed down for being far too dangerous and killing tons of people.<br />
<br />
== Sights ==<br />
Lots and lots of fossils! Bring a pickaxe.<br />
<br />
== Travel ==<br />
Very few people know how to get to Fossil Roo, the only person with any clue being Vickers, a paleontologist residing in Crysta.<br />
<br />
== Inhabitants ==<br />
Large numbers of vicious monsters.<br />
<br />
== Law, Government, and Politics ==<br />
<br />
Being basically unknown to the world at large, Fossil Roo is ungoverned as far as anyone is concerned.<br />
<br />
== Quests ==<br />
<br />
Safe passage through the tunnel requires solving the dangerous puzzles throughout the area! Good luck figuring out what they are, though.<br />
<br />
== The Great Explorer Luigi Says ==<br />
[[file:luigi.jpg]]<br />
"Being unexplored for-a decades, Fossil Roo will likely try to kill you as soon as you find it!"<br />
<br />
[[Category:Areas]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=File:Fossilroo.png&diff=4307File:Fossilroo.png2021-06-09T01:03:50Z<p>Pascal: </p>
<hr />
<div></div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Fossil_Roo&diff=4306Fossil Roo2021-06-09T01:03:35Z<p>Pascal: Created page with "{{AreaStats | color = #3c3 | picture = File:fossilroo.png | name = Fossil Roo | source = Final Fantasy IX | builder = Cooper | level range = 56-60 | linked = Yes | caption..."</p>
<hr />
<div>{{AreaStats | color = #3c3 | picture = [[File:fossilroo.png]] | name = Fossil Roo | source = Final Fantasy IX | builder = Cooper | level range = 56-60 | linked = Yes | caption = "Time to die." }}<br />
<br />
Fossil Roo is an old excavation site that was closed down for being far too dangerous and killing tons of people.<br />
<br />
== Sights ==<br />
Lots and lots of fossils! Bring a pickaxe.<br />
<br />
== Travel ==<br />
Very few people know how to get to Fossil Roo, the only person with any clue being Vickers, a paleontologist residing in Crysta.<br />
<br />
== Inhabitants ==<br />
Large numbers of vicious monsters.<br />
<br />
== Law, Government, and Politics ==<br />
<br />
Being basically unknown to the world at large, Fossil Roo is ungoverned as far as anyone is concerned.<br />
<br />
== Quests ==<br />
<br />
Safe passage through the tunnel requires solving the dangerous puzzles throughout the area! Good luck figuring out what they are, though.<br />
<br />
== The Great Explorer Luigi Says ==<br />
[[file:luigi.jpg]]<br />
"Being unexplored for-a decades, Fossil Roo will likely try to kill you as soon as you find it!"<br />
<br />
[[Category:Areas]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Kakkara_Desert&diff=4305Kakkara Desert2021-06-08T21:58:57Z<p>Pascal: /* Travel */</p>
<hr />
<div>{{AreaStats | color = #FFCC00 | picture = lom46.jpg | name = Kakkara Desert | source = Various | builder = Arilothas/Ageatii| level range = 51+ | linked = Yes | caption = Desert}}<br />
<br />
The Kakkara Desert is a desert island in [[Shadmire]]. It is near [[Caspia]], which sits on the other end of the same island.<br />
<br />
== History ==<br />
<br />
'''20''' - Desperate to survive, a large group of individuals transplanted into the Cleft of Dimensions begins digging into the earth to escape the harsh weather of the Cleft's early years.<br />
<br />
'''23''' - After years of digging, a tunnel is discovered deep in the ground, leading to Fa'Diel.<br />
<br />
'''325''' - [[Monotoli Inc.]] establishes a sandship transportation system.<br />
<br />
== Sights ==<br />
<br />
It's a very barren and boring desert. There is mostly nothing to see out here.<br />
<br />
===Dry Dry Outpost===<br />
A small outpost exists on the edge of the desert near the sandship dock. It was originally founded to support the sandship workers, but neighboring chobins moved in shortly after, expressing their natural entrepreneurial spirit.<br />
<br />
== Travel ==<br />
<br />
Traveling by foot in the desert is strongly discouraged. Some of the more experienced utilize mounts to trek across the desert. A mechanical sandship acts as a ferry between the ends of the desert, where [[Caspia]], [[Gobi's Valley]], and the [[Sea of Wonders]] lies to the northeast, and _____ lies to the south.<br />
<br />
== Inhabitants ==<br />
<br />
=== Vampires ===<br />
<br />
There are rumors of a dark world of vampires somewhere around the desert. They say all who go looking for the vampire castle never return, but it's probably because of heatstroke.<br />
<br />
=== Creatures ===<br />
<br />
The wildlife is sparse here, consisting of a small colony of lanmolas and a few desert mallards that congregate around the water.<br />
<br />
== Law, Government, and Politics ==<br />
<br />
Kakkara Desert exists on the largest island of the [[Shadmire]] Archipelago. It belongs to the Shadmire Kingdom, but there are no laws that govern this specific region, as it is ungovernable.<br />
<br />
Monotoli Inc. has staked a minor claim in the region with their Sandship Industry which is necessary for much communication and resources across the island.<br />
<br />
== Quests ==<br />
<br />
Can you assist an aspiring chef?<br />
<br />
== The Great Explorer Luigi Says ==<br />
[[file:luigi.jpg]]<br />
"It's-a heavy, but the water keg is-a very big water container! La Funk canteens are-a good substitute if weight is a concern. Luigi carries a blue turban around to refill his canteens on the go!"<br />
<br />
[[Category:Areas]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Wizard&diff=4303Wizard2021-06-07T13:01:21Z<p>Pascal: /* Spells */</p>
<hr />
<div>{| style="position:relative; margin: 0 0 0.5em 1em; border-collapse: collapse; float:right; background:white; clear:right; width:200px;" border="1" cellpadding="0"<br />
|- style="text-align:center;"<br />
! style="background: {{{color|#fff}}};"|'''{{{name|{{PAGENAME}}}}}'''<br />
|-<br />
|<div style="text-align:center">[[image:Wizard.png]]<br><small>Magical artillery, possibly in a pointy hat</small></div><br />
|-<br />
|Style: Offensive Magic User<br />
|-<br />
|Primary Stat: [[Statistics#Intelligence|Intelligence]]<br />
|-<br />
|HP Gain per Level: 6-9<br />
|-<br />
|MP Gain per Level: 7-10<br />
|-<br />
|Weapon Skills: 1<br />
|}<br />
<br />
='''Wizard'''=<br />
The Wizard is a class which can cast offensive magic proficiently. Wizards get an array of spells to damage their enemies with. Wizards can charge spells to increase their damage, and they can summon elementals at higher levels. They have poor HP and defensive skills, but make up for this with their ability to do lots of damage in a short time.<br />
<br />
At level 30, a Wizard may evolve into either an [[#Archmage|Archmage]] or an [[#Elementalist|Elementalist]].<br />
Wizards can choose one weapon type in which to be proficient.<br />
The primary attribute of the Wizard is [[Statistics#Intelligence|Intelligence]].<br />
<br />
<br />
==Skills==<br />
*'''Manashield''' - ''Level: 18'' - Lag: 4<br />
:This is a toggle skill that causes all damage directed toward the caster to deplete mana instead of HP, at twice the rate.<br />
<br />
==Spells==<br />
*'''Air Blast''' - ''Level: 1'' - Lag: 10 - ''Mana: 18''<br />
:Air Blast focuses nearby air into a forceful attack, pummeling the foe. Air Blast is a Tier 1 offensive spell and can be charged to deliver 1.5x the normal damage. It deals wind-type damage.<br />
:Air Blast imposes 17% less lag than comparable spells.<br />
*'''Gem Missile''' - ''Level: 2'' - Lag: 12 - ''Mana: 18''<br />
:Gem Missile takes nearby earth and rock to create a series of quick attacks upon a foe. Gem Missile is a Tier 1 offensive spell and can be charged to deliver 1.5x the normal damage. It deals earth-type damage.<br />
:Gem Missile has a 12.5% chance of dealing double damage.<br />
*'''Ice Smash''' - ''Level: 3'' - Lag: 12 - ''Mana: 18''<br />
:Ice Smash creates sharp thin shards of ice to stab the foe. Ice Smash is a Tier 1 offensive spell and can be charged to deliver 1.5x the the normal damage. It deals cold-type damage.<br />
:Ice Smash deals two distinct hits to the target and has a higher minimum damage than comparable spells.<br />
*'''Fireball''' - ''Level: 4'' - Lag: 12 - ''Mana: 18''<br />
:Fireball creates a large fireball which is hurled towards a foe. Fireball is a Tier 1 offensive spell and can be charged to deliver 1.5x the normal damage. It deals fire-type damage.<br />
:After its initial hit, Fireball inflicts a lingering burn amounting to 5% damage each pulse for three pulses.<br />
*'''Rhizome Lance''' - ''Level: 5'' - Lag: 12 - ''Mana: 15''<br />
:Rhizome Lance conjures giant roots from the earth to attack foes. Rhizome Lance is a Tier 1 offensive spell and can be charged to deliver 1.5x the normal damage. It deals wood-type damage.<br />
:Rhizome Lance costs 17% less mana than comparable spells.<br />
*'''Darkside''' - ''Level: 6'' - Lag: 12 - ''Mana: 18''<br />
:Darkside is a spell which calls upon the nature of the deep dark void to blot the caster's foes from existence. Darkside is a Tier 1 offensive spell and can be charged to deliver 1.5x the normal damage. It deals dark-type damage.<br />
:Darkside is 12.5% stronger than comparable spells, but it inflicts recoil damage to the caster amounting to 10% of the damage dealt to the target.<br />
*'''Invisibility''' - ''Level: 7'' - Lag: 12 - ''Mana: 40''<br />
: This is a cloaking spell, that makes the wizard, or their target, invisible to those who are not affected by 'detect invis'.<br />
*'''Detect Magic''' - ''Level:9'' - Lag: 12 - ''Mana: 5''<br />
:This spell allows the target to see magical auras on items, as well as giving a rough estimate on the mana reserves of other mobs. This can be cast on yourself as well as others.<br />
*'''Charge''' - ''Level: 10'' - Lag: 8 - ''Mana: 30''<br />
:The charge spell infuses the target with a charge, greatly improving the effects of the next spell used by the target. Most offensive spells will have their damage output increased by half when charged, although other spells may have other effects added. Charge wears off after it has boosted one spell.<br />
*'''Sleep''' - ''Level: 12'' - Lag: 12 - ''Mana: 96''<br />
:This is an enfeebling spell that, when successful, puts the target to sleep. Failing, however, will provoke the target to attack. Recasting on an already-sleeping foe will reset the duration of the spell, keeping victims tranquilized longer. Sleep is considered to be of the "Charm" element - thus, any enemy who is immune to charm will not fall asleep.<br />
*'''Wizen''' - ''Level: 14'' - Lag: 4 - ''Mana: 0''<br />
:Wizen exchanges a portion of the user's HP for MP. When cast, 1/5 of your max HP is drained, to restore about 1/5 of your max MP. Greater skill % increases the efficiency of this spell.<br />
*'''Detect Invisible''' - ''Level: 16'' - Lag: 12 - ''Mana: 5''<br />
:This spell is used to detect invisible entities, setting their long descriptions of those who are invisible with the (Invis) flag. It can be cast on yourself as well as others.<br />
*'''Kundela''' - ''Level: 20'' - Lag: 12 - ''Mana: 0''<br />
:Kundela deals maximum damage when your current MP is equal to one fifth of your max MP. The damage decreases as your current MP deviates from this target. Kundela has no MP cost but will always fully drain the caster's MP.<br />
*'''Blink''' - ''Level: 22'' - Lag: 8 - ''Mana: 40''<br />
:Blink teleports the caster randomly into a nearby room, allowing escape from combat or, sometimes, access to inaccessible areas. When charged, Blink may teleport the caster up to twice as far.<br />
*'''Syphon''' - ''Level: 24'' - Lag: 16 - ''Mana: 27''<br />
:Syphon is an attack spell that absorbs the target's hp, mana and moves, converting everything drained into mana for the caster. When charged, Syphon deals 1.5x damage and therefore 50% more returned mana.<br />
*'''Conjure Elemental''' - ''Level: 26'' - Lag: 12 - ''Mana: 40''<br />
:This is spell that creates a [[Pets#Followers|follower]] for the caster. The type of pet is determined by the owner's [[innate]]. Based upon the owner's innate, each elemental has its own weaknesses and strengths. The spell can be used with charge to allow the pet better resistances.<br />
:Charge will also allow this elemental to cast matching-innate spells, at the cost of the owner's mana.<br />
:As a follower and not a pet, a Wizard can still own a pet of whatever type and have a conjured Elemental.<br />
*'''Read Magic''' - ''Level: 28'' - Lag: 8 - ''Mana: 24''<br />
:The Read Magic spell allows witches to observe the current affects on a target, whether they are innate, granted by equipment, or the result of a spell.<br />
<br />
='''Archmage'''=<br />
The Archmage is one of two classes a [[#Wizard|Wizard]] may evolve into at level 30.<br />
<br />
Archmagi are scholars of the highest caliber, who have refined the art of spellcasting into sheer masterpieces. Their level of control over mana is so fine they can ensure their spells are flawlessly cast, or even<br />
reverse the elemental damage the inflict. An Archmage's repertoire is one of detailed skill, from the echoing of spells to confining a spell into a sacrificial staff or wand. Their signature ability is the<br />
practice of combining spells to create an entirely new effect.<br />
<br />
<br />
<br />
==Skills==<br />
*'''Surecasting''' - ''Level: 30'' - Lag: ---<br />
:Surecasting is a skill that can be toggled. When active, it ensures that any spells cast by the user will never fail. There is a chance, dependent on the user's skill in the spell being cast, that the spell will cost dramatically more mana than it normally would. This is capable of draining the user completely of mana, which will result in the user being stunned for a short while. Nonetheless, the spell will be cast even if it leaves the user completely depleted.<br />
*'''Combomagic''' - ''Level: 45'' - Lag: 12<br />
:Combomagic is a toggled skill. When active, if the two spells of the proper innates are cast consecutively on a single target, the second spell is replaced by a Tier 4 combospell.<br />
:The elemental composition and strength of the combospell depend on its components, whereas the mana cost, spell lag, and cooldown depend on the combospell itself.<br />
:Combomagic can be triggered by an ally's spells, spells from held items, or even a previous combospell. The main requirement is that the second component of the combospell is provided by a caster proficient in combomagic.<br />
<br />
{| class="wikitable"<br />
!colspan="6"|Tier 4 Spell Combos<br />
|-<br />
|(Moon OR Earth) + Fire <br />
|Flare Star<br />
|<br />
The flare star spell opens a portal to a nearby star directly in front of the<br />
caster's opponent. Peerless heat and radiation pours from the portal,<br />
incinerating the enemy. Victims of the flare star may even burst into flames,<br />
their grossly incandescent bodies continued fuel for the inferno.<br />
<br />
Flare Star is a Tier 4 offensive spell and can be charged to deliver 1.25x the<br />
damage. It deals dark and fire-type damage unless altered by combomagic.<br />
<br />
On a lethal blow, Flare Star inflicts damage, equal to its overkill damage, to<br />
all remaining enemies in the room, every pulse for three pulses.<br />
|-<br />
|(Earth OR Wind) + Water<br />
|Catastrophe<br />
|<br />
At the heart of the Catastrophe was a simple idea: they never wanted to go to<br />
war again. Wanted to rule it out. Make it so their enemies would never be able<br />
to threaten them ever again. The Catastrophe would stop the fighting cold, tear<br />
the earth to pieces from the inside. Then there was a breakthrough. It worked.<br />
<br />
Catastrophe is a Tier 4 offensive spell and can be charged to deliver 1.25x the<br />
damage. It deals earth and cold-type damage unless altered by combomagic.<br />
<br />
On a lethal blow, Catastrophe wracks the room: hp/mp/mv regen rates are cut 75%<br />
and movement costs are greatly increased, with duration dependent on overkill<br />
damage.<br />
|-<br />
|(Wind OR Wood) + Moon<br />
|Southern Cross<br />
|<br />
The heavens themselves become the artillery of he who casts the southern cross.<br />
The unlucky victim is vivisected by searing beams of starlight called down to<br />
earth at the caster's command. But stellar energy is not purely destructive, and<br />
the same starlight that brings the target to his knees may breathe vigor into<br />
the caster.<br />
<br />
Southern Cross is a Tier 4 offensive spell and can be charged to deliver 1.25x<br />
the damage. It deals wind, dark, and light-type damage unless altered by<br />
combomagic.<br />
<br />
On a lethal blow, Southern Cross cancels all lag for the caster and reduces all<br />
cooldowns, proportional to the amount of overkill damage.<br />
|-<br />
|(Wood OR Fire) + Earth<br />
|Ancient Power<br />
|<br />
Invoking ancient power calls upon prehistoric stone-like artifacts to burst from<br />
the earth. These stones, engraved with long-forgotten runes, are imbued with<br />
sentience that desires only destruction. A caster who fulfills the stones'<br />
deadly desires by laying waste to his enemies is granted power.<br />
<br />
Ancient Power is a Tier 4 offensive spell and can be charged to deliver 1.25x<br />
the damage. It deals wood and earth-type damage unless altered by combomagic.<br />
<br />
On a lethal blow, Ancient Power increases all stats of the caster to a degree<br />
dependent on the overkill damage and with duration dependent on the level of the<br />
victim.<br />
|-<br />
|(Fire OR Water) + Wind<br />
|Black Wind<br />
|<br />
The black wind howls... one among you will shortly perish. Wheter it comes as a<br />
burning, punishing wind or a frigid, piercing gale, the black wind is a dreadful<br />
spell, prophesied to carry death to those who feel it. Only a fool would not<br />
flee in terror before someone wielding this terrible force.<br />
<br />
Black Wind is a Tier 4 offensive spell and can be charged to deliver 1.25x the<br />
damage. It deals fire and wind-type damage unless altered by combomagic.<br />
<br />
On a lethal blow, Black Wind terrifies any remaining enemies in the room, who<br />
may immediately attempt to flee.<br />
|-<br />
|(Water OR Moon) + Wood<br />
|Grand Dream<br />
|<br />
They say this spell banishes its victim to the dream world, but those who<br />
survive never remember where they've been. We only know that sinking into the<br />
grand dream sends you somewhere for a very long time. Hair goes gray, the body<br />
rots or turns to stone, covered with moss or mold like something long abandoned<br />
in the forest.<br />
<br />
Grand Dream is a Tier 4 offensive spell and can be charged to deliver 1.25x the<br />
damage. It deals cold and wood-type damage unless altered by combomagic.<br />
<br />
On a lethal blow, Grand Dream fossilizes the victim. Sundry goods may be looted<br />
from a Grand Dream fossil, their number and quality based on the amount of<br />
overkill damage.<br />
|}<br />
<br />
*'''Trance''' - ''Level: 40'' - Lag:---<br />
:Trance is a passive skill that empowers the user for defeating many enemies consecutively. This triggers when the second foe is defeated ~30 seconds after the first foe.<br />
:As long as Trance is active, the user gains +2 Magroll/defeated foe, and regenerates mana as if they were asleep.<br />
:The longer you are in a trance, the more rapidly you must defeat foes to keep the trance going.<br />
:As a passive skill, trance works as soon as it is practiced above 1%. Higher skill makes it easier to stay in a longer trance.<br />
*'''Echomagic''' - ''Level: 55'' - Lag: ---<br />
:Echomagic is a toggled skill. When active, all offensive spells will hit a second time, several pulses after the original spell.<br />
:This increases the mana cost of the original spell by 50%. The power of the echoed spell increases with skill.<br />
:The echoed spell will target whoever the caster is currently fighting.<br />
*'''Staffify''' - ''Level: 70'' - Lag: ---<br />
:An Archmage can create a magical [[staff]] by trapping their spells inside of a weapon. The level is based on the caster's level or the item's, whichever is lower. The weapon is consumed in the process, and has a single charge. The skill % in the spell you are trying to charge the staff with is a small factor in the creation process.<br />
<br />
==Spells==<br />
<br />
*'''Wind Blade''' - ''Level: 31'' - Lag: 10 - ''Mana: 64''<br />
:Wind Blade is a Tier 2 offensive spell and can be charged to deliver 1.25x the damage. It deals wind-type damage.<br />
:Wind Blade imposes 17% less lag than comparable spells.<br />
*'''Earthslide''' - ''Level: 32'' - Lag: 12 - ''Mana: 48''<br />
:Earthslide is a Tier 2 offensive spell and can be charged to deliver 1.25x the damage. It deals earth-type damage.<br />
:Earthslide costs 25% less mana than comparable spells.<br />
*'''Absolute Zero''' - ''Level: 33'' - Lag: 12 - ''Mana: 64''<br />
:Absolute Zero is a Tier 2 offensive spell and can be charged to deliver 1.25x the damage. It deals cold-type damage.<br />
:Absolute Zero has much more predictable damage than comparable spells.<br />
*'''Lava Wave''' - ''Level: 34'' - Lag: 12 - ''Mana: 64''<br />
:Lava Wave is a Tier 2 offensive spell and can be charged to deliver 1.25x the damage. It deals fire-type damage.<br />
:After its initial hit, Lava Wave inflicts a lingering burn amounting to 5% damage each pulse for three pulses.<br />
*'''Maneater''' - ''Level: 35'' - Lag: 12 - ''Mana: 64''<br />
:Maneater is a Tier 2 offensive spell and can be charged to deliver 1.25x the damage. It deals wood-type damage.<br />
:Maneater has a small chance to swallow the target whole, dealing ten times the damage and usually ending the fight instantly. This effect is much more likely to occur against small targets.<br />
*'''Void Ray''' - ''Level: 35'' - Lag: 12 - ''Mana: 64''<br />
:Void Ray is a Tier 2 offensive spell and can be charged to deliver 1.25x the damage. It deals dark-type damage.<br />
:Void Ray is weaker than comparable spells but deals double damage any time it is cast at least twice in a row, regardless of the target.<br />
*'''Thorn Aegis\Hailstone Barrier\Quartz Guard''' - ''Level: 38'' - Lag: 12 - ''Mana: 28''<br />
:The caster calls forth a shield that has -15AC and reflects back up to 1/4 of the damage taken by the owner.<br />
:Wood\Moon-Innate evolved wizards learn Thorn Aegis, which reflects as piercing damage.<br />
:Fire\Earth\None-Innate evolved wizards learn Quartz Guard, which reflects as slashing damage.<br />
:Water\Wind-Innate evolved wizards learn Hailstone Barrier, which reflects as bludgeoning damage.<br />
*'''Cure Osmose''' - ''Level: 43'' - Lag: 12 - ''Mana: 5''<br />
:Osmosis is a status effect that slowly depletes your mana. This spell will cure it.<br />
*'''Chrysalis''' - ''Level: 51'' - Lag: 8 - ''Mana: 40''<br />
:Chrysalis produces a shield that can take damage equal to the caster's maximum MP. Like manashield, the chrysalis takes 50% more damage than the caster would otherwise suffer.<br />
:Unlike manashield, damage to the chrysalis does not drain MP, but the caster cannot fight from within the chrysalis, and taking any action will cause the chrysalis to immediately shatter open.<br />
*'''Megamagic''' - ''Level: 60'' - Lag: 32 - ''Mana: SPECIAL''<br />
:This is a non-elemental attack spell. The damage done by the spell is equal to the wizard's max mana. However, if a wizard is not at full mana, then HP is taken to make up for the difference between current and max mana.<br />
*'''Reverse Polarity''' - ''Level: 65'' - Lag: 8 - ''Mana: 40''<br />
:After Reverse Polarity is cast, for all damage dealt by anyone in the room, most elements will have their damage type inverted, as per the table below. Both spells and elemental physical attacks are affected. Healing is unaffected.<br />
<br />
{| class="wikitable"<br />
!colspan="6"|Reverse Polarity<br />
|-<br />
|Fire<br />
|Cold<br />
|-<br />
|Energy<br />
|Water<br />
|-<br />
|Wind<br />
|Earth<br />
|-<br />
|Electricity<br />
|Iron<br />
|-<br />
|Wood<br />
|Dark<br />
|-<br />
|Poison<br />
|Light<br />
|}<br />
<br />
*'''Headology''' - ''Level: 80'' - Lag: 12 - ''Mana: 150''<br />
:A particularly clever Witch can convince a sentient enemy that they are, in fact, a newt. I'm quite sure you'll see this is true as well since they will become a tiny, slimy newt worth 0 EXP.<br />
:This spell has no cooldown.<br />
<br />
='''Elementalist'''=<br />
Elementalist is one of two classes a [[#Wizard|Wizard]] may evolve into at level 30.<br />
<br />
Mana is raw power, and few understand this primal rule as well as the Elementalists. They are able to impose their will on this power so forcefully that they can turn their attacks back into usable mana, cast more with less, and even instinctively retaliate with spells. While their focus is more narrow than others, the results of their dedication to the elemental powers of mana can not be argued with.<br />
<br />
<br />
==Skills==<br />
*'''Wildcasting''' - ''Level: 30'' - Lag: 10<br />
:Wildcasting is a skill that can be toggled. When active, it allows the user to continue casting spells if they don't have enough mana, even ZERO. However, casting without mana can lead to some random but detrimental side effects.<br />
:Additionally, wildcasting cuts spell lag based on the caster's remaining mana. A manaless caster enjoys a 75% cut in lag, while a caster with more than half mana remaining sees a negligible lag cut.<br />
*'''Feedback''' - ''Level: 40'' - Lag: 0 - ''Mana: 0''<br />
:Feedback is a passive skill that is always active once practiced above 1%. Whenever the user casts a spell, the user gains mana according to the amount of damage dealt. This is not limited by the user's maximum mana, which will temporarily increase to accomodate the gain from feedback, if needed.<br />
:Feedback includes overkill damage as well as damage affecting multiple targets, as long as the damage occurs from a single spell cast. <br />
:Although feedback has a long cooldown, feedback will partially activate even while on cooldown, as long as the user deals damage exceeding that of the previous feedback activation.<br />
:High skill converts a greater percentage of damage into mana.<br />
*'''Power Surge''' - ''Level: 55'' - Lag: --- - ''Mana: 0<nowiki>*</nowiki>''<br />
:Power Surge is a skill that can be toggled. While active, all cast spells will enjoy a 50% power boost(via increasing the level of the spell cast) but suffer a 20% increased failure rate.<br />
*'''Counterspell''' - ''Level: 70'' - Lag: 0 - ''Mana: 0<nowiki>*</nowiki>''<br />
:Counterspell is a skill that can be toggled. When active, it allows the user to immediately counterattack any offensive spell with any offensive spell of their choice. The counterspell induces no lag but costs twice the MP of a regular spell.<br />
:Counterspells do not consume a Wizard's Charge. The probability of counterspell activating is based on the user's skill percentage in counterspell.<br />
<br />
<br />
==Spells==<br />
*'''Thunderstorm''' - ''Level: 31'' - Lag: 12 - ''Mana: 64''<br />
:Thunderstorm is a Tier 2 offensive spell, and can be charged to deliver 1.5x the damage. It has a chance to confuse the target, causing them to randomly attack themselves. It does Electric-type damage. Non-Earth Innate Elementalists learn this.<br />
*'''Gyro Ball''' - ''Level: 32'' - Lag: 12 - ''Mana: 64''<br />
:Gyro Ball is a Tier 2 offensive spell, and can be charged to deliver 1.5x the damage. It has a chance to sprain the target, which reduces their movement points to zero. It deals Iron-type damage. Non-Moon Innate Elementalists learn this.<br />
*'''Bubblebeam''' - ''Level: 33'' - Lag: 12 - ''Mana: 64''<br />
:Bubblebeam is a Tier 2 offensive spell, and can be charged to deliver 1.5x the damage. It has a high chance to reduce its target's saves. It does Water-type damage. Non-Fire/None Innate Elementalists learn this.<br />
*'''Burst''' - ''Level: 34'' - Lag: 12 - ''Mana: 64''<br />
:Burst is a Tier 2 offensive spell, and can be charged to deliver 1.5x the damage. It also has a chance to burn the target, worsening their AC and damroll. It deals Energy-type damage. Non-Wood Innate Elementalists learn this.<br />
*'''Viro Plasm''' - ''Level: 35'' - Lag: 12 - ''Mana: 64''<br />
:Viro Plasm is a Tier 2 offensive spell, and can be charged to deliver 1.5x the normal damage. It also reduces the target's maximum HP, making the damage it deals difficult to heal. As a result, sometimes targets may appear healthier than they actually are. It does Poison-type damage. Non-Wind Innate Elementalists learn this.<br />
*'''Lucent Beam''' - ''Level: 36'' - Lag: 12 - ''Mana: 64''<br />
:Lucent Beam is a Tier 2 offensive spell, and can be charged to deliver 1.5x the normal damage. It also has a chance to daze the target, handicapping their skills briefly. It deals Light-type damage. Non-Water Innate Elementalists learn this.<br />
*'''Thorn Aegis\Hailstone Barrier\Quartz Guard''' - ''Level: 38'' - Lag: 12 - ''Mana: 28''<br />
:The caster calls forth a shield that has -15AC and reflects back up to 1/4 of the damage taken by the owner.<br />
:Wood\Moon-Innate evolved wizards learn Thorn Aegis, which reflects as piercing damage.<br />
:Fire\Earth\None-Innate evolved wizards learn Quartz Guard, which reflects as slashing damage.<br />
:Water\Wind-Innate evolved wizards learn Hailstone Barrier, which reflects as bludgeoning damage.<br />
*'''Cure Osmose''' - ''Level: 43'' - Lag: 12 - ''Mana: 5''<br />
:Osmosis is a status effect that slowly depletes your mana. This spell will cure it.<br />
*'''Cyclone''' - ''Level: 45'' - Lag: 24 - ''Mana: 150''<br />
:Cyclone is a Tier 3 offensive spell. It attacks the entire room, except the caster's group and can be charged to deliver 1.5x the damage. It causes Wind-type damage. Non-Earth Innate Elementalists learn this.<br />
*'''Magnitude''' - ''Level: 46'' - Lag: 24 - ''Mana: 150''<br />
:Magnitude is a Tier 3 offensive spell. It attacks the entire room, except the caster's group and can be charged to deliver 1.5x the damage. It causes Earth-type damage. Non-Moon Innate Elementalists learn this.<br />
*'''Snowy''' - ''Level: 47'' - Lag: 24 - ''Mana: 150''<br />
:Snowy is a Tier 3 offensive spell. It attacks the entire room, expect the caster's group and can be charged to deliver 1.5x the damage. It causes Cold-type damage. Non-Fire/None Innate Elementalists learn this.<br />
*'''Pyroclasm''' - ''Level: 48'' - Lag: 24 - ''Mana: 150''<br />
:Pyroclasm is a Tier 3 offensive spell. It attacks the entire room, except the caster's group and can be charged to deliver 1.5x the damage. It causes Fire-type damage. Non-Wood Innate Elementalists learn this.<br />
*'''Petal Burst''' - ''Level: 49'' - Lag: 24 - ''Mana: 150''<br />
:Petal burst is a Tier 3 offensive spell. It attacks the entire room, except the caster's group and can be charged to deliver 1.5x the damage. It causes Wood-type damage. Non-Wind Innate Elementalists learn this.<br />
*'''Nebula''' - ''Level: 50'' - Lag: 24 - ''Mana: 150''<br />
:Nebula is a Tier 3 offensive spell. It attacks the entire room, except the caster's group and can be charged to deliver 1.5x the damage. It causes Dark-type damage. Non-Water Innate Elementalists learn this.<br />
*'''Calm''' - ''Level: 51'' - Lag: 12 - ''Mana: 200''<br />
:Peaceful thoughts and good vibrations flow through the air when the Calm spell is cast. All enemies in the room are overcome with an overpowering mellowness, breaking up any current fights. For a brief period afterwards, the targets will suffer reduced damroll and be unable to initiate combat.<br />
:Fights with more participants are harder to stop. Calm can be charged to increase its likelihood of success.<br />
*'''Megamagic''' - ''Level: 60'' - Lag: 32 - ''Mana: 0<nowiki>*</nowiki>''<br />
:This is a non-elemental attack spell. The damage done by the spell is equal to the wizard's max mana. However, if a wizard is not at full mana, then HP is taken to make up for the difference between current and max mana.<br />
*'''Wall Change''' - ''Level: 65'' - Lag: 16 - ''Mana: 50''<br />
:An expert Elementalist can alter the elemental strengths and weaknesses of himself or others. Casting Wall Change imbues a target with the major and minor elemental resistances of a random innate, as well as the corresponding vulnerabilities.<br />
:Successive castings of the spell will randomly assign new resistances and vulnerabilities. Wall Change can be used on both allies and enemies. When charged, the effects from this spell last twice as long.<br />
*'''Headology''' - ''Level: 80'' - Lag: 12 - ''Mana: 150''<br />
:A particularly clever Witch can convince a sentient enemy that they are, in fact, a newt. I'm quite sure you'll see this is true as well since they will become a tiny, slimy newt worth 0 EXP.<br />
:This spell has no cooldown.<br />
<br />
<br />
<br />
---<br />
<br />
='''Wizard Innate Spell Chart'''=<br />
<br />
{| border="1"<br />
|+ Wizard Spells By Innate<br />
|- <br />
! Innate<br />
! Damage Type<br />
! Tier 1<br />
! Tier 2<br />
! AoE<br />
|-<br />
| EARTH || Earth <br> Iron || Gem Missile <br> --- || Earthslide <br> Gyro Ball || Magnitude <br> ---<br />
|-<br />
| WIND || Wind <br> Electricity || Air Blast <br> --- || --- <br> Thunderstorm || Cyclone <br> ---<br />
|-<br />
| WOOD || Wood <br> Poison || Rhizome Lance <br> --- || --- <br> Viro Plasm || Petal Burst <br> ---<br />
|-<br />
| FIRE || Fire <br> Energy || Fireball <br> --- || Lava Wave <br> Burst || Pyroclasm <br> ---<br />
|-<br />
| WATER || Water <br> Ice || --- <br> Ice Smash || Bubblebeam <br> --- || Surf <br> ---<br />
|-<br />
| MOON || Light <br> Dark || --- <br> Darkside || Lucent Beam <br> --- || ''Halo'' <br> Nebula<br />
|}<br />
<br />
*Italicized spells are not learned naturally.<br />
<br />
{{Classes}}<br />
<br />
[[Category:Classes]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Building_Guide&diff=4299Building Guide2021-06-01T01:04:02Z<p>Pascal: added shopkeeper info to medit section</p>
<hr />
<div>*''This guide is adapted from [http://web.archive.org/web/20020402164025/http://www.geocities.com/TimesSquare/Dome/4876/ OLC: Down and Dirty in the Mud] (original Geocities site offline) by Kara Ann''<br />
<br />
OLC is short for On-Line Creation. It is your friend.<br />
<br />
OLC is a set of code added to a MUD that allows builders to edit area files in real-time while logged into the MUD, instead of the old method of manually editing text files and rebooting the game every time a change is to be implemented.<br />
<br />
There are many different versions of OLC in use on different MUDs, although the syntax and usage is fairly standard. Becoming familiar with OLC will let you be an asset as a builder on almost any MUD. This guide is written explicitly for the Cleft of Dimensions, however.<br />
<br />
==Basics==<br />
===Vnums===<br />
'VNUM' is short for 'virtual number'. One vnum can be assigned to a mobile, an object, a room, AND a [[Mprog Compendium|mob program]] (or mprog)<br />
<br />
Each mobile and object has a virtual number, which is used to store the index data or template that is used to create each instance of that mobile or object.<br />
<br />
For example:<br />
* Object vnum 1050 contains data for a pair of purple pants. Every pair of purple pants in the game shares this vnum, but object vnum 1050 is only used for purple pants.<br />
* Mobile vnum 1050 contains data for Green Imps. Every Green Imp in the game uses shares this vnum, and mobile vnum 1050 is only used by Green Imps.<br />
* Room vnum 1050 contains data for a section of road in Truce Canyon. There is only one room with this vnum, and any references to room vnum 1050 are thus references to this specific section of road.<br />
* Mob program vnum 1050 contains a greet program for the Imp King. Only one mobprog is number 1050, and any references to mobprog 1050 are to this one, although one prog can be used by several mobs.<br />
<br />
===Building Modes===<br />
These are modes in which builders can edit certain things. <br />
* REDIT - room edit, rooms are created, linked, and edited, and resets are made within this mode<br />
* OEDIT - object edit, objects are created and edited within this mode<br />
* MEDIT - mobile edit, mobs are created and edited within this mode<br />
* MPEDIT - mobprogram edit, mob programs are created and edited within this mode (reserved for builders above level 101)<br />
* AEDIT - area edit, area files are created and edited within this mode (generally reserved for the head builder)<br />
* HEDIT - help edit, creates and modifies help files (reserved for high-level staff)<br />
Commands are limited between modes, IE you can only do certain things in a given mode. For a list of commands specific to each mode, enter one and type '''commands'''.<br />
<br />
You can switch from one mode to another any time. To exit a mode, type '''done'''.<br />
<br />
===Saving your Work===<br />
It is vitally important to save completed work often. If the game crashes or is rebooted without saving, any work done will be lost forever. To save your work, type '''asave changed''' frequently. This works in all edit modes and will save everything that has been changed or created.<br />
<br />
===Names===<br />
Object and mobile names function as keywords for targeting those objects and mobiles. Any words within the name will work to target the object or mobile. Adding too many names to an object or mobile increases the chance of ambiguity when attempting to interact with it.<br />
<br />
A mobile or object's name consists of several words, separated by spaces. Words can also be enclosed in double quotes, if necessary. If a mobile's name is 'green imp' then both 'look green' and 'look imp' will function correctly. If the mobile's name is 'a green imp' then 'look a' will also target the imp, which is not desired behavior. If a mobile's name is '"green imp"' with both words enclosed by double quotes, then 'look green' will work while 'look imp' will not, but 'look "green imp"' will!<br />
<br />
If the long description doesn't contain the same words as the short description, it's good form to add extra words to the name. For example, the Chain Chomp's short desc is "a Chain Chomp", while its long desc is "A round black beast tied to a chain is chomping away at you as close as it can get." Since a player may not know from the long desc that it is a chain chomp, they will probably type 'look beast' to find out more about it. Because of this, the mob's name string is 'chain chomp beast' so that all these words function correctly.<br />
<br />
===Short Descriptions===<br />
A short description is the text displayed when an object or mobile is being interacted with, such as 'a red apple' or 'the noxious Grimer'.<br />
<br />
Short descriptions should either be a proper noun or begin with an article. (a/an/the/some/etc)<br />
<br />
===Long Descriptions===<br />
A long description is the text displayed when an object or mobile is seen in a room, such as 'The enterprising Hassan is here, waiting to make a sale.' <br />
<br />
Note that long descs are not the same as a mobile's 'description'.<br />
<br />
==REDIT==<br />
Redit is the mode used to create and change rooms and exits between rooms. <br />
<br />
To enter Redit mode, you can type '''redit''' by itself, but only if you are in an area that you have permission to modify.<br />
<br />
To see all the rooms in an area and their vnums, type '''rlist'''. To see details about the room you're working on, type '''show''' or just enter a blank line.<br />
<br />
===Creating New Rooms===<br />
To create a room from scratch, you '''redit create (new room vnum)''', which will create an empty room with no exits, and simultaneously move you into it.<br />
<br />
You can also simultaneously create a new room and a two-way exit to it by typing '''(direction) dig (new room vnum)''', where the direction is which way from the current room to link it.<br />
<br />
A brand-new room will have no name, no description, and no special properties.<br />
<br />
===Linking Existing Rooms===<br />
Rooms can have two-way and one-way [[exits]]. <br />
<br />
To create a two-way exit from a room, type '''(direction) link (other room)''', where direction is which way the exit will be in this room. Two-way exits are always linked opposite of each other E.G. if Room A has a two-way exit West to Room B, then Room B will have an exit East to Room A. A door on one side of a two-way exit will let people on the other side know that it has been opened.<br />
<br />
To create a one-way exit from a room, type '''(direction) room (other room)'''. One-way exits don't do anything to the room on the other side, so be careful not to create dead-ends when using one-way exits.<br />
<br />
When linking rooms from different areas make sure that both areas are edited and saved. The link will not save if you only asave changed.<br />
<br />
====Deleting Exits====<br />
Rooms cannot be deleted, but exits can. To delete an exit, type '''(direction) delete'''. Deleting a two-way exit removes both sides.<br />
Note that if you delete a one-way exit that leads to a room where the "returning" exit is different, both exits would be deleted.<br />
<br />
===Describing Rooms===<br />
To set the name of a room, go to the room to name and type '''name (name)'''. <br />
<br />
A room's Name is the line of text that players see at the top of the description when they see a room or type 'exits', and the part a builder sees when typing 'rlist'. It's standard procedure in this MUD to include the area name in the room title. Normal formats are 'Area Name - Room Name' and 'Room Name, Area Name', colored however you wish.<br />
<br />
To edit a room's description, enter the room to be described and just type '''description'''. This enters the description editor, which is identical to the normal note and player desc editor. Type .h if you need help using the editor.<br />
<br />
A room's description is the block of text that players see when they look at a room, describing its contents and atmosphere. Room descs can be colored, but they should all be one solid color for readability. <br />
<br />
====Description Style Tips====<br />
Keeping descriptions to a decent length is important, since players will often avoid reading anything that shows up as one giant wall of words. Five or six lines is usually plenty. If you want to elaborate more on something in the room, you can use an extra desc (see below).<br />
<br />
Colors are available to help set a mood, but be aware that some colors (particularly blue and dark blue) are difficult to read on a black background. Descriptions can be colored, but should be one solid color for readability unless highlighting specific words.<br />
<br />
Descs should stay objective in tone, avoiding references to the reader. "The monster terrifies you." is inapplicable if the player is a robot incapable of fear or a hardy warrior who's seen worse. That said, sometimes it's more fun to write them subjectively; be creative!<br />
<br />
====Extra Descriptions====<br />
Extra Descriptions are additional descriptions a room can have for curious players who try to look at things mentioned in the main description. IE If a room description mentions that there is a painting on the wall, you could describe the painting in depth using an extra desc for the word 'painting' to avoid cluttering the main room desc.<br />
<br />
If there is an item or mob in the room with the same name as an extra desc, then the player will see that item or mob instead of the extra desc.<br />
<br />
To add an extra desc to a room, type '''ed add (keywords)'''. You can add one desc for multiple keywords at once if you enclose them in double quotes. To edit an existing extra desc, type '''ed edit (keyword)'''. To delete an extra desc, type '''ed delete (keyword)'''.<br />
<br />
Extra descs can be any length, can contain asciiart, break the fourth wall, and ignore all sorts of other description conventions for the sake of an interesting experience. It's good form to add extra descs in every room you can, but it's not strictly necessary.<br />
<br />
===Changing Room Properties===<br />
To toggle a room flag, type '''room (flag name)'''. Most room properties exist as flags, which can all be toggled on and off individually. All flags are off in a new room. For a list of room flags and their functions, see [[Flags_Compendium#ROOM_FLAGS]].<br />
<br />
To change a room's sector, type '''sector (sector name)'''. A sector has information about the general biome or type of room. A room can only have one sector, and it is set to 'inside' by default. For a list of sectors and their functions, see [[Flags_Compendium#SECTOR]].<br />
<br />
To change a room's mana or health regeneration rates, type '''heal (percent)''' or '''mana (percent)'''. These numbers are percentages that regeneration rates are modified by EG 'mana 200' will double MP regeneration for players and monsters alike in the room. Note that setting a negative number won't cause damage, but will floor regeneration rates to their absolute minimum.<br />
<br />
Rooms can also have specific positions on the weather grid and extra weather modifiers. These are usually set at for the whole area instead of for specific rooms. A room's weather modifiers will override the ones set for the area. Avoid very high weather modifiers unless absolutely necessary (You're in a tornado!). We want the weather modifying spells to be more useful..<br />
To set a room's coordinates, type "xarea #" or "yarea #".<br />
<br />
===Changing Exit Properties===<br />
To toggle an exit flag, type '''(direction) (flag name)'''. For a list of exit flags and their functions, see [[Flags_Compendium#EXITS]]. Note that for 'closed', 'locked', etc to work, 'door' must be on. If 'door' is on but 'closed' is not, then the door will open itself when the area is reset and players will likely not even notice it. Applying a flag to one side of a two-way exit will automatically apply it to the other side as well.<br />
<br />
If a door is locked, you can specify what item a player needs to unlock it by typing '''(direction) key (obj vnum)'''. The player will only need to have the object in their inventory to be able to unlock the door.<br />
<br />
====Exit Names and Descs====<br />
Doors can also have special names and descriptions. These can help immerse the player in the area they're exploring.<br />
<br />
To set an exit's keywords, type '''(direction) name "(names)"''' Note that the double quotes are required. This will allow players to use these names when trying to open or close the door EG 'east name gate' will allow players to type 'open gate' in addition to 'open east' to open the door, as well as allowing them to 'enter gate' in addition to just typing 'east'. Once you've given an exit a special name, you can make the exit hidden and mention 'There is a gate to the east.' in the room's description to reward players that read descs thoroughly. You can use '(direction) name none' to remove all names.<br />
<br />
To set an exit's description, type '''(direction) desc "(desc)"''' Note that the double quotes are required. A door's description string is cosmetic, and will be shown to people manipulating the door EG 'east desc "the imposing iron gate"' will show players 'You open the imposing iron gate'/'Soandso opens the imposing iron gate', etc. You can use '(direction) desc none' to remove anything and revert the exit to using the default text 'the door'.<br />
<br />
==MEDIT==<br />
<br />
Medit is the mode used to create and edit mobs, or mobiles, AKA NPCs. A mob is any fightable or unfightable monster, shopkeeper, quest NPC, townsperson, boss, etc. Mobs can also be made completely invisible to players in order to create special events or puzzles.<br />
<br />
To see all the mobs in the area you're in, type '''mlist'''. You can see only mobs with a certain name with '''mlist (name)'''.<br />
<br />
To see details about the mob you're currently working on, type '''show''' or just enter a blank line.<br />
<br />
===Creating and Editing Mobs===<br />
To enter Medit mode, you must type either '''medit create (empty mobile vnum)''' or '''medit (existing mobile vnum)''' If you try to create a mob in a vnum that already exists, or edit a mob that doesn't already exist, you will receive an error and not enter medit mode. <br />
<br />
A newly created mobile is mostly blank and has no name, description, or attributes.<br />
<br />
===Describing Mobs===<br />
To set the name of a mob, type '''name (mobile names)'''. This is not the same as the mobile's short description, and the names are never seen by the player all at once.<br />
<br />
To set the short description of a mob, type '''short (short description)'''. This is the what the player sees when interacting with the mobile.<br />
<br />
To set the mob's long description, type '''long (long description)'''. This is the line of text that the player sees when looking at a room with this mob in it.<br />
<br />
To create or change a mob's description, type '''desc'''. This enters the string editor, and if the mob already has a desc it will be loaded into the editor. When you are finished editing the description, type '''@''' to exit the editor. A mob's description is what a player sees when looking at the mob. A mob without a description only shows the player 'You see nothing special about (him/her/it).'<br />
<br />
===Setting Mob Stats===<br />
Mobs have a variety of statistics. They can all be changed from within Medit mode.<br />
<br />
A mob's race can be set with '''race (race name)'''. To see a list of all PC and NPC races in the game, type '''race ?'''. A mob's race pre-sets act, form, part, imm, res, and vuln flags. Changing an existing mob's race will add new flags but won't remove existing ones. A mob's race doesn't affect many things on its own, though.<br />
<br />
Mobiles have lots of other stats that can be set.<br />
<br />
;sex (male/female/neutral/random)<br />
:The mob's gender; modifies pronouns when interacting with the mob. A mob set to be Random sex will be randomly male or female each time it is loaded.<br />
;level (#)<br />
:The level of the mob. Note that a mob's armor values will need to be modified accordingly with the mob's level.<br />
;align (#)<br />
:While players can only range from -1000 to 1000, mobs can have outrageous alignment values. Despite this, -1000 to 1000 is normal.<br />
;hitroll (#)<br />
:This is a bonus or penalty to hitroll for this mob. This usually isn't necessary to change.<br />
;damtype (damage type)<br />
:This is the damage noun and thus damage type that the mob uses for unarmed attacks. Type '''? weapon''' for a list.<br />
;hitdice (XdY + Z)<br />
:Must be entered with the '''d''' and '''+'''. A mobile will have a randomly-rolled amount of hit points when loaded. A mobile's hit points should not vary too widely to prevent very easy/difficult to defeat outliers.<br />
;manadice (XdY + Z)<br />
:Mobiles have mana, but will not use it unless explicitly told to by an mobprog. This number is rolled when a mobile is loaded, like hit dice.<br />
;damdice (XdY + Z)<br />
:The first two numbers determine how much damage a mobile will do with unarmed attacks. If the mob is wielding a proper weapon, it will do damage based on the weapon instead. The third number is the mob's damroll. This bonus will apply whether the mob has a weapon or not!<br />
;armor (# # # #)<br />
:The AC scores of the mobile. The actual amount of damage prevented depends on the level of the mobile as well. All four values must be entered to set all four armor scores for the mobile.<br />
;size (size)<br />
:Type '''? size''' for a list of valid sizes. This stat mostly affects combat skills like bash and trip.<br />
;wealth (#)<br />
:The amount of wealth, in silver, that this mob carries. This number is not exact, so a mob will have a random amount of money when actually loaded, somewhere near this variable. If the wealth value is high enough, at least some portion of the mob's money will be in gold coins.<br />
<br />
When setting stats on a mob, use the Formulator application to determine how much HP, armor, etc it should have based on its level. Talk to another staff member for information on how to download this application.<br />
<br />
===Mobile Special Properties===<br />
<br />
In addition to their descriptions and stats, mobs can have a variety of special flags that change how they act.<br />
<br />
To toggle a mob's Act flags, type '''act (flags to toggle)''' A mob's act2, affect, shield, form, part, imm, res, vuln, offensive, and behavior flags are changed in the same way. <br />
<br />
For a list of all applicable mob flags, see [[Flags_Compendium#MOB_FLAGS]], or type '''? (flag name)''' while in medit mode.<br />
<br />
===Shopkeepers===<br />
<br />
To make a mobile a shopkeeper, use the syntax "shop assign" while editing the desired mobile. Typing just "shop" while in MEdit will display possible shopkeeper-related commands.<br />
<br />
Shopkeepers can have mobprogs like regular mobs with the exception of give progs, always giving an error that the player must sell the item instead. <br />
<br />
==OEDIT==<br />
===Basics===<br />
<br />
Oedit is the mode to edit objects, which includes fountains, apples, swords, basically anything that can't move around or perform actions on its own. Though note that there are cases where you may want a certain thing like a computer to be an object vs. a mob. Mobs can react to people interacting with them, objects cannot.<br />
<br />
Like the other modes, you need to either '''oedit create (vnum)''' or '''oedit (vnum)''' depending on whether it already exists or not. A new object will be basically blank and featureless. You can check its status at any time that you're in oedit mode by typing '''show'''.<br />
<br />
===Descriptions===<br />
<br />
There are three main descriptions that an item needs:<br />
<br />
'''Name''' - These are the keywords that the player uses to identify the item. They'll never actually *see* this (so no need for colors), but you want it to include the relevant keywords from it's short and long descs. Depending on what item it is, you may want to add certain hidden names in order to sort them for later searching. Typically for weapons this is +wtype, like +sslash, and for armor it's =slot, like =legs. (Later you can take advantage of these along with vnum to search for a certain slot, or in an mprog to remove whatever's on the legs, as long as it's been properly tagged)<br />
<br />
Example: name silver sword excalibur +sslash<br />
<br />
'''Short''' - This is the word that shows up directly for the object, such as when the player picks it up or has it equipped. This should not be very long, and including 'a', 'an', or 'the' is appropriate unless it has an actual proper name, as the player should ideally see 'You get '''an apple'''' rather than 'You get '''apple''''. This is also where color is most likely to be used.<br />
<br />
Example: short {WExcalibur{x<br />
<br />
'''Long''' - This description is what will be seen when the item is sitting on the ground in a room. Keep in mind both where it comes from and the fact that players could potentially later drop the items in different places entirely. This is also what will normally show up for the description of the item (see below).<br />
<br />
Example: long A silver sword has been stuck in the ground.<br />
<br />
There's also extra descriptions. As mentioned, the long description is the default, but that's generally not good enough for a real item. In order to attach a longer description, exdescs must be utilized. These can be done with '''ed add "<keywords>"''', '''ed edit "<keywords>"''', and '''ed delete "<keywords>"'''. Remember the quotes there or else it will only take the first word that you specify. Once you do ed add, an editor window will pop up, similar to personal or mob descriptions. Just put your text in there. Make sure that you include all the same keywords that are in the name (though any hidden ones are generally unnecessary).<br />
<br />
Example: <br />
ed add "silver sword excalibur"<br />
<br />
.c<br />
<br />
This shining sword looks like the weapon of a true king! It glows with soft light from within.<br />
<br />
.f<br />
<br />
@<br />
<br />
If an object has a keyword set as one of its names, but no extra desc for that keyword, then the object's long desc will be used instead. For example:<br />
*name: silver sword runes<br />
*short: a silver sword with runes<br />
*long: Covered with runes, a silver sword has been left here.<br />
*extra desc with keyword 'runes': These runes are in a long forgotten language.<br />
*"look sword"/"look silver": "Covered with runes, a silver sword has been left here."<br />
*"look runes": "These runes are in a long forgotten language."<br />
<br />
===Stats===<br />
<br />
'''Type''' - One very important part of any object is it's type. This determines what other flags it has - weapons will have flags to determine what type of damage it does and how hard it hits, pills will have flags for what spells they cast, trash is trash, etc. For a full list of these, check the [[Flags_Compendium/Obj_Types]]. Once a type is selected, new flags v0 - v4 show up and will need to be selected.<br />
<br />
'''Level''' - The level that is required to use this item. Keep in mind that items will poof if the player is too underleveled and the remortable flag is not on the item.<br />
<br />
'''Wear''' - The wear flags determine if the item can be worn and where. Most important of these is '''take'''! If you don't flag the item as wear take, it will not be able to be picked up at all. This also means you can make strange cases, like wearing a weapon on your face or a rod on your wrist. Note that the arms, waist, and shoulders slots are typically not used in our MUD, so do not use those unless you have an good reason and have checked with someone else.<br />
<br />
'''Extra''', '''Extra2''' - These two flags hold various important utilities that do a variety of things. Refer to the [[Flags Compendium]] for full information.<br />
<br />
'''Weight''' - How heavy the item is. 10 here means 1 pound.<br />
<br />
'''Cost''' - How much the object is worth, in silver. Keep in mind that this is just the base, and shopkeeper settings mean they'd buy the item for 60% of it's real cost, etc.<br />
<br />
===Enchantments===<br />
<br />
One last trick that you might need to know is how to put affects and applys on items. These are the 'enchantments', the stuff like dex+2 or permanent quartz guard that goes on an item you wear.<br />
<br />
They are split into two categories:<br />
<br />
'''Addaffect''' - This is used for purely stat boosts. There's a lot of options here, but you don't really want to touch anything other than the primary stats (str, dex, etc), mana, hp, move, saves, ac, hitroll and damroll. The rest you really don't want to be messing with on items. The syntax is '''addaffect <type> <amount>'''. Remember that if you're doing this with AC, good AC is negative, not positive.<br />
<br />
Example: addaffect str 2<br />
<br />
'''Addapply''' - Addapply does the stuff that's not just stats but effects. The syntax for this is really strange - by definition an addapply must also *include* an addaffect, but it can be of type 'none'. The flags that can be added include affects, object, immune/resist/vuln, weapon, and shield flags (For a full list of these refer to mob flag information). Once added these show up on the object show as just addaffects w/out the associated real effect, so you may have to load a copy of the object and identify it to make sure it's working right.<br />
<br />
Here are a few examples:<br />
<br />
'''addapply vuln str 1 bash''' - This gives +1 strength but weakness to bashing damage.<br />
<br />
'''addapply affects none 0 slow''' - This causes a permanent slow state, with no other effects.<br />
<br />
'''addapply shield mana 20 confused''' - This causes the player to gain 20 max mana but be constantly confused.<br />
<br />
To remove an affect or apply, just use delaffect #, where the # is the right one from typing '''show''' in oedit mode.<br />
<br />
That's basically it - items are fairly straightforward!<br />
<br />
==MPEDIT==<br />
See [[Mprog Compendium]]. And then ask someone to show you what to do because mprogs can get confusing fast.<br />
<br />
==AEDIT==<br />
Aedit is the mode used to create and modify area files, their vnum ranges, and certain area-wide flags and settings.<br />
<br />
Typing 'aedit' in any room will begin editing the area that room is in, assuming you have appropriate permission. Aedit is currently a level 105 (advanced builder) command.<br />
<br />
===Creating a New Area===<br />
To create a new area, enter aedit from any existing area and type 'create'. This makes a new area with no vnums assigned and gives it the filename area0.are. ''Areas cannot be deleted from within OLC, so do not use this command for no reason.''<br />
<br />
Several fields need to be set right away: use 'filename <foo.are>' to change the filename of the area, which should be short (8 characters, lowercase) but clearly indicate the name of the area. Consult with the head builder or higher immortal for further guidance.<br />
<br />
Next, the base vnum range needs to be set to a block of free vnums. This can be done with either the 'vnum (lower) (upper)' command, or separately with 'lvnum (lower)' and 'uvnum (upper)' commands. OLC will not let you use vnums that are already part of a different area. Convention in the Cleft of Dimensions is to create new areas with contiguous vnums, so consult with the head builder or higher immortal to figure out the next highest block, or use 'alist' to figure it out yourself!<br />
* An area can contain rooms from outside its vnum range, relocated with the 'areaoverride (filename)' Redit command. Use this sparingly, as it was mostly designed for expanding old areas which were created with insufficient vnum space!<br />
<br />
Make sure to give the area a name, using the 'name (name)' command. Note that this name can be displayed to players at various points.<br />
<br />
Finally, fill out the credits field for the area; this is what shows up in the 'areas' command, and unintuitively does not contain the builder credits for the area. It takes the form of '''{c[{Y Area Name {wLw-Up {c]{x'''<br />
<br />
===Security and Builders===<br />
Areas can only be modified by specified people. Access can be tweaked by changing the area's Security and Builders.<br />
<br />
'Security (number)' will restrict editing of the level to immortals with security equal or higher to the given number.<br />
<br />
'Builders (name/all)' will toggle a given immortal's name, allowing that builder to override the security setting for the area. This is usually done to assign new builders to their probational area without allowing them edit access to anywhere else.<br />
<br />
===Weather, Location and Level Range===<br />
Regardless of what [[weather]] system is over the area's X/Y coordinates, the weather can be adjusted area-wide with the 'skymod (number)' and 'wndmod (number)' commands, which range from 4 to -4. <br />
*These can also be set per room.<br />
<br />
The area's X/Y coordinates can be set with the 'xpos (number)' and 'ypos (number)' commands. This determines the area's place on the weather map as well as the atlas.<br />
*These can also be set per room.<br />
<br />
The area's level range is used to show players the area when appropriate in response to an 'areas' command with no arguments. This should be set appropriately for the mobs and objects in the area.<br />
<br />
===Flags===<br />
Areas have two types of flags: area flags, and exflags. Exflags can be set by a builder by using 'exflags (flag)', and have various practical effects on the area for players. The list is at [[Flags_Compendium#AREA_EXFLAGS]]<br />
<br />
The other kind of Area flags are for temporary weather up/down affects (caused by the Stormy Sky and Clear Sky affects) and other things about the loading/saving of area files:<br />
* Changed: Area has changed and will be written to disk at the next 'asave changed'.<br />
* Added: Area is new and will be written to disk for the first time at the next 'asave changed'.<br />
* Loading: Used for counting in db.c<br />
* Weather Up: Area is affected by Stormy Sky and has a temporary additional +1 to Wind modifier and Sky modifier.<br />
* Weather Down: Area is affected by Clear Sky and has a temporary additional -1 to Wind modifier and Sky modifier.<br />
<br />
===Other Commands===<br />
'age (number)' overrides an area's current age (in minutes) for the purpose of reset timing.<br />
<br />
'automap' does nothing useful or interesting, and is probably a vestigal remnant of some planned function.<br />
<br />
'commands' shows all the valid aedit commands.<br />
<br />
'reset' forces an immediate reset of the entire area's objects and mobs.<br />
<br />
'show' is the same as a blank line in Aedit mode, and shows information about the area being edited.<br />
<br />
'? (field)' shows available flags in a given field, like other OLC editors.<br />
<br />
'version' shows OLC credits.<br />
<br />
==HEDIT==<br />
===Editing General Help Files===<br />
For an existing help file you can just type '''hedit <keyword>''' to open that file. It has the keywords, the level to view the file (101 for immortal-only helpfiles, otherwise 0 generally), and the text itself.<br />
<br />
To create a new helpfile, start with '''hedit hedit''' to open a helpfile in general, then type '''new help.are keyword''' - help.are can also be olc.are or somewhere else, this is mainly for organizational purposes. In general, to ensure helpfiles get saved, it is best to edit an area in some minor way (add and remove a safe room flag, for instance) and asave changed to have both save at the same time.<br />
<br />
===Editing Maps===<br />
Maps are slightly trickier. When designing a map, it should be 60x24 characters. You also want to put it in maps.are, again for organizational purposes. Maps should be named area.are000 and incrementing. Examples: '''truce.are000''', '''saturnv.are001'''<br />
<br />
Whichever map is 000 will be set as the default local map for that area (provided it matches the name exactly! you should be using your area name exactly as it is in game). To make an individual room use a different map, redit that room and '''localmap newmap.are00x'''. These maps should all be at security level 101 - players will be able to see them as maps but not by typing 'help'.<br />
<br />
ProTuna also has built-in functionality to highlight the area where the player is on the map, but this must be manually set. To do this, type '''xlocal 1''' and '''ylocal 1''' where 1,1 is the top left character of your map. These must be set individually for each room.<br />
<br />
===Editing Quest Lists===<br />
Each area also has a corresponding quest list to be stored as: '''areaname.are.quests''' (like truce.are.quests). These are basically just text, except you can use the string '''^areaname1''' to show whether that questflag has been obtained or not. You can also hide quests until they are completed by prefacing them with two ^ i.e. '''^^areaname2'''. These hidden quests will not show up as blank lines but are entirely undetectable. See any other quests lists for examples.<br />
<br />
==SEDIT==<br />
coming soon<br />
<br />
Avoid making new socials simply for entertainment purposes, as this will add more clutter to the socials list, which is utilized by players to maneuver through rooms, puzzles or quests at times. Existing social commands are for the most part set in stone. Changing existing output can cause quests to fail activation. If a condition arises where the syntax should indeed be changed, an admin should run a find and replace for relevant mprog triggers.<br />
<br />
==GEDIT==<br />
coming soon<br />
<br />
Edits clans: will probably change dramatically in the future as clan code is changed.</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=4289Mprog Compendium2021-05-27T13:11:51Z<p>Pascal: added troubleshooting at the bottom</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===Optimizing Mobprogs===<br />
Mobprogs are the biggest use of CPU time for the Cleft of Dimensions. Because of this, builders are encouraged to design and write progs with efficiency in mind. Below are some guidelines to follow:<br />
<br />
* Random progs attempt to execute on every game tick. Because of this, they should be small and efficient.<br />
** It is vastly more efficient to give a mob a 'random 50' prog, than a 'random 100' prog that begins with 'if rand 50'.<br />
*** The same is true of any prog trigger with a percentile parameter!<br />
** A 'schedule all' prog will only attempt to execute every minute instead, if that's acceptable.<br />
** A delay prog that re-sets the acting mob's delay, can also be used instead of a random prog, as long as the initial delay amount is set by a spawn prog or some other method.<br />
<br />
* The 'break' command will end prog execution immediately.<br />
** In a vnum-stacked prog, put the most frequent users first, and end those blocks with a 'break'. Without a break, the rest of the prog will still be parsed!!<br />
<br />
* "Vnum Stacking" is a method of using one mprog vnum on multiple mobs by making blocks of code within 'if vnum $i == ####' checks.<br />
** This can conserve vnums within an area, but in exchange makes each vnum-stacked prog less efficient to process.<br />
** Avoid vnum stacking random progs, or other progs that are called frequently, like delay or schedule.<br />
<br />
* The 'mobexists' and 'objexists' ifchecks with words are the least efficient in the entire mobprog language, despite efforts to speed them up.<br />
** This is because they must compare their input string to every single name component of every single mob/obj in the entire world.<br />
** Both of these ifchecks can be used with a vnum instead. This is ''MUCH, MUCH'' faster, because it doesn't actually count anything; mob and object index data keep track of what's been loaded and unloaded!<br />
** This doesn't mean these ifchecks are off limits! Just avoid using them on progs that run frequently.<br />
<br />
* Update_always mobs will execute all their progs even when a player is not in the area.<br />
** However, when a player leaves an area, it stays active for several minutes anyway.<br />
** Areas are also active for several minutes when the game first boots up.<br />
** Because of this, you probably don't need update_always on your mob unless it's running schedule progs.<br />
** Update_always and random progs are a bad mix that I will scold you for.<br />
<br />
* Schedule, delay, and random progs WILL NOT execute if the mobile is fighting, UNLESS the mob is also flagged as update_always<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere '''This check is for use with variables, not names'''<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists 1233 - is there mob vnum 1233 somewhere<br />
if mobexists fido - is there a fido mob somewhere '''!!! WARNING !!!''' this is cpu-intensive. use a vnum instead if possible!<br />
if mobexists 5.2839 - are there at least 5 mobs of vnum 2839 anywhere<br />
objexists if objexists 1233 - is there obj vnum 1233 somewhere<br />
if objexists sword - is there a sword obj somewhere '''!!! WARNING !!!''' avoid this too, for the same reasons<br />
if objexists 500.sword - are there at least 500 swords in the entire world? '''!!!''' and this<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
area if area $i == 1 - is $i in the immortal area?<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khcount if khcount $n > 30 - did $n kill more than 30 things?<br />
khexists if khexists $n 1234 - did $n kill a mob of vnum 1234? <br />
enchant if enchant $o > 10 - does $o have a total enchantment modifier of more than 10? NOTE: armor enchants are negative<br />
recentdam if recentdam $i > 4 - is my recent_dam variable (aka $a) greater than 4?<br />
localx if localx = 3 - is the current room at the localx 3 position?<br />
localy if localy = 10 - is the current room at the localy 10 position? Note that these are the variables for the protuna minimap, and they'll be zero in every room if the builder hasn't created a map and set them<br />
<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I have either haste or slow, and I definitely have zombie!<br />
else<br />
say I might have any one of haste, slow, or zombie, I might have haste AND slow without zombie...<br />
say Or I might just have none of the above!<br />
endif<br />
<br />
if carries $i apple<br />
and carries $i sword<br />
or carries $i dagger<br />
say I have an apple for sure, and either a sword or a dagger!<br />
else<br />
say I have neither an apple and a sword, nor an apple and a dagger.<br />
say But I might have an apple and no weapon, or both weapons... or nothing!<br />
endif<br />
<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$c the current combat target of the remember target<br />
$d random player-targetable entity<br />
$D random charmie or pet<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$h random player or charmie or pet<br />
$i the acting mob itself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$u the mob remember target of the mob remember target<br />
$y the original actor in a chain of event progs<br />
<br />
These codes return numbers instead of a mob or object target:<br />
<br />
$a the amount of last successful mob damage OR mob award exp<br />
$B the level of the mob remember target<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage<br />
$A the name of the mob's object target, without quotes <br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$c the name of the current combat target of the mob's remember target<br />
$C the short desc of the current combat target of the mob's remember target<br />
$d the name of a random player-aligned mobile (i.e. pet or charmie) in the room<br />
$D the name of a random player-targetable mobile or PKable player in the room<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$h the name of a random player OR player-aligned mobile in the room<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$u the name of the mob's remember target's remember target<br />
$U the short desc of the mob's remember target's remember target<br />
$X the subject pronoun of the mob remember target<br />
$y the name of the original user of an event item, because $i can change in different force/call contexts<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
$$ an actual dollar sign symbol, in case you needed that<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|-<br />
|Remember Target's Remember Target|| $u || $U<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;BREAK:break<br />
This command will immediately stop the mobprog. Nothing else below a 'break' statement will be processed. This is often used to stop a prog short when one thing happens, so that later events in the same prog will not happen. It's commonly used in vnum-stacking.<br />
<br />
Examples: 451, 456<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;DECHO:mob decho <string><br />
As mob echo, but will not show the echo to the user.<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. In this case, only exact keywords are allowed, partials are not accepted. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single *exact* keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob gtransfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;MCLONE:mob mclone <target><br />
This command creates a perfect duplicate of a target mobile, including any modifications to it, such as restring/face fields, equipment, inventory, affects, etc. It cannot clone PCs.<br />
<br />
;OCLONE:mob oclone <target> [I]<br />
This command creates a perfect duplicate of a target object, including any modifications to it, such as restringed fields, affects, etc. By default, it will load the cloned object into the room, regardless of where the original object was. "I" can be added to the command to force the new object to appear in the mob's inventory instead.<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an *exact* argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
:Because the message strings are parsed by the mprog interpreter BEFORE being passed to the damage_next() function, $ variables will not work as expected when using the 'all' parameter. To show each actual victim's short desc in the "message to room", use the unintuitive '''$$N''' (with two dollarsigns) instead of '''$n'''.<br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [scaled]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'scaled' argument is optional, which causes awarded experience to scale by 0-200% based on the level difference between target and mob, like XP gained from kills. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area when not using scaled.<br />
<br />
It's possible to use 'mob award $i' but ONLY do this in event progs, where $i is the player.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;ADVANCE:mob advance <target> <value><br />
This command will advance the target to the specified level. This command MUST be used carefully, as it can reduce the target's level as well. The target can only be a player and not a mob. This command should also be used SPARINGLY as we should not be providing multiple level skips in the game and is mostly intended for use in RARE, PROMO-TYPE event objects and event content. To properly use this command without accidentally over- or under-leveling the player, the following set-up should be used, where the final 'mob counter' is the amount of levels you wish to grant the player:<br />
<br />
mob remember $n<br />
mob counter $B<br />
mob counter 1<br />
mob advance $n $z<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 16 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-16 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;QUESTALT:mob questalt <target> <+/-/=> <questflag><br />
As mob quest, but for the now-defunct hardcoded quest flags.<br />
<br />
;SET:mob set <target> <skill> <percent><br />
This command will set a player's skill% in the specified skill or spell. This is usually used to award quest skills at 1%.<br />
<br />
Skills that are in a player's class list, but not learned yet, are actually already learned at 1% and will be unlocked for use when the player also meets the level requirement. Mob set'ing them to 2% or higher will make them practicable/usable immediately.<br />
<br />
Examples: 823, 8947<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or an *exat* keyword for a mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here. Note that <br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;GCALL:mob gcall <vnum> [victim|'null'] [object1|'null'] [object2|'null']<br />
This command functions exactly like 'mob call', but will execute the called program once for every member of "victim"'s group, with $n iterating over groupmates across the loops. This includes NPC groupmates. The order of execution is based on the arrangement of the group members in the room; the original "victim" will not necessarily be first.<br />
<br />
Groupmates who are no longer in the room when it's "their turn" will not have the prog executed on them, so be careful when combining this with commands like gforce and gtransfer.<br />
<br />
If there is no victim specified, or the victim isn't in the same room, then the program will execute exactly once. In this case, $n in the called prog will be null.<br />
<br />
Examples: <br />
<br />
For gcall-based quest exp, first make a dedicated mprog, e.g. mpdump 17375:<br />
* Called by prog 1001. Booster statue in Truce<br />
if ispc $n<br />
if quest $n truce6<br />
or level $n >= 15<br />
else<br />
mob award $n exp 500 scaled<br />
mob echoat $n {WYou have completed a quest and gain $a experience!{x<br />
endif<br />
mob quest $n + truce6<br />
endif<br />
<br />
Then, call that prog in the main mobprog, e.g. mpdump 1001:<br />
mob echo Something clatters within the statue's head, and an LED spits out of<br />
its mouth.<br />
mob gcall 17375 $n<br />
<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
*condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
More fields: ed(keyword "new extra desc"), add (affect #modifier), apply(flag bitvector), delaffect(#)<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob. This command is very powerful, and can have complex syntax.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), alignment(#), damtype(a), hitroll(#), damroll(#), magroll(#), saves(#), dicecount(#), dicetype(#), acbash(#), acslash(#), acpierce(#), acexotic(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;RSET: mob rset <field/affect/command> <string/value/duration><br />
This allows a mob to temporarily edit the room they are standing in. These changes should not save through copyovers or crashes.<br />
<br />
*Available fields: name <string>, desc <string>, heal <value>, mana <value>, xpos <value>, ypos <value><br />
*Available affects: sandstorm , blizzard , frostveil, darkness, flash, firetrap, brainstorm, consecrate_neutral, consecrate_good, consecrate_evil, quicksand, hprain, sunstroke, timewarp, timestop, meteo, grease, skylight<br />
*Available commands: save, reset <"area"/"room"><br />
<br />
**There is a 500-ish character limit to 'mob rset desc <string>'.<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds [[Time#Beats|beats]] of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 999. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
;ANCIENTCAVE: mob ancientcave<br />
This command re-randomizes the ancient cave area. Don't use this unless you know exactly what you're doing, as the ancient cave receptionist mob already does this periodically.<br />
<br />
Examples: 13275<br />
<br />
;ADDLOG: mob addlog<br />
This command allows a mob to write to the mud's log, for debug purposes. It will write the short desc and vnum of the mob, followed by the argument. It may be useful for debugging mprogs that have a lot of moving parts.<br />
<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage/"all"><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* "all" can be also specified to trigger on any damage<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number/"all"><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number/"all"><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour/"all"><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
*By using the "all" keyword instead of a numerical hour, this trigger can also be set to execute every in-game hour, which is about once per minute. This is similar to a Random 100 trigger, but somewhat less frequent and therefore using less of the server's CPU time.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
<br />
===Mobprog Troubleshooting===<br />
<br />
Aside from improperly coding mobprogs, they sometimes don't work for less obvious reasons. Below is a basic guide to help troubleshoot mobprogs that appear like they should be working. You can also always ask other Builders for help.<br />
<br />
=====Inside Progs=====<br />
<br />
There's nothing much more to say about checking for typos other than, checking for them. Assuming nothing is simply misspelled, there are other typo-like errors to look for.<br />
<br />
:*Ensure placement of the variable(s) in the right place in the command, i.e. "give $n $o" is backward.<br />
:*A common error is to accidentally type things like, "mob get item" instead of simply "get item". Mobs can perform basic tasks without a 'mob' signifier.<br />
:*A space at the end of a mob command will cause it to not fire. Spaces at the beginning of lines are allowed and do not interfere with the command firing, but at the end, e.g. "mob peace ", they will cause the command to not work. Highlight your mobprog and check for accidental spaces at the end of commands where it seems to be breaking.<br />
:*If the mobprog is shared with other mobprogs in the same vnum, ensure a previous mprog is not breaking the ones after it. Missing or extra endifs in previous mobprogs can also cause these errors, so a perfectly written mobprog may not execute if it's stacked with another incorrectly written prog ahead of it in the stack.<br />
:*Double check things like "if vnum $i" checks to make sure the mob that is supposed to perform the action is properly written. <br />
<br />
=====Trigger Errors=====<br />
<br />
:*An act trigger for a mob that requires a social needs syntax as the mob sees it. This will be the same as seeing the social used on yourself, so forcing a mob to use the social on you will show you what the mob being acted upon will see.<br />
:*It is unadvised to use any part of the social echo that includes a pronoun, as there are many pronouns and you would have to add an additional trigger for each pronoun possible. This may still wind up breaking in the future if we add more genders.<br />
:*Act triggers that involve an item with color codes require the actual typed characters in perfect sync with the short of the item. This means if you color code your item like so, "a {Ggreen{R snapple{X" but write your act trigger like so, "a {Ggreen {Rsnapple{X", the act trigger will not fire. Remember: The game doesn't "see" colors, it sees the color codes as characters.<br />
:*If mobprogs do not appear to be triggering at all, please double check the wiki to ensure they do not interfere with other mobprogs, for example schedule triggers override simultaneous delay and random triggers. Two different mobprogs with the same trigger can't both activate at once, either.<br />
:*Ensure you are using the proper variant of GREET vs. GRALL and EXIT vs. EXALL if these appear to be improperly firing. Only use greet and exit if you do not want the mob to react to sneaking, hiding, or otherwise invisible players. <br />
<br />
=====Further Testing Tips=====<br />
<br />
:*A good method for troubleshooting a mobprog that otherwise appears to be properly written is to have the mob 'say' or otherwise announce each step of the mobprog. Adding the variables being used into the says can help ensure that other parts are happening correctly as well. When you do not see the expected extra says, you can assume the error is somewhere close by. <br />
:*Utilizing "mpstat [mobname]" will also help ensure that expected behaviors are occurring in the background, as far as counters, remember target, and delay timers.<br />
:*While testing a prog that involves a quest flag, you can force mobs to quest you and unquest you to ensure each step of the prog is reacting properly to the quest flags.<br />
:*Immortals cannot be forced by mobs, so it's common practice to make a test character to bring in and test such mobprogs for accuracy. <br />
<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=BEdit&diff=4266BEdit2021-05-12T02:31:55Z<p>Pascal: added rules and regulations</p>
<hr />
<div>[[Image:bedit.jpg|right|thumb|400px|clonk badonk]]<br />
<br />
BEdit, short for Base Edit, is an OLC mode available for players to build new rooms within the game, which can be private or public as the builder desires.<br />
<br />
This building mode is still in a 'beta' testing state, and so details are liable to change before full implementation.<br />
<br />
==Rules and Guidelines==<br />
======Guidelines======<br />
The purpose of BEdit is for players to be able to create their own basic player houses without Immortal intervention. There are more advanced player housing additions that are available but must be obtained through an Immortal. <br />
<br />
BEdit is not to allow players to participate in world building at large. While such endeavors may be acceptable, when considering a personal BEdit project that could overstep the lines between a player house and world building, the player has the personal responsibility to contact an Immortal and ask if their plans are acceptable. Unacceptable world building is subject to relocation or deconstruction by the Staff under the premise that the player should have done their due diligence to ensure it was appropriate before beginning their project. Additionally, such violations may be subject to punishment on a case by case basis. <br />
<br />
As always, a player seeking to lend their creativity to the game for actual world building can either apply for builder status or seek a willing Immortal to build their ideas for them.<br />
<br />
======Rules======<br />
1. BEdit should not be used in ways that may cause violations of the game's existing rules. <br />
:Ex. Room descs that give qinfo for nearby quests.<br />
2. BEdit rooms that are public should not detract from the expected quality of the game. <br />
:Ex1. With the exception of the house being under active construction, unfinished rooms cannot be left accessible by the public.<br />
:Ex2. Excessively graphic or obscene descs or custom objects would be considered a violation of this rule.<br />
3. BEdit rooms cannot interfere with the intended gameplay of the area they are built into. <br />
:Ex1. Placing too many exits in an existing area, either individually or because of multiple player houses, that make navigating the area much harder than intended.<br />
:Ex2. Making shortcuts with housing exits.<br />
4. If an area for the most part disallows the use of BEdit except for small numbers of rooms, it is most likely this is an error. Alert Staff to these instances before building in such a room. Violations of this will be removed once discovered and the creator subject to punishment.<br />
<br />
5. Public housing in starting towns and early areas, especially Truce, will be held to higher quality standards due to the likelyhood of newbies finding them. Make a good first impression!<br />
<br />
The Staff reserves the right to decide if a particular public player house is unacceptable for reasons not listed here. Such decisions will not be taken lightly and will be discussed between Staff and with the player who built the house before any action is taken. A house will not be deconstructed or moved without informing the player. If it requires immediate attention, it may be disconnected from the world until discussion can properly be had.<br />
<br />
==Using BEdit==<br />
===Creating New Houses===<br />
* show<br />
* build <direction><br />
* build portal<br />
<br />
Cost is 5000 + ( area's level x 50 ) gold. Not all areas can be built in. The 'show' command will tell you whether a house can be built, and what the cost will be.<br />
<br />
New houses are either created with a sign or portal outside, depending on how the house is linked. The name and description of this item can be freely edited, or it can be hidden, but its long description will always start with [Player Housing].<br />
<br />
'dig' and 'create' are synonyms for 'build'.<br />
<br />
===Expanding Houses===<br />
* show<br />
* build <direction><br />
<br />
Cost is 500 gold per room for the first 6 rooms, then 500 x (rooms - 5) beyond that. The 'show' command will calculate the cost for you, and show you other information about the room. Please note that all extra rooms are CUMULATIVE, regardless of how many individual houses you own. This means that if you own a home with 5 rooms and a house with 7 rooms, the next room you build for EITHER one of these houses will be at the cost of room #13.<br />
<br />
Interior rooms cannot be created with a portal.<br />
<br />
===Describing Rooms===<br />
* desc<br />
* name <string><br />
* format<br />
<br />
Rooms can have their descriptions edited freely. Room titles will always begin with [Player Housing], however.<br />
<br />
===Describing Signs or Portals===<br />
* entrance show<br />
* entrance short <string><br />
* entrance long <string><br />
* entrance name <string><br />
* entrance portal<br />
* entrance hidden<br />
* exit <direction><br />
<br />
Entrance portals will always have the keyword _portal_Playername. Portals and signs both will always have [Player Housing] at the beginning of their long description.<br />
<br />
Changing an entrance sign into a portal or vice-versa will reset its properties and descriptions. You can also hide the object and make it inert, if desired.<br />
<br />
The exit command can move a one-way exit from a house into a different direction. Changing the exit back into a normal two-way exit will re-link it to the live world in the appropriate way, if possible.<br />
<br />
====Extra Descriptions====<br />
* ed add <keyword><br />
* ed delete <keyword><br />
* ed edit <keyword><br />
* ed format <keyword><br />
<br />
Extra descriptions, which are shown when one enters 'look <keyword>' can be added and removed freely.<br />
<br />
===Deleting Rooms and Houses===<br />
* destroy <direction><br />
* destroy portal<br />
<br />
Deleting a room refunds half of what it cost to create. For safety, you can't destroy a room that isn't empty of furniture, or that still has exits to other rooms.<br />
<br />
===Access Lists===<br />
* access show<br />
* access add <name><br />
* access delete <name><br />
<br />
Rooms have one primary owner which cannot be changed, and a list of secondary owners which can be added and removed. Only the primary owner can edit the access list.<br />
<br />
The first room of a house has the builder as the primary owner, and no secondary owners. Expansion rooms will have their access list copied from the current room in any case.<br />
<br />
Unless a room is private, secondary owners can edit that room and add new ones connected to it.<br />
<br />
====Private Rooms====<br />
* access private<br />
<br />
If a room is set to private, secondary owners can no longer build in it, and players who are not owners cannot enter it at all!<br />
<br />
If the main room is made private, this effectively locks the entire house to players not on the access list.<br />
<br />
====Ejecting Players====<br />
* eject <player><br />
* eject self<br />
<br />
You can eject a player from any house you own, even if you're not in it.<br />
<br />
You can also eject yourself from any house at any time.<br />
<br />
===Adding and Removing Furniture===<br />
* buy list<br />
* buy <furniture><br />
* sell list<br />
* sell <reset number><br />
<br />
Furniture costs are in gold. More furniture can be added at any time. Selling furniture refunds 1/4 of its cost. If you would like a specific item placed in the shop for purchase, please let Lilly know, and she will (probably) make it happen. '''Please note: Purchasing an item installs the RESET for that item in the room, but not the object/mob itself. You must then wait for the object/mob to spawn naturally.'''<br />
<br />
For Immortals: Any object or mob reset into room 32766 will be available for purchase. A mob's cost as furniture is it's 'wealth' stat.<br />
<br />
===Changing Room Properties===<br />
* sector <sector><br />
* indoors<br />
<br />
Changing a room's [[Flags_Compendium#SECTOR|sector]] will cost the player 100 gold per change. Changing a room's status as indoors or outdoors costs 50 gold per toggle. Outdoors rooms will automatically also be set as lit.<br />
<br />
===Other Information===<br />
* done<br />
Like other OLC modes, you can leave the editor by typing 'done'.<br />
<br />
* recall<br />
You can freely set your recall point to any room you have building permission in.<br />
<br />
* commands<br />
You can see a list of BEdit commands at any time within the editor.</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Immortal_Shops&diff=4200Immortal Shops2021-04-19T03:57:08Z<p>Pascal: /* Rare and Exotic High-Risk Trading */</p>
<hr />
<div>For the sake of vanity, various staff members have set up shops that you can only access by trading in an immortal token. Some of these shops are hidden somewhere in the cleft, others require contacting an immortal.<br />
<br />
===Tea House of Ageatii===<br />
Hidden somewhere in the cleft, the Tea House of Ageatii can be accessed by trading in a clay cup of ageatea. A bank is present inside the shop for your convenience, but make sure you buy everything you came here for before leaving! The shop keeper, the Basilisk Ronin offers the following items:<br />
<br />
* Steel Fist Sake (1)<br />
: Cost: 300g Level: 50 Weight: 0lbs<br />
:: It is a potion with the level 50 spells of Attack Up, Encore and Encore<br />
<br />
* Steel Soul Sake<br />
: Cost: 300g Level: 50 Weight: 0lbs<br />
:: It is a potion with the level 50 spells of Protect, Encore and Encore<br />
<br />
* Rare Ores Grab Bag (%)<br />
: Cost: 500g Level: 0 Charges: 3 Cooldown: 0 minutes Weight: 0lbs<br />
:: It is an event that randomly creates rare crafting materials.<br />
<br />
* Masterball (%)<br />
: Cost: 750g Level: 65 Charges: -1 Cooldown: 2 minutes Weight: 1lbs<br />
:: It is an event that will charm and enslave the target, unless it is immune to charm or you already have a pet. It will then vanish.<br />
<br />
* Piece of Heart (x)(!)<br />
: Cost: 1500g Level: 0 Weight: 0lbs<br />
:: If you get four of these it will give you an additional 50 max HP.<br />
<br />
* Organ of the Evening Calm (m)<br />
: Cost: 2000g Level: 40 Cooldown: 10 minutes Weight: 2lbs<br />
:: It is a rod that can be worn as a shield and it casts a level 150 spell of Calm. It also affects HP by +150 and affects armor class by -40. This is an instrument that can affect Harvest Sprites, too.<br />
<br />
* Warp Whistle (Currently DISABLED)<br />
: Cost: 4000g Level: 0 Charges: 100 Cooldown: 0 minutes Weight: 1lbs<br />
:: It is an event that will call forth a spiraling vortex that carries you to a warp zone. The warp zone has pipes leading down to many locations around the world.<br />
<br />
* Dainty Cup of Ageatea (!)(x)(*)<br />
: Cost: 6000g Level: 0 Weight: 0lbs<br />
:: It is a handy and weightless fountain of tea. <br />
<br />
* Stone Mask (!)<br />
: Cost: 10,000g Level: 60 Weight: 2lbs<br />
:: Wearing this mask makes you permanently invisible(unless you enter a fight like the spell) but also makes you vulnerable to weapons, magic and degrades your dexterity by 4. With great power comes...Great weakness?<br />
<br />
=== The Wigglytuff Store (Carsanquay)===<br />
[[Wigglytuff]], the mysterious entity, will sell you these items for a frightening amount of gold and a tuna token. This shop requires an immortal to load Wigglytuff, so send an immortal a tell when you're willing to purchase an item. Each item costs 1 tuna token and its gold amount.<br />
<br />
* the wand of banishment (*)<br />
: Cost: 1,500g Level: 0 Weight: 3lbs<br />
:: This wand will send the target to a twisted void of shadow and horror. It will disappear when exhausted.<br />
:* It has 40 (max 40) charges of level 100 'Xzone'.<br />
<br />
* Lobster Power<br />
: Cost: 3,000g Level: 0 Weight: 1lb<br />
:: This staff, worn on the wrist, will enhance your power. It protects the wearer with a mystical barrier of thorns, enable the wearer to swim, make them slightly tougher, and possibly improve their love life. Or not.<br />
:* This staff improves Constitution by 2, Damroll by 5, AC by -10, adds Swim, and grants the Thorn Shield effect.<br />
:* It has 20 charges of level 50 'Attack Up'.<br />
<br />
* a lazy shell<br />
: Cost: 3,000g Level: 0 Weight: 35lbs<br />
:: This huge shell is worn on the torso. It makes the user a little tougher, but makes it harder to move freely. You could easily carry junk in this.<br />
:* This container improves Constitution by 1, worsens Dexterity by 2, and improves AC by -15. It's also a container, which can hold up to 10000 items weighing up to 10000 pounds, in total. The weight of all those items is reduced to 10% of their normal value.<br />
<br />
* a minivan<br />
: Cost: 6,000g Level: 60 (70 to purchase) Weight: 25lbs<br />
::* This is a van. You can ride in it! Sweet! Insanely strong people can also hulk out and use this as a weapon. Ouch. I don't even want to think about what that would do to your premiums.<br />
:* A minivan is a level 60 vehicle with seating for 8. It ignores move, and, when wielded as a weapon, affects dexterity by -4, damage roll by 70, armor class by -9,and hit roll by 100. WHAM!<br />
<br />
* the pratfallotron <br />
: Cost: 2,250g Level: 0 Weight: 2 lbs<br />
:: This item can be held. What it does is a mystery.<br />
<br />
===The Bountiful Garden Cafe & Gift Shop (Lilly)===<br />
The lovely waitstaff of this cafe have plenty to offer,<br />
both food and trinkets alike, as long as you have a Bag<br />
of Grass Seed (and plenty of gold) to exchange in return!<br />
This shop is hidden somewhere in the cleft and costs a single Bag of Grass Seed to enter. A bank is present, so be sure not to leave the shop until you've purchased everything you came here for!<br />
<br />
====Cafe====<br />
<br />
* A Bountiful Garden designer tote bag<br />
: Cost: 2000g, Level: 8, Weight: 2lbs<br />
:: Elegant and sturdy, this thing holds a lot!<br />
:* Weight Cap: 300lbs, Item Cap: 120, Weight Reduction: 40%<br />
:* Can be held or worn over the shoulder! AC -5, Moves +50, Wis & Int +1<br />
<br />
* A Bountiful Garden designer canteen<br />
: Cost: 1000g, Level: 1, Weight: 1lbs<br />
:: One of our best-selling souvenirs!<br />
:* Holds 250 units of liquid, starting with pre-filled root beer.<br />
:* Can be held, HP & Mana +20<br />
<br />
* A Caramel Mocha Latte<br />
: Cost: 500g, Level: 50, Weight: 0lbs<br />
:: Great for those who need a quick pick-me-up (and we do mean "quick")!<br />
:* This is a single-use potion with Lv110 spells of "Haste", "Regen" & "Extension"<br />
<br />
* An Angelic Energy Drink<br />
: Cost: 650g, Level: 50, Weight: 0lbs<br />
:: Downing one of these is guaranteed to bring about a heavenly experience!<br />
:* This is a single-use potion with Lv80 spells of "Attack Up", "Valor", & "Seraph Form"<br />
<br />
* A Slice of Bountiful Garden Cafe's Cherry Cheesecake<br />
: Cost: 50g, Level 5, Weight: 0lbs<br />
:: The signature treat of the Bountiful Garden Cafe! Few leave without having tried some at least once!<br />
:* This is food that provides 15 hours of satiation and 7 hours of fullness.<br />
:* Also heals the consumer by ~450 HP!<br />
<br />
* A Whole Bountiful Garden Cafe's Cherry Cheesecake<br />
: Cost: 200g, Level: 5, Weight 1lbs<br />
:: Why stop at just one slice when you can have the whole thing?<br />
:* This is a useable item that creates a slice of cheesecake when activated.<br />
:* Provides 6 slices total, and is no-recharge.<br />
<br />
====Gift Shop====<br />
<br />
* A Bountiful Garden 'Vol Wolf' Essence Bulb (!)(%)(m)(1)<br />
: Cost: 4000g, Level: 50, Weight: 0lbs<br />
:: A faithful companion for the more-traveled adventurer. Shockingly loyal!<br />
:* This is a useable item that will summon a Lv50 'Vol Wolf' as a pet.<br />
:* It has 1 charge, but does not disappear when exhausted.<br />
<br />
* A Bountiful Garden 'Rappy' Essence Bulb (!)(%)(m)(1)<br />
: Cost: 2500g, Level: 30, Weight: 0lbs<br />
:: A cute companion for the seasoned, but not super-experienced, traveler. Cuddly in its own way!<br />
:* This is a useable item that will summon a Lv30 'Rappy' as a pet.<br />
:* It has 1 charge, but does not disappear when exhausted.<br />
<br />
* An Adventurously-Cut, Pale Rose Tube Top (!)(%)(1)<br />
: Cost: 3800g, Level: 15, Weight: 1lbs<br />
:: Sleek and provocative, worn only by the most outgoing of ladies. Designed by our resident succubus, Natalie!<br />
:* This is a wand-type item that can be worn on the torso and is flagged AntiMale.<br />
:* AC +25, Hitroll +5, Damroll +10, Magroll+5, Mana +100<br />
:* Contains 20 charges of Lv50 'Charm'<br />
<br />
*(Bountiful Garden) Rose Dress Shoes (!)<br />
: Cost: 3200g, Level: 20, Weight: 1lbs<br />
:: Cute in their presentation and easy to move around in! These are the standard footwear apparel for our waitstaff.<br />
:* This is a wand-type item that can be worn on the feet and is flagged AntiMale.<br />
:* AC -20, Int/Wis+1, Dex +2, Mana +50, Magroll+2<br />
:* Contains 30 charges of Lv120 'Mana Restore'<br />
<br />
* (Bountiful Garden) A Pleated, Dark Rose Dress Skirt (!)<br />
: Cost: 3000g, Level: 30, Weight: 1lbs<br />
:: Stylish and elegant, this classy skirt is the standard legwear apparel for our waitstaff.<br />
:*This is an armor that can be worn on the legs and is flagged AntiMale.<br />
:* AC: 38 pierce/slash/bash, 45 Magic<br />
:* Int & Wis +1, HP/Mana/Mov +50, Magroll+3<br />
:* Adds resistance to iron & silver<br />
<br />
* (Bountiful Garden) A Ruffle-Sleeved, Rose-Hued Blouse (!)<br />
: Cost: 3000g, Level: 30, Weight: 1lbs<br />
:: Professional with a touch of grace, this pretty blouse is the standard upperwear apparel for our waitstaff.<br />
:* This is an armor that can be worn on the torso and is flagged AntiMale.<br />
:* AC: 38 pierce/slash/bash, 45 magic<br />
:* Int & Wis +1, HP/Mana/Mov +50, Magroll+3<br />
:* Adds resistance to charm & mental<br />
<br />
* A Soft and Cuddly Flammie Plushie (!) (1)<br />
: Cost: 8000g, Level: 85, Weight: 1lbs<br />
:: A soft, furry and squishy representation of the gentle Manabeast herself. A strong magical aura surrounds this toy; known to bring happiness to those who can afford one!<br />
:* This is a wand-type item that can be held.<br />
:* Mov +150, Mana/HP +250, Damroll/Magroll/Hitroll +5, Str & Wis +1<br />
:* Contains 20 charges of Lv100 'Float'<br />
<br />
* A Giant Sunflower Pillow (!)(1)<br />
: Cost: 3500g, Level: 12, Weight: 3lbs<br />
:: A bright decoration to throw around the house, yet sturdy enough to bring into combat!<br />
:* This is a furniture-type item that increases HP/Mana regen rates by 300%,<br />
:* can hold one person, and can be worn as a shield.<br />
:* HP +75, Con +3, AC -20, Mana +30<br />
<br />
* A Golden Ankh of Venus (!)(%)(1)<br />
: Cost: 2500g, Level: 30, Weight: 0lbs<br />
:: A symbol of the female gender itself, this trinket is guaranteed to turn your world upside down! Or is it inverted? We're not too sure, really. Has a unique effect if used with the full Bountiful Garden Waitress' ensemble.<br />
:* This is a useable item that can be worn around the neck. When used, it will cast Lv30 'Change Sex' & 'Extension' on the user if a target is not selected, or a specified player if one is selected.<br />
:* It has unlimited charges, with a cooldown of 3 minutes.<br />
:* Wis & Int +2, Mana +50<br />
<br />
* A Flammie Jetbike (!)(1)<br />
: Cost: 6800g, Level: 50, Weight: 5lbs<br />
:: Highly prized and consistently ranked at the top of most customers' "Most-Wanted" lists, this blazing vehicle boasts speed and durability, as well as easy carrying ability when not in use!<br />
:* This is a vehicle that is ignores movement during usage, is fast, and flying. It can hold 2 people, and can be worn on the body.<br />
:* Damroll +3, AC -10, HP +75, Mana +50, Mov +100<br />
<br />
* A Piece of Mind (!)(x)<br />
: Cost: 1500g, Level: 1, Weight: 0lbs<br />
:: The long-awaited counterpart to the Piece of Heart, obtaining four of these will boost your maximum Mana by 50!<br />
:* Collect four of these and turn them in to an Immortal to obtain +50 Max Mana.<br />
<br />
* A Token of Expansion (!)(x)(1)<br />
: Cost: 3500g, Level: 1, Weight: 0lbs<br />
:: Bigger houses, more room, happier guests! This token allows you to expand your house space by one room. Useful when you just don't have enough restring tokens (damn that stingy Lilly)!<br />
:* Give this token to an Immortal in charge of Player Housing to waive the cost of 1 room! Mobs, objects, and anything else not included.<br />
<br />
* A Token of Conversion (!)(x)(1)<br />
: Cost: 3000g, Level: 85, Weight: 0lbs<br />
:: You ask, and we answered! This token allows an adventurer to exchange 50 practice sessions for 5 training sessions! The power involved is a fickle one, however, and only one of these may be used per incarnation!<br />
:* This is a useable item that will deduct 50 practices and bestow 5 trains to the user. The player is then flagged for the playthrough, and may not use another one until reaching the appropriate level of their next remort session.<br />
<br />
* A Token of Exchange<br />
: Cost: 2500g, Level: 50, Weight: 0lbs<br />
:: Did you pick the wrong weaponskill? Are you tired of the one you DID pick and yearn for something else? We've got you covered! Simply exchange this trinket to Lilly to exchange your old weaponskill for a new one (at 50% of the original's "learned" percentage rate)!<br />
:* This is an exchangeable that will trade one weaponskill of your choice for a new one. The new weaponskill will be bestowed at half the learned rate of the one being swapped out.<br />
<br />
=<(The Magician's Trick)>=<br />
If you've received a black silk top hat with a red velvet band, you can visit Ozlynn's magical shop! By dropping the hat and entering it (which will promptly pick it back up), you can freely purchase these 4 items:<br />
<br />
* A Magikoopa Kap (1)<br />
: Cost: 750g, Level: 16, Weight: 4 lbs<br />
:: Use this hat to recall with style and hustle your goods to unsuspecting citizens, like a true Magikoopa! (Do not use in nonsmoking areas)<br />
:* This hat is an event that boosts INT by 1 and Mana by 30. It has 4 charges of recall.<br />
<br />
* A solid brick of cheese<br />
: Cost: 100g, Level:1, Weight: 10 lbs<br />
:: This big brick of cheese will provide 5 hours of satiation and 20 hours of fullness, but be warned: Eating 10 pounds of cheese in a single sitting might cause one to feel lethargic.<br />
<br />
* A twinkle, twinkle little star<br />
: Cost: 60g, Level: 5, Weight: 1 lbs<br />
:* This little star will guide you through darkness forever!.. Or at least 240 hours, whichever comes first. It affects Mana by 10 and saves by -2<br />
<br />
* A fancy bottle of orange juice<br />
: Cost: 320g, Level: 10, Weight 3 lbs<br />
:: Start your day out right. Start your day with orange juice!<br />
:* This is a drink container that holds 95 units, starting with orange juice.<br />
<br />
<br />
===For Serious Magicians===<br />
These items can only be purchased by trading in a tophat for each transaction. Magical!<br />
<br />
* A Personal Dimension<br />
: Cost: 6,200g, Level 30, Weighing 1 lbs.<br />
:: Holds 15 items weighing up to 10,000 pounds, Reducing weight by 100%<br />
:: Worn in float slot<br />
:* Adds regeneration, HP/Mana/MV +110<br />
<br />
* A Warp Star<br />
: Cost: 14,500g, Level 90 vehicle, Weighing 20 lbs.<br />
:: Holds 2 people, affects regen by 100%<br />
:: Fast, flying, indoors and ignores MV<br />
:: Worn in shield slot<br />
:* Affects hitroll by -3, AC -45, damroll +16, HP/Mana +120<br />
:: Note: It cannot be used by mobs<br />
<br />
* A pair of hypno-goggles (%)<br />
: Cost: 3,600 Level 35 event, weighing 2 lbs<br />
:: Has 100(max 100) charges with a cooldown of 120 minutes, with norecharge<br />
::Worn in face slot<br />
:: It will hypnotize/tame the target, then enslave them!<br />
:* Affects Con +2, AC -10, HP +40<br />
<br />
* A shiny cummerbund (%)<br />
: Cost: 13,500g, Level 50 rod, Weighing 0 lbs.<br />
:: Casts level 50 Dazzle, with a 10 minute cooldown.<br />
:: Worn in waist slot<br />
:* Affects AC -10, Mana +150, HP +50<br />
<br />
* A large, striped bow tie (!)<br />
: Cost: 12,500g, Level 80 rod, Weighing 1 lbs.<br />
:: Casts level 10 Charge, with a 5 minute cooldown, with norecharge<br />
:: Worn in neck slot<br />
:* Affects AC -5, HP +60, Mana +380, WIS +2, Int +2<br />
<br />
* A pair of glossy tap dancing shoes (!)<br />
: Cost: 11,000g Level 35 event, weighing 4 lbs.<br />
:: Has infinite charges with a 20 minute cooldown, with norecharge<br />
:: Worn in feet slot<br />
:: Tap dance in ways that might make you kick, break someone's heart, or get pumped and charged!<br />
:* Affects HP +30, Mana +40, AC -20, MV +100, dex +2<br />
<br />
* A flashy black suede cape, lined in red silk<br />
: Cost: 10,500g, Level 38 rod, weighing 8 lbs.<br />
:: Casts level 15 Invisibility, with a 30 minute cooldown, with norecharge<br />
:: Worn in about slot<br />
:*Affects AC -16, MV +30, Mana +110, HP +105, adds float<br />
:: Note: It cannot be used by mobs<br />
<br />
* A sterling silver cufflink (!)<br />
: Cost: 1000g, Level 0 staff, weighing 0 lbs.<br />
:: Has 20(max 25) charges of level 40 Haste<br />
:: Worn in wrist slot<br />
:* Affects damroll/hitroll +5, Ac -10, dex +2, adds ice shield<br />
<br />
* A Disco Star<br />
: Cost: 8,000g, Level 1.<br />
:* Summons a temporary float item and a temporary light item for a super boost!<br />
<br />
* A false memory (x)<br />
: Cost 15,000g, Level 0, weighing 0 lbs.<br />
:: Give this memory to Ozlynn and have her jam it into your head, but be warned, she'll take a memory in exchange!<br />
:* Trade in a skill NOT in your current class, which you remorted into the class you are now, for another skill of another class.<br />
:* The skill you wish to receive may not be a qspell, megamagic, a style(for simplicity's sake), or a skill that's outside what the current classes have available to them.<br />
:* Other restrictions may apply.<br />
<br />
= The Black Market (Cooper) =<br />
Hidden somewhere in the Cleft, the bartender of The Thieves' Den will accept a coin made of pyrite featuring the smug grinning mug of Cooper himself for access to The Black Market. Certain items can only be acquired by exchanging the coin!<br />
<br />
===Surplus Contraband===<br />
<br />
* Terrible, glittering potion (1)<br />
: Cost: 350g Level: 30 Weight: 4lbs<br />
:: Potion that casts level 80 Darkmatter and level 80 Bleeding.<br />
::* It is not recommended to drink these yourself.<br />
<br />
* Bottled enchantment essence<br />
: Cost: 250g Level: 8 Light: 80 hours Weight: 5lbs<br />
:: Used as light<br />
:* Affects ac -2, damroll 1<br />
<br />
* Bag of unusual food (x) (q) (A)<br />
: Cost: 25,000g Level: 40 Weight: 0lbs<br />
:: Worn in hold<br />
:: Event that spawns a random food on a 15 minute cooldown. Rechargeable, infinite charges. <br />
<br />
* Glass rod tipped with a beer keg (1) (m) (A)<br />
: Cost: 10,000g Level: 0 Weight: 2lbs<br />
:: Worn in hold<br />
:: Rod that casts level 1 Create Booze on a 10 minute cooldown. Rechargeable.<br />
:* Affects con 5<br />
<br />
<br />
===Rare and Exotic High-Risk Trading===<br />
<br />
* Tanuki Leaf (%) (1) (A)<br />
: Cost: 20,000g Level: 40 Charges: 30 Cooldown: 1 minute Weight 0lbs<br />
:: Worn in float<br />
:: Event item that equips the user with the Tanuki Suit. Suit is worn in head, face, about, legs, and feet and must be removed with the leaf, or by dying. How convenient! The leaf does not need to be worn while the suit is worn.<br />
:* Affects saves -10, hp 25, hitroll 5<br />
:* Suit grants infrared, detect hidden, motivation, sneak, fast, 500 move, 400 hp, 250 mana, 15 dex, 5 str, 10 damroll, 15 hitroll<br />
<br />
* Instalux brand instant tent (x) (!) (%) (1) (A) (norecharge)<br />
: Cost: 1,500g Level: 1 Charges: 500 Cooldown: 1 minute Weight 0lbs<br />
:: Worn in hold<br />
:: Event item that spawns a temporary tent. The tent grants 1000/1000 health/mana regen and can fit 5 people up to 10,000lbs. The tent disappears after 10 minutes or when the person who used the Instalux brand instant tent leaves the room.<br />
<br />
* Hooked staff, for thievery (1) (A)<br />
: Cost: 3,000g Level 23 Weight: 3lbs<br />
:: Long bashing weapon<br />
:* Claw attacks (slashing) 6d12 (average 39) <br />
:* Affects dex 5, hitroll 2<br />
:* Weapon flags: sharp, leaf<br />
:* Has a 3% chance to steal coins from your target, once per target (success percentage based on your own level).<br />
<br />
* Chrome cufflink (!) (1) (noexplode)<br />
: Cost: 1,000g Level 0 Charges: 15 (25max) Cooldown: 0 Weight .5lbs<br />
:: Worn on wrist<br />
:: Wand that casts level 5 Psyke Up with 15 charges (25 max)<br />
:* Affects ac -10, saves -10, wisdom 2, strength 2, magroll 5<br />
<br />
* Pair of finely tailored crocodile skin, suede padded leggings (1)<br />
: Cost: 18,000g Level: 31 Weight 10lbs<br />
:: Worn on legs<br />
:: Armor with 25/25/25/25<br />
:* Affects moves 300, mana 200, hp 100, dex 3, damroll 5, hitroll 2<br />
<br />
* High-tech steel-reinforced designer tote bag <br />
: Cost: 2,000g Level: 8 Weight: 10lbs<br />
:: Worn on shoulders, hold<br />
:: Container with 100 item capacity, up to 300lbs. Items weigh 30% of normal.<br />
:* Affects ac -15, mana 20, str 3<br />
<br />
* Super Potato Plushie (!) (%) (1) (A)<br />
: Cost: 4,500g Level: 3 Cooldown: 3 minutes Weight: 2lbs<br />
:: Worn in hold<br />
:: Rod that casts level 3 Create Food on a 3 minute cooldown<br />
:* Affects ac -10, saves -5, moves 50, wis 1, int 1, con 1, dex 1, str 1<br />
<br />
* Pouch-laden sash (!) (A) (noexplode)<br />
: Cost: 3,500g Level: 17 Charges: 70 Weight: 3lbs<br />
:: Worn in waist<br />
:: Wand with 70 charges of level 1 Idle Hands<br />
:* Affects ac -10, moves 100, hitroll 5<br />
<br />
* Unusually large flask, modified for use as a shield (!) (noexplode)<br />
: Cost: 23,000g Level 71 Units: 300 Weight: 12lbs<br />
:: Worn as shield<br />
:: Drink container with 300 units of whisky. Refillable.<br />
:* Affects ac -40, con 5, damroll 5, magroll 5<br />
:* Grants resistance to draining<br />
<br />
* Ring of pure condensed magic (1) (A) (norecharge)<br />
: Cost: 25,000g Level: 60 Cooldown: 15 minutes Weight: 2lbs<br />
:: Worn on finger<br />
:: Rod that casts level 60 Rainbow on a 15 minute cooldown<br />
:* Affects saves -10, mana 600, int 5, magroll 4<br />
<br />
<br />
(x)= Uncounted (!)= Adhesive (*)= Magic (%)= No Check (m)= Hum (1)= Unique (A)= Anti-mob</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Building_Guide&diff=2527Building Guide2019-12-11T02:21:18Z<p>Pascal: /* Editing Quest Lists */</p>
<hr />
<div>*''This guide is adapted from [http://web.archive.org/web/20020402164025/http://www.geocities.com/TimesSquare/Dome/4876/ OLC: Down and Dirty in the Mud] (original Geocities site offline) by Kara Ann''<br />
<br />
OLC is short for On-Line Creation. It is your friend.<br />
<br />
OLC is a set of code added to a MUD that allows builders to edit area files in real-time while logged into the MUD, instead of the old method of manually editing text files and rebooting the game every time a change is to be implemented.<br />
<br />
There are many different versions of OLC in use on different MUDs, although the syntax and usage is fairly standard. Becoming familiar with OLC will let you be an asset as a builder on almost any MUD. This guide is written explicitly for the Cleft of Dimensions, however.<br />
<br />
==Basics==<br />
===Vnums===<br />
'VNUM' is short for 'virtual number'. One vnum can be assigned to a mobile, an object, a room, AND a [[Mprog Compendium|mob program]] (or mprog)<br />
<br />
Each mobile and object has a virtual number, which is used to store the index data or template that is used to create each instance of that mobile or object.<br />
<br />
For example:<br />
* Object vnum 1050 contains data for a pair of purple pants. Every pair of purple pants in the game shares this vnum, but object vnum 1050 is only used for purple pants.<br />
* Mobile vnum 1050 contains data for Green Imps. Every Green Imp in the game uses shares this vnum, and mobile vnum 1050 is only used by Green Imps.<br />
* Room vnum 1050 contains data for a section of road in Truce Canyon. There is only one room with this vnum, and any references to room vnum 1050 are thus references to this specific section of road.<br />
* Mob program vnum 1050 contains a greet program for the Imp King. Only one mobprog is number 1050, and any references to mobprog 1050 are to this one, although one prog can be used by several mobs.<br />
<br />
===Building Modes===<br />
These are modes in which builders can edit certain things. <br />
* REDIT - room edit, rooms are created, linked, and edited, and resets are made within this mode<br />
* OEDIT - object edit, objects are created and edited within this mode<br />
* MEDIT - mobile edit, mobs are created and edited within this mode<br />
* MPEDIT - mobprogram edit, mob programs are created and edited within this mode (reserved for builders above level 101)<br />
* AEDIT - area edit, area files are created and edited within this mode (generally reserved for the head builder)<br />
* HEDIT - help edit, creates and modifies help files (reserved for high-level staff)<br />
Commands are limited between modes, IE you can only do certain things in a given mode. For a list of commands specific to each mode, enter one and type '''commands'''.<br />
<br />
You can switch from one mode to another any time. To exit a mode, type '''done'''.<br />
<br />
===Saving your Work===<br />
It is vitally important to save completed work often. If the game crashes or is rebooted without saving, any work done will be lost forever. To save your work, type '''asave changed''' frequently. This works in all edit modes and will save everything that has been changed or created.<br />
<br />
===Names===<br />
Object and mobile names function as keywords for targeting those objects and mobiles. Any words within the name will work to target the object or mobile. Adding too many names to an object or mobile increases the chance of ambiguity when attempting to interact with it.<br />
<br />
If a mobile's name is 'green imp' then both 'look green' and 'look imp' will function correctly. If the mobile's name is 'a green imp' then 'look a' will also target the imp, which is not desired behavior.<br />
<br />
If the long description doesn't contain the same words as the short description, it's good form to add extra words to the name. For example, the Chain Chomp's short desc is "a Chain Chomp", while its long desc is "A round black beast tied to a chain is chomping away at you as close as it can get." Since a player may not know from the long desc that it is a chain chomp, they will probably type 'look beast' to find out more about it. Because of this, the mob's name string is 'chain chomp beast' so that all these words function correctly.<br />
<br />
===Short Descriptions===<br />
A short description is the text displayed when an object or mobile is being interacted with, such as 'a red apple' or 'the noxious Grimer'.<br />
<br />
Short descriptions should either be a proper noun or begin with an article. (a/an/the/some/etc)<br />
<br />
===Long Descriptions===<br />
A long description is the text displayed when an object or mobile is seen in a room, such as 'The enterprising Hassan is here, waiting to make a sale.' <br />
<br />
Note that long descs are not the same as a mobile's 'description'.<br />
<br />
==REDIT==<br />
Redit is the mode used to create and change rooms and exits between rooms. <br />
<br />
To enter Redit mode, you can type '''redit''' by itself, but only if you are in an area that you have permission to modify.<br />
<br />
To see all the rooms in an area and their vnums, type '''rlist'''. To see details about the room you're working on, type '''show''' or just enter a blank line.<br />
<br />
===Creating New Rooms===<br />
To create a room from scratch, you '''redit create (new room vnum)''', which will create an empty room with no exits, and simultaneously move you into it.<br />
<br />
You can also simultaneously create a new room and a two-way exit to it by typing '''(direction) dig (new room vnum)''', where the direction is which way from the current room to link it.<br />
<br />
A brand-new room will have no name, no description, and no special properties.<br />
<br />
===Linking Existing Rooms===<br />
Rooms can have two-way and one-way [[exits]]. <br />
<br />
To create a two-way exit from a room, type '''(direction) link (other room)''', where direction is which way the exit will be in this room. Two-way exits are always linked opposite of each other E.G. if Room A has a two-way exit West to Room B, then Room B will have an exit East to Room A. A door on one side of a two-way exit will let people on the other side know that it has been opened.<br />
<br />
To create a one-way exit from a room, type '''(direction) room (other room)'''. One-way exits don't do anything to the room on the other side, so be careful not to create dead-ends when using one-way exits.<br />
<br />
When linking rooms from different areas make sure that both areas are edited and saved. The link will not save if you only asave changed.<br />
<br />
====Deleting Exits====<br />
Rooms cannot be deleted, but exits can. To delete an exit, type '''(direction) delete'''. Deleting a two-way exit removes both sides.<br />
Note that if you delete a one-way exit that leads to a room where the "returning" exit is different, both exits would be deleted.<br />
<br />
===Describing Rooms===<br />
To set the name of a room, go to the room to name and type '''name (name)'''. <br />
<br />
A room's Name is the line of text that players see at the top of the description when they see a room or type 'exits', and the part a builder sees when typing 'rlist'. It's standard procedure in this MUD to include the area name in the room title. Normal formats are 'Area Name - Room Name' and 'Room Name, Area Name', colored however you wish.<br />
<br />
To edit a room's description, enter the room to be described and just type '''description'''. This enters the description editor, which is identical to the normal note and player desc editor. Type .h if you need help using the editor.<br />
<br />
A room's description is the block of text that players see when they look at a room, describing its contents and atmosphere. Room descs can be colored, but they should all be one solid color for readability. <br />
<br />
====Description Style Tips====<br />
Keeping descriptions to a decent length is important, since players will often avoid reading anything that shows up as one giant wall of words. Five or six lines is usually plenty. If you want to elaborate more on something in the room, you can use an extra desc (see below).<br />
<br />
Colors are available to help set a mood, but be aware that some colors (particularly blue and dark blue) are difficult to read on a black background. Descriptions can be colored, but should be one solid color for readability unless highlighting specific words.<br />
<br />
Descs should stay objective in tone, avoiding references to the reader. "The monster terrifies you." is inapplicable if the player is a robot incapable of fear or a hardy warrior who's seen worse. That said, sometimes it's more fun to write them subjectively; be <br />
<br />
====Extra Descriptions====<br />
Extra Descriptions are additional descriptions a room can have for curious players who try to look at things mentioned in the main description. IE If a room description mentions that there is a painting on the wall, you could describe the painting in depth using an extra desc for the word 'painting' to avoid cluttering the main room desc.<br />
<br />
If there is an item or mob in the room with the same name as an extra desc, then the player will see that item or mob instead of the extra desc.<br />
<br />
To add an extra desc to a room, type '''ed add (keywords)'''. You can add one desc for multiple keywords at once if you enclose them in double quotes. To edit an existing extra desc, type '''ed edit (keyword)'''. To delete an extra desc, type '''ed delete (keyword)'''.<br />
<br />
Extra descs can be any length, can contain asciiart, break the fourth wall, and ignore all sorts of other description conventions for the sake of an interesting experience. It's good form to add extra descs in every room you can, but it's not strictly necessary.<br />
<br />
===Changing Room Properties===<br />
To toggle a room flag, type '''room (flag name)'''. Most room properties exist as flags, which can all be toggled on and off individually. All flags are off in a new room. For a list of room flags and their functions, see [[Flags_Compendium#ROOM_FLAGS]].<br />
<br />
To change a room's sector, type '''sector (sector name)'''. A sector has information about the general biome or type of room. A room can only have one sector, and it is set to 'inside' by default. For a list of sectors and their functions, see [[Flags_Compendium#SECTOR]].<br />
<br />
To change a room's mana or health regeneration rates, type '''heal (percent)''' or '''mana (percent)'''. These numbers are percentages that regeneration rates are modified by EG 'mana 200' will double MP regeneration for players and monsters alike in the room. Note that setting a negative number won't cause damage, but will floor regeneration rates to their absolute minimum.<br />
<br />
Rooms can also have specific positions on the weather grid and extra weather modifiers. These are usually set at for the whole area instead of for specific rooms. A room's weather modifiers will override the ones set for the area. Avoid very high weather modifiers unless absolutely necessary (You're in a tornado!). We want the weather modifying spells to be more useful..<br />
To set a room's coordinates, type "xarea #" or "yarea #".<br />
<br />
===Changing Exit Properties===<br />
To toggle an exit flag, type '''(direction) (flag name)'''. For a list of exit flags and their functions, see [[Flags_Compendium#EXITS]]. Note that for 'closed', 'locked', etc to work, 'door' must be on. If 'door' is on but 'closed' is not, then the door will open itself when the area is reset and players will likely not even notice it. Applying a flag to one side of a two-way exit will automatically apply it to the other side as well.<br />
<br />
If a door is locked, you can specify what item a player needs to unlock it by typing '''(direction) key (obj vnum)'''. The player will only need to have the object in their inventory to be able to unlock the door.<br />
<br />
====Exit Names and Descs====<br />
Doors can also have special names and descriptions. These can help immerse the player in the area they're exploring.<br />
<br />
To set an exit's keywords, type '''(direction) name "(names)"''' Note that the double quotes are required. This will allow players to use these names when trying to open or close the door EG 'east name gate' will allow players to type 'open gate' in addition to 'open east' to open the door, as well as allowing them to 'enter gate' in addition to just typing 'east'. Once you've given an exit a special name, you can make the exit hidden and mention 'There is a gate to the east.' in the room's description to reward players that read descs thoroughly. You can use '(direction) name none' to remove all names.<br />
<br />
To set an exit's description, type '''(direction) desc "(desc)"''' Note that the double quotes are required. A door's description string is cosmetic, and will be shown to people manipulating the door EG 'east desc "the imposing iron gate"' will show players 'You open the imposing iron gate'/'Soandso opens the imposing iron gate', etc. You can use '(direction) desc none' to remove anything and revert the exit to using the default text 'the door'.<br />
<br />
==MEDIT==<br />
<br />
Medit is the mode used to create and edit mobs, or mobiles, AKA NPCs. A mob is any fightable or unfightable monster, shopkeeper, quest NPC, townsperson, boss, etc. Mobs can also be made completely invisible to players in order to create special events or puzzles.<br />
<br />
To see all the mobs in the area you're in, type '''mlist'''. You can see only mobs with a certain name with '''mlist (name)'''.<br />
<br />
To see details about the mob you're currently working on, type '''show''' or just enter a blank line.<br />
<br />
===Creating and Editing Mobs===<br />
To enter Medit mode, you must type either '''medit create (empty mobile vnum)''' or '''medit (existing mobile vnum)''' If you try to create a mob in a vnum that already exists, or edit a mob that doesn't already exist, you will receive an error and not enter medit mode. <br />
<br />
A newly created mobile is mostly blank and has no name, description, or attributes.<br />
<br />
===Describing Mobs===<br />
To set the name of a mob, type '''name (mobile names)'''. This is not the same as the mobile's short description, and the names are never seen by the player all at once.<br />
<br />
To set the short description of a mob, type '''short (short description)'''. This is the what the player sees when interacting with the mobile.<br />
<br />
To set the mob's long description, type '''long (long description)'''. This is the line of text that the player sees when looking at a room with this mob in it.<br />
<br />
To create or change a mob's description, type '''desc'''. This enters the string editor, and if the mob already has a desc it will be loaded into the editor. When you are finished editing the description, type '''@''' to exit the editor. A mob's description is what a player sees when looking at the mob. A mob without a description only shows the player 'You see nothing special about (him/her/it).'<br />
<br />
===Setting Mob Stats===<br />
Mobs have a variety of statistics. They can all be changed from within Medit mode.<br />
<br />
A mob's race can be set with '''race (race name)'''. To see a list of all PC and NPC races in the game, type '''race ?'''. A mob's race pre-sets act, form, part, imm, res, and vuln flags. Changing an existing mob's race will add new flags but won't remove existing ones. A mob's race doesn't affect many things on its own, though.<br />
<br />
Mobiles have lots of other stats that can be set.<br />
<br />
;sex (male/female/neutral/random)<br />
:The mob's gender; modifies pronouns when interacting with the mob. A mob set to be Random sex will be randomly male or female each time it is loaded.<br />
;level (#)<br />
:The level of the mob. Note that a mob's armor values will need to be modified accordingly with the mob's level.<br />
;align (#)<br />
:While players can only range from -1000 to 1000, mobs can have outrageous alignment values. Despite this, -1000 to 1000 is normal.<br />
;hitroll (#)<br />
:This is a bonus or penalty to hitroll for this mob. This usually isn't necessary to change.<br />
;damtype (damage type)<br />
:This is the damage noun and thus damage type that the mob uses for unarmed attacks. Type '''? weapon''' for a list.<br />
;hitdice (XdY + Z)<br />
:Must be entered with the '''d''' and '''+'''. A mobile will have a randomly-rolled amount of hit points when loaded. A mobile's hit points should not vary too widely to prevent very easy/difficult to defeat outliers.<br />
;manadice (XdY + Z)<br />
:Mobiles have mana, but will not use it unless explicitly told to by an mobprog. This number is rolled when a mobile is loaded, like hit dice.<br />
;damdice (XdY + Z)<br />
:The first two numbers determine how much damage a mobile will do with unarmed attacks. If the mob is wielding a proper weapon, it will do damage based on the weapon instead. The third number is the mob's damroll. This bonus will apply whether the mob has a weapon or not!<br />
;armor (# # # #)<br />
:The AC scores of the mobile. The actual amount of damage prevented depends on the level of the mobile as well. All four values must be entered to set all four armor scores for the mobile.<br />
;size (size)<br />
:Type '''? size''' for a list of valid sizes. This stat mostly affects combat skills like bash and trip.<br />
;wealth (#)<br />
:The amount of wealth, in silver, that this mob carries. This number is not exact, so a mob will have a random amount of money when actually loaded, somewhere near this variable. If the wealth value is high enough, at least some portion of the mob's money will be in gold coins.<br />
<br />
When setting stats on a mob, use the Formulator application to determine how much HP, armor, etc it should have based on its level. Talk to another staff member for information on how to download this application.<br />
<br />
===Mobile Special Properties===<br />
<br />
In addition to their descriptions and stats, mobs can have a variety of special flags that change how they act.<br />
<br />
To toggle a mob's Act flags, type '''act (flags to toggle)''' A mob's act2, affect, shield, form, part, imm, res, vuln, offensive, and behavior flags are changed in the same way. <br />
<br />
For a list of all applicable mob flags, see [[Flags_Compendium#MOB_FLAGS]], or type '''? (flag name)''' while in medit mode.<br />
<br />
==OEDIT==<br />
===Basics===<br />
<br />
Oedit is the mode to edit objects, which includes fountains, apples, swords, basically anything that can't move around or perform actions on its own. Though note that there are cases where you may want a certain thing like a computer to be an object vs. a mob. Mobs can react to people interacting with them, objects cannot.<br />
<br />
Like the other modes, you need to either '''oedit create (vnum)''' or '''oedit (vnum)''' depending on whether it already exists or not. A new object will be basically blank and featureless. You can check its status at any time that you're in oedit mode by typing '''show'''.<br />
<br />
===Descriptions===<br />
<br />
There are three main descriptions that an item needs:<br />
<br />
'''Name''' - These are the keywords that the player uses to identify the item. They'll never actually *see* this (so no need for colors), but you want it to include the relevant keywords from it's short and long descs. Depending on what item it is, you may want to add certain hidden names in order to sort them for later searching. Typically for weapons this is +wtype, like +sslash, and for armor it's =slot, like =legs. (Later you can take advantage of these along with vnum to search for a certain slot, or in an mprog to remove whatever's on the legs, as long as it's been properly tagged)<br />
<br />
Example: name silver sword excalibur +sslash<br />
<br />
'''Short''' - This is the word that shows up directly for the object, such as when the player picks it up or has it equipped. This should not be very long, and including 'a', 'an', or 'the' is appropriate unless it has an actual proper name, as the player should ideally see 'You get '''an apple'''' rather than 'You get '''apple''''. This is also where color is most likely to be used.<br />
<br />
Example: short {WExcalibur{x<br />
<br />
'''Long''' - This description is what will be seen when the item is sitting on the ground in a room. Keep in mind both where it comes from and the fact that players could potentially later drop the items in different places entirely. This is also what will normally show up for the description of the item (see below).<br />
<br />
Example: long A silver sword has been stuck in the ground.<br />
<br />
There's also extra descriptions. As mentioned, the long description is the default, but that's generally not good enough for a real item. In order to attach a longer description, exdescs must be utilized. These can be done with '''ed add "<keywords>"''', '''ed edit "<keywords>"''', and '''ed delete "<keywords>"'''. Remember the quotes there or else it will only take the first word that you specify. Once you do ed add, an editor window will pop up, similar to personal or mob descriptions. Just put your text in there. Make sure that you include all the same keywords that are in the name (though any hidden ones are generally unnecessary).<br />
<br />
Example: <br />
ed add "silver sword excalibur"<br />
<br />
.c<br />
<br />
This shining sword looks like the weapon of a true king! It glows with soft light from within.<br />
<br />
.f<br />
<br />
@<br />
<br />
If an object has a keyword set as one of its names, but no extra desc for that keyword, then the object's long desc will be used instead. For example:<br />
*name: silver sword runes<br />
*short: a silver sword with runes<br />
*long: Covered with runes, a silver sword has been left here.<br />
*extra desc with keyword 'runes': These runes are in a long forgotten language.<br />
*"look sword"/"look silver": "Covered with runes, a silver sword has been left here."<br />
*"look runes": "These runes are in a long forgotten language."<br />
<br />
===Stats===<br />
<br />
'''Type''' - One very important part of any object is it's type. This determines what other flags it has - weapons will have flags to determine what type of damage it does and how hard it hits, pills will have flags for what spells they cast, trash is trash, etc. For a full list of these, check the [[Flags_Compendium/Obj_Types]]. Once a type is selected, new flags v0 - v4 show up and will need to be selected.<br />
<br />
'''Level''' - The level that is required to use this item. Keep in mind that items will poof if the player is too underleveled and the remortable flag is not on the item.<br />
<br />
'''Wear''' - The wear flags determine if the item can be worn and where. Most important of these is '''take'''! If you don't flag the item as wear take, it will not be able to be picked up at all. This also means you can make strange cases, like wearing a weapon on your face or a rod on your wrist. Note that the arms, waist, and shoulders slots are typically not used in our MUD, so do not use those unless you have an good reason and have checked with someone else.<br />
<br />
'''Extra''', '''Extra2''' - These two flags hold various important utilities that do a variety of things. Refer to the [[Flags Compendium]] for full information.<br />
<br />
'''Weight''' - How heavy the item is. 10 here means 1 pound.<br />
<br />
'''Cost''' - How much the object is worth, in silver. Keep in mind that this is just the base, and shopkeeper settings mean they'd buy the item for 60% of it's real cost, etc.<br />
<br />
===Enchantments===<br />
<br />
One last trick that you might need to know is how to put affects and applys on items. These are the 'enchantments', the stuff like dex+2 or permanent quartz guard that goes on an item you wear.<br />
<br />
They are split into two categories:<br />
<br />
'''Addaffect''' - This is used for purely stat boosts. There's a lot of options here, but you don't really want to touch anything other than the primary stats (str, dex, etc), mana, hp, move, saves, ac, hitroll and damroll. The rest you really don't want to be messing with on items. The syntax is '''addaffect <type> <amount>'''. Remember that if you're doing this with AC, good AC is negative, not positive.<br />
<br />
Example: addaffect str 2<br />
<br />
'''Addapply''' - Addapply does the stuff that's not just stats but effects. The syntax for this is really strange - by definition an addapply must also *include* an addaffect, but it can be of type 'none'. The flags that can be added include affects, object, immune/resist/vuln, weapon, and shield flags (For a full list of these refer to mob flag information). Once added these show up on the object show as just addaffects w/out the associated real effect, so you may have to load a copy of the object and identify it to make sure it's working right.<br />
<br />
Here are a few examples:<br />
<br />
'''addapply vuln str 1 bash''' - This gives +1 strength but weakness to bashing damage.<br />
<br />
'''addapply affects none 0 slow''' - This causes a permanent slow state, with no other effects.<br />
<br />
'''addapply shield mana 20 confused''' - This causes the player to gain 20 max mana but be constantly confused.<br />
<br />
To remove an affect or apply, just use delaffect #, where the # is the right one from typing '''show''' in oedit mode.<br />
<br />
That's basically it - items are fairly straightforward!<br />
<br />
==MPEDIT==<br />
See [[Mprog Compendium]]. And then ask someone to show you what to do because mprogs can get confusing fast.<br />
<br />
==AEDIT==<br />
Aedit is the mode used to create and modify area files, their vnum ranges, and certain area-wide flags and settings.<br />
<br />
Typing 'aedit' in any room will begin editing the area that room is in, assuming you have appropriate permission. Aedit is currently a level 105 (advanced builder) command.<br />
<br />
===Creating a New Area===<br />
To create a new area, enter aedit from any existing area and type 'create'. This makes a new area with no vnums assigned and gives it the filename area0.are. ''Areas cannot be deleted from within OLC, so do not use this command for no reason.''<br />
<br />
Several fields need to be set right away: use 'filename <foo.are>' to change the filename of the area, which should be short (8 characters, lowercase) but clearly indicate the name of the area. Consult with the head builder or higher immortal for further guidance.<br />
<br />
Next, the base vnum range needs to be set to a block of free vnums. This can be done with either the 'vnum (lower) (upper)' command, or separately with 'lvnum (lower)' and 'uvnum (upper)' commands. OLC will not let you use vnums that are already part of a different area. Convention in the Cleft of Dimensions is to create new areas with contiguous vnums, so consult with the head builder or higher immortal to figure out the next highest block, or use 'alist' to figure it out yourself!<br />
* An area can contain rooms from outside its vnum range, relocated with the 'areaoverride (filename)' Redit command. Use this sparingly, as it was mostly designed for expanding old areas which were created with insufficient vnum space!<br />
<br />
Make sure to give the area a name, using the 'name (name)' command. Note that this name can be displayed to players at various points.<br />
<br />
Finally, fill out the credits field for the area; this is what shows up in the 'areas' command, and unintuitively does not contain the builder credits for the area. It takes the form of '''{c[{Y Area Name {wLw-Up {c]{x'''<br />
<br />
===Security and Builders===<br />
Areas can only be modified by specified people. Access can be tweaked by changing the area's Security and Builders.<br />
<br />
'Security (number)' will restrict editing of the level to immortals with security equal or higher to the given number.<br />
<br />
'Builders (name/all)' will toggle a given immortal's name, allowing that builder to override the security setting for the area. This is usually done to assign new builders to their probational area without allowing them edit access to anywhere else.<br />
<br />
===Weather, Location and Level Range===<br />
Regardless of what [[weather]] system is over the area's X/Y coordinates, the weather can be adjusted area-wide with the 'skymod (number)' and 'wndmod (number)' commands, which range from 4 to -4. <br />
*These can also be set per room.<br />
<br />
The area's X/Y coordinates can be set with the 'xpos (number)' and 'ypos (number)' commands. This determines the area's place on the weather map as well as the atlas.<br />
*These can also be set per room.<br />
<br />
The area's level range is used to show players the area when appropriate in response to an 'areas' command with no arguments. This should be set appropriately for the mobs and objects in the area.<br />
<br />
===Flags===<br />
Areas have two types of flags: area flags, and exflags. Exflags can be set by a builder by using 'exflags (flag)', and have various practical effects on the area for players. The list is at [[Flags_Compendium#AREA_EXFLAGS]]<br />
<br />
The other kind of Area flags are for temporary weather up/down affects (caused by the Stormy Sky and Clear Sky affects) and other things about the loading/saving of area files:<br />
* Changed: Area has changed and will be written to disk at the next 'asave changed'.<br />
* Added: Area is new and will be written to disk for the first time at the next 'asave changed'.<br />
* Loading: Used for counting in db.c<br />
* Weather Up: Area is affected by Stormy Sky and has a temporary additional +1 to Wind modifier and Sky modifier.<br />
* Weather Down: Area is affected by Clear Sky and has a temporary additional -1 to Wind modifier and Sky modifier.<br />
<br />
===Other Commands===<br />
'age (number)' overrides an area's current age (in minutes) for the purpose of reset timing.<br />
<br />
'automap' does nothing useful or interesting, and is probably a vestigal remnant of some planned function.<br />
<br />
'commands' shows all the valid aedit commands.<br />
<br />
'reset' forces an immediate reset of the entire area's objects and mobs.<br />
<br />
'show' is the same as a blank line in Aedit mode, and shows information about the area being edited.<br />
<br />
'? (field)' shows available flags in a given field, like other OLC editors.<br />
<br />
'version' shows OLC credits.<br />
<br />
==HEDIT==<br />
===Editing General Help Files===<br />
For an existing help file you can just type '''hedit <keyword>''' to open that file. It has the keywords, the level to view the file (101 for immortal-only helpfiles, otherwise 0 generally), and the text itself.<br />
<br />
To create a new helpfile, start with '''hedit hedit''' to open a helpfile in general, then type '''new help.are keyword''' - help.are can also be olc.are or somewhere else, this is mainly for organizational purposes. In general, to ensure helpfiles get saved, it is best to edit an area in some minor way (add and remove a safe room flag, for instance) and asave changed to have both save at the same time.<br />
<br />
===Editing Maps===<br />
Maps are slightly trickier. When designing a map, it should be 60x24 characters. You also want to put it in maps.are, again for organizational purposes. Maps should be named area.are000 and incrementing. Examples: '''truce.are000''', '''saturnv.are001'''<br />
<br />
Whichever map is 000 will be set as the default local map for that area (provided it matches the name exactly! you should be using your area name exactly as it is in game). To make an individual room use a different map, redit that room and '''localmap newmap.are00x'''. These maps should all be at security level 101 - players will be able to see them as maps but not by typing 'help'.<br />
<br />
ProTuna also has built-in functionality to highlight the area where the player is on the map, but this must be manually set. To do this, type '''xlocal 1''' and '''ylocal 1''' where 1,1 is the top left character of your map. These must be set individually for each room.<br />
<br />
===Editing Quest Lists===<br />
Each area also has a corresponding quest list to be stored as: '''areaname.are.quests''' (like truce.are.quests). These are basically just text, except you can use the string '''^areaname1''' to show whether that questflag has been obtained or not. You can also hide quests until they are completed by prefacing them with two ^ i.e. '''^^areaname2'''. These hidden quests will not show up as blank lines but are entirely undetectable. See any other quests lists for examples.<br />
<br />
==SEDIT==<br />
coming soon<br />
<br />
Avoid making new socials simply for entertainment purposes, as this will add more clutter to the socials list, which is utilized by players to maneuver through rooms, puzzles or quests at times. Existing social commands are for the most part set in stone. Changing existing output can cause quests to fail activation. If a condition arises where the syntax should indeed be changed, an admin should run a find and replace for relevant mprog triggers.<br />
<br />
==GEDIT==<br />
coming soon<br />
<br />
Edits clans: will probably change dramatically in the future as clan code is changed.</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Economy&diff=2508Economy2019-11-29T17:00:45Z<p>Pascal: /* Just the Equipment Upgrades */</p>
<hr />
<div>The Economy of the Cleft is diverse and varied, owing primarily to the diverse and varied resources in the world and the diverse and varied peoples that use them.<br />
<br />
== Towns of the Cleft ==<br />
Not all shops shall be listed here. Some that are intentionally left off the list are "Secret/Hidden" shops or those not in towns.<br />
<br />
General Store = variety of items<br />
<br />
Artifice Store = items like wands or scrolls<br />
<br />
=== Lvl 1-30 Areas Closer to Truce ===<br />
<br />
====[[Truce]] - Starting Town:====<br />
*IMPORTS - Newbies, Cloth, Weapons, Medicines<br />
*EXPORTS - Adventurers, Tourism, Clothing, Labor<br />
*Recall, Bank, Inn, Healer and Morgue Services<br />
<br />
Tent of Warfare - Armor (light) [lvl 10]<br />
<br />
Tent of Subsistence - General Store<br />
<br />
Moogle Trader - General Store<br />
<br />
Tent of Medicines - Recovery Items<br />
<br />
Tent of Wonders - Artifice Items<br />
<br />
Truce Bar - Restaurant<br />
<br />
Hut of Animal Husbandry - Pets<br />
<br />
====[[Crysta]]:====<br />
*IMPORTS - Labor<br />
*EXPORTS - Grain, Cloth, Medicines<br />
<br />
Merchant - Weapons [lvl 5] and Recovery Items<br />
<br />
Weaver's Hall - Magic Armor [lvl 15]<br />
<br />
Magishop - Recovery and Artifice Items<br />
<br />
Golem Workshop - Pets<br />
<br />
Jimmy's Bait and Tackle - Fishing Gear<br />
<br />
====[[Rocket Town]]:====<br />
*IMPORTS - Labor, Metal<br />
*EXPORTS - Machinery, Weapons<br />
*Inn Service<br />
<br />
Weapons Store - Weapons [lvl 10]<br />
<br />
Armor Shop - Armor [lvl 15]<br />
<br />
Items Shop - General Store<br />
<br />
Mindy's Mine Shop - Mining Gear<br />
<br />
====[[Wutai]]:====<br />
*IMPORTS - Iron, Cloth<br />
*EXPORTS - Grain (Rice), Tourism, Tea, Silk <br />
*Bank Service<br />
<br />
Weapon Shop - Weapons [lvl 15]<br />
<br />
Armor Shop - Armor (medium and heavy) [lvl 20]<br />
<br />
Item Shop - General Store<br />
<br />
Bits and Pieces - General Store<br />
<br />
Magishop - Artifice Items<br />
<br />
Turtle's Paradise - Restaurant<br />
<br />
Altamira Boardwalk - Entertainment<br />
<br />
====[[Saturn Valley]]====<br />
*IMPORTS - Ducks, Ribbon<br />
*EXPORTS - Peanut Cheese Bars<br />
*ATM, Healer Services<br />
<br />
Inside a Store - General Store<br />
<br />
====[[Cosmo Canyon]]:====<br />
*IMPORTS - Grain, Cloth<br />
*EXPORTS - Clothing, Weapons, Stone<br />
*Inn Service<br />
<br />
Tiger Lily Arms Shop - Weapons [lvl 20 + one lvl 35]<br />
<br />
Tailor's Shop - Armor (medium) [lvl 30]<br />
<br />
Lifestream - Recovery Items<br />
<br />
Materia Shop - Artifice Items<br />
<br />
Starlet Pub - Restaurant<br />
<br />
----<br />
<br />
=== Lvl 1-30 Areas Closer to Viorar ===<br />
<br />
====[[Viorar]] - Starting Town:====<br />
*IMPORTS - Grain, Cloth, Lumber<br />
*EXPORTS - Iron, Seafood, Gems, Minerals, Books<br />
*Recall, Bank, Inn, Healer and Morgue Services<br />
<br />
El Hazardous - Weapons [lvl 10]<br />
<br />
Armor Emporium - Armor (light) [lvl 5-10)<br />
<br />
Reckless Abandon - General Store<br />
<br />
Woodfall - Recovery Items<br />
<br />
Tatl Tael - Artifice Items<br />
<br />
Mummy Seeker - Artifice Items<br />
<br />
Lucky 8 - Food<br />
<br />
Mischievous Spirit - Restaurant<br />
<br />
Limelight - Light Sources<br />
<br />
Inuki's - Pets<br />
<br />
Cindy's Mine Shop - Mining Gear<br />
<br />
====[[Douglas Island]]====<br />
*IMPORTS - Machinery<br />
*EXPORTS - Fish<br />
<br />
Timmy's Bait and Tackle - Fishing Gear<br />
<br />
====[[Monstro Town]]====<br />
*IMPORTS - Books, Fine Art<br />
*EXPORTS - Pacifism, Fine Art<br />
<br />
Goom-Mart - Weapons [lvl 5], General Store<br />
<br />
====[[Fort Walla Walla]]====<br />
*IMPORTS - Metal, Weapons, Cattle<br />
*EXPORTS - Security, Tourism<br />
<br />
Blacksmith - some Weapons [lvl 10]<br />
<br />
Dry Goods - General Store<br />
<br />
====[[Arlia]]====<br />
*IMPORTS - Produce<br />
*EXPORTS - Alcohol, Gold, Minerals<br />
*Bank and Inn Service<br />
<br />
Hardware Store - some Weapons [lvl 25], Armor (heavy) [lvl 30]<br />
<br />
Drug Store - Recovery Items <br />
<br />
Love Delicatessen - Restaurant<br />
<br />
Lanky's Saloon - Alcohol<br />
<br />
====[[Tonoe]]====<br />
*IMPORTS - Labor, Machinery<br />
*EXPORTS - Cloth, Dairy, Medicines, Produce<br />
*Inn Service<br />
<br />
Atelier Saibara - Weapons [lvl 30]<br />
<br />
Hearty Lyla - Armor (light) [lvl 25], Recovery Items, General Store<br />
<br />
Cafe Callaway - Restaurant<br />
<br />
???? - Resistance Earrings<br />
<br />
----<br />
<br />
=== Areas Above Lvl 30 ===<br />
<br />
====[[Shrike]]====<br />
*IMPORTS - Grain, Iron<br />
*EXPORTS - Medicines, Machinery<br />
*Recall and Bank Services<br />
<br />
Bushmaster Sporting Goods - Various Level 35 Equipment<br />
<br />
Nakajima Robotics - Pets<br />
<br />
Lu Bu Feng Xian's Chinese Takeout - Restaurant<br />
<br />
Fruit Vendor - Food<br />
<br />
Quickstop - Food<br />
<br />
====[[Brei]]====<br />
*IMPORTS - ???<br />
*EXPORTS - Lumber<br />
<br />
====[[Mandala]]====<br />
*IMPORTS - Books, Clothing<br />
*EXPORTS - The Future?<br />
*Inn Service<br />
<br />
Watts' Forge - Weapons [lvl 40]<br />
<br />
Mr. Mito's Shop - General Store<br />
<br />
Happy Mask Shop - Masks<br />
<br />
====[[Dry Dry Outpost]]====<br />
*IMPORTS - Machinery, Produce<br />
*EXPORTS - Transportation, Tourism<br />
<br />
Item Shop - General Store<br />
<br />
Pawn Shop - Artifice Items<br />
<br />
Fruit Stand - Food and Drink<br />
<br />
====[[Caspia]]====<br />
*IMPORTS - Clothing, Food, Machinery, Seafood<br />
*EXPORTS - Gems<br />
*Recall, ATM Services<br />
<br />
Armoury Plaza - Armor (light) (heavy) [lvl 50]<br />
<br />
Flower Stand - Flowers<br />
<br />
Crystal Stand - Artifice Items<br />
<br />
Yoshimi's Jewelry - Resistance Necklaces<br />
<br />
The Blue Moon - Restaurant<br />
<br />
====[[Lasacul]]====<br />
*IMPORTS - Books, Produce<br />
*EXPORTS - Water, Medicines, Fish<br />
*Recall, Bank, Inn, Healer, Morgue Services<br />
<br />
====[[Todo]]====<br />
*IMPORTS - Clothing, Weapons<br />
*EXPORTS - Lumber, Medicines<br />
*Recall Service<br />
<br />
Mammoth Discounts - General Store<br />
<br />
Savoonga Diner - Restaurant<br />
<br />
====[[Brigantes]]====<br />
*IMPORTS - Books, Candles, Halloween decorations<br />
*EXPORTS - Candy, Gold, Gemstones, Wands, Potions<br />
*Bank Service<br />
<br />
Pin's Armor Emporium - Armor (light) [lvl 60]<br />
<br />
Pip's Pawn Shop - General Store<br />
<br />
Alanna's Alchemy - Recovery Items<br />
<br />
Studious Scribbery - Scrolls<br />
<br />
Creepy Confectionary - Food<br />
<br />
Killer Kitchen - Food<br />
<br />
Resting Rat - Alcohol<br />
<br />
The Witch's Wart - Alcohol<br />
<br />
Monstrous Menagerie - Pets<br />
<br />
Enchanted Evenings - Item Enhancements<br />
<br />
Fiendish Forge - Item Crafting<br />
<br />
====[[Gigantos Stronghold]]====<br />
*IMPORTS - Water, Weapons<br />
*EXPORTS - None<br />
<br />
Merchant - Weapons (twohands) [lvl 60]<br />
<br />
Classroom - Pets<br />
<br />
====[[Gold City]]====<br />
*IMPORTS - Cloth, Clothing, Silk, Tea, Seafood, Medicines, Machinery, Gems, Minerals, Books, Slaves<br />
*EXPORTS - Gold, Slaves<br />
*Bank and Inn Service<br />
<br />
Market Stall - Weapons [lvl 60]<br />
<br />
Hole-in-the-wall Market - Armor (light) [lvl 70]<br />
<br />
Original Moti Market - General Store<br />
<br />
Gepetto's Toy Shop - Toys<br />
<br />
Poppy and Palahniuk's - Jewelry<br />
<br />
The Mad Hatter - Restaurant that also sells Decorative Headgear<br />
<br />
== Just the Equipment Upgrades ==<br />
<br />
{| border="1"<br />
|+ Locations of Full Armor and Weapon Shops<br />
|- <br />
! Level<br />
! Light Armor<br />
! Medium Armor<br />
! Heavy Armor<br />
! Weapons<br />
|-<br />
| 5 || || [[Crysta]] <br> [[Viorar]] || || [[Crysta]] <br> [[Monstro Town]]<br />
|-<br />
| 10 || || [[Truce]] <br> [[Viorar]] || || [[Rocket Town]] <br> [[Viorar]]<br />
|-<br />
| 15 || || [[Rocket Town]] || || [[Wutai]]<br />
|-<br />
| 20 || [[Wutai]] || [[Wutai]] || || [[Cosmo Canyon]]<br />
|-<br />
| 25 || [[Mabe Village]] <br> [[Tonoe]] || || || [[Arlia]] (some)<br />
|-<br />
| 30 || [[Cosmo Canyon]] || Arlia || || [[Tonoe]]<br />
|-<br />
| 35 || || || || [[Alfador Isle]]<br />
|-<br />
| 40 || || [[Brei]] || [[Brei]] || [[Mandala]]<br />
|-<br />
| 50 || [[Caspia]] || [[Lasacul]] || Caspia || Lasacul<br />
|-<br />
| 60 || || [[Brigantes]] || || [[Gigan Hold]] <br> [[Gold City]]<br />
|-<br />
| 70 || || [[Gold_City]] || ||<br />
|}<br />
<br />
*No Upgrade Shops will exist beyond 70<br />
*Medium Armor - normal defensive armor<br />
*Light Armor - weaker defensive armor but with some stat bonuses<br />
*Heavy Armor - stronger defensive armor but with some stat penalties<br />
<br />
==Global Economy==<br />
The Cleft, despite its often high level of technology, does not appear to have an extremely high volume of trade. As such, Cleft economies do not usually have a high degree of specialization. While every town has its imports and exports, all towns have some degree of self-sufficiency. Due to the high volume of monsters and invading armies that tend to roam the countryside, relying on distant areas for vital supplies would be suicidal for most areas. The diversification of Cleft economies can be seen in that almost all towns have a general store which sells most essential supplies.<br />
<br />
Due to their proximity and the relative safety of the routes between them, there is a high volume of trade between Truce, Wutai, Crysta, and Rocket Town. Shrike, too, is only a port away from Truce.<br />
<br />
'''ADD MORE INTERCONNECTED REGIONS HERE'''<br />
<br />
===Currency===<br />
<br />
*''See the main article at [[Money]]''<br />
<br />
== Treasures ==<br />
<br />
The Cleft is full of many rare ores and minerals. All of these are found by miners and their cost reflects their rarity. Sometimes you may be rewarded these items for doing good deeds or as a rare monster drop. The names reflect the location they were initially discovered by the Cleft denizens, but do NOT reflect where you are most likely to find it.<br />
<br />
Names of Items subject to change when we have more places to name them after.<br />
<br />
{| border = 1<br />
! Value !! Name !! Mining !! Drops !! Quests !! Sea Chests !! Forge Implemented?<br />
|-<br />
| 1 || Altamira Zinc || X || || || X || X<br />
|-<br />
| 50 || Bequerel Copper || X || X || || X || X<br />
|-<br />
| 100 || Cosmo Brimstone || X || || || || X<br />
|-<br />
| 500 || Tonoe Manganese* || X || || || ||<br />
|-<br />
| 1000 || Smaskifa Bronze* || X || X || || ||<br />
|-<br />
| 2500 || Shrike Iron || X || X || || || X<br />
|-<br />
| 5000 || Pedan Wood || || X || X || || X<br />
|-<br />
| 10000 || Gold City Gold || X || || X || X ||<br />
|-<br />
| 15000 || Shasras Steel || X || || X || X || X<br />
|-<br />
| 20000 || Lorien Silver* || || || X || X ||<br />
|-<br />
| 30000 || Brigantes Gold || || || X || X || X<br />
|-<br />
| 40000 || Zurvan Platinum || || X || X || X ||<br />
|-<br />
| 50000 || Iktoa Mithril || X || || X || X || X<br />
|-<br />
| 60000 || Lasacul Alloy || || X || X || X || X<br />
|-<br />
| 70000 || Magicant Rock || || X || X || X ||<br />
|-<br />
| 80000 || Nosgoth Obsidian || X || || X || X ||<br />
|-<br />
| 90000 || Zanarkand Diamond || || || || X ||<br />
|-<br />
| 100000 || Rune Metal || ? || ? || ? || ? || ?<br />
|-<br />
|}<br />
<br />
Starred Names* subject to change<br />
<br />
== [[Player Housing]] ==<br />
<br />
== [[Clan Halls]] ==</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Oset_and_mset_tips_and_tricks&diff=2502Oset and mset tips and tricks2019-11-20T14:55:21Z<p>Pascal: /* GENERAL */</p>
<hr />
<div>This page contains tips and tricks for the commands oset and mset, it is not a fully detailed, exhaustive guide. These commands are considered to be more advanced and a good grasp of mobprogs should be obtained before attempting to utilize most of the applications written below. Oset and mset were only implemented to a certain degree. Any information herein may become inaccurate if either command are updated or changed in some way.<br />
<br />
<br />
== GENERAL ==<br />
<br />
<br />
There are a lot of things to keep in mind for all potential applications of mset and oset.<br />
<br />
Oset does not work on vnums and must specifically target a name keyword (or variable, as in event item progs). If the name keyword is too vague and shared by other items in the room or the player's or mob's inventory, oset could set the wrong item. Oset typically smartly targets the "closest" item to the mob using it, I.e. if the item is in the mob's inventory (and is the only item in existence with that name keyword) it will probably definitely oset the right item. You can also use "mob mforce ($n or $q) mob oset <item name>" as this will target the "closest" item to the player, as they are the one osetting the item. Alternately, if the item can be dropped, it can be given to the mob to oset and given back. Remember these oset item keywords will share keywords with identical items carried by separate players!<br />
<br />
If the item will need to be "mob remove"'d, remember to give it a unique name keyword and to not use the vnum, as you may mob remove the wrong item.<br />
<br />
Use "help oset" and "help mset" to remember which fields can be oset and mset. Remember unlike string, oset and mset replaces the variable entirely. If the object name it started with is not repeated in the oset command, it will lose that name keyword. Typically I use a temporary name on the base item with "osetitem" or some variation, to both indicate to anyone looking at the item in the obj editor that the item's final intended form is oset in the prog that creates it, as well as ensuring there are no other items in the game with that name keyword to be accidentally oset. Make sure to keep track of your oset item's name keywords - if you oset the name before you're done osetting other parts, you'll need to change the target name keyword for the remaining commands, as well as any following commands (give, wear, etc.).<br />
<br />
The "type" of an item cannot be oset! You cannot turn a potion into a sword, for example.<br />
<br />
When using mset, mobs can only mset themselves. This is easily bypassed by using "mob force" commands i.e. "mob force (target mob) mob mset (target mob)" if a separate mob is the one running the prog. Obviously if the target mob is msetting itself it can just mob mset $i.<br />
<br />
== VARIOUS CREATIVE APPLICATIONS ==<br />
<br />
<br />
Oset and mset allow a lot of creativity and new types of mechanics! Here are some of the things you can do with them.<br />
<br />
<br />
== UPGRADING EXISTING ITEMS ==<br />
<br />
<br />
Allow players to add strong, meaningful upgrades their existing items, including not only additional stats but upgrading the base values (and level) of the item itself. This could be through event type items or quest rewards.<br />
<br />
When using oset to upgrade existing items: if using an event item, ensure that the object being upgraded is represented by the 'target object' variable. The player will need to use the event item on the target upgrade item. When using oset on an item forcibly, as in occurring through a prog as a quest reward or what not, ensure that the item being oset has a unique name keyword. Remember other players may have this same item keyword! When upgrading existing items that may share keywords with objs other players in the room may be carrying (if players quest together and are grouped etc) it is safest to give the item to the mob (use an owned flag if you don't want the item to be able to be given away) to have them oset it to avoid osetting the wrong item.<br />
<br />
<br />
== RANDOM CHANCE TO UPGRADE ITEMS ==<br />
<br />
<br />
Create varied and random drops of the same item without creating a different object vnum for each variation. For example, using 'if rand' commands to give a weapon a chance to have a poison weapon flag or a leaf weapon flag. It is even possible to make event items with stronger or weaker uses by utilizing the name field of the item combined with "if name" checks.<br />
<br />
When using oset to make random attributes, remember the details of the base object. You can reduce the amount of characters in your prog if there is a stat you want to be on all of the potential variations, just make the base item as complete as possible. You may want to add a name keyword identifier that indicates the item is oset or that that specific item was randomly generated to be better, for example "broadsword sword _osetupgraded" so that when the item is stat'd or searched, you can tell it benefited from an RNG upgrade. This is also necessary if you're making an upgraded event type item that you want to have a better chance to work well, or have a chance to do something that the non-upgraded version doesn't, by using this keyword in the manner of "if name $p _osetupgraded" before your special application within the event's prog.<br />
<br />
''Example:''<br />
<br />
if rand 25<br />
mob oset =osetdagger v4 vorpal<br />
endif<br />
<br />
The above example creates an if rand 25 chance to make the weapon add the special weapon flag of 'vorpal'. <br />
<br />
Mpdump 8461 for an example of an event item that becomes oset to be better or worse.<br />
<br />
== SCALE MOBS/PETS TO PLAYER'S LEVEL ==<br />
<br />
<br />
Make mobs that scale with the player's level. This can require very long progs depending on how wide of a scale you want. This would be valuable for special event or arena type areas where you want a large number of players to be able to participate regardless of their level, or if you don't want a player to be able to muscle through a combat oriented quest with a valuable reward by over leveling it (or making harder, remort versions of existing fights!) This is also good for making pets scale with their master's level. This level scaling potential includes the stats of the mobs as well, so they scale realistically! This is an advanced application, be mindful!<br />
<br />
There are a large number of things to consider and know in regards to making mobs scale with level or "level up".<br />
<br />
First of all, for a mob to actually realistically scale, you will need to do more than set its level to the level of the target/master. Setting the level of the mob to the player/targets level is done by making the mob remember the intended scale target and using 'mob mset $i level $B', $B being the level of the mob remember target. You can also only scale it at certain intervals if desired, with if level $n >= xx etc. checks.<br />
<br />
You can just make the mob level up, which will do some things, but not increase its health, mana, moves, stats or increase any 'mob damage' or 'mob damecho' numbers. It WILL make any spells it uses increase in power, it will fair better against higher level foes in melee combat in regards to dodge/parry, and obviously allow it to use higher level armor. It is more feasible to scale every 5 or every 10 levels for stats on the mob, depending on how wide of a level range you'd like. If you want them to use a mob damecho/damage command that also scales, that mob damecho/damage command will have to have if level $i >= xx checks each time to make it better according to the mob's level, meaning a mob that levels up a lot could have a very long fight prog!<br />
<br />
Mset itself cannot add all of the stats typically considered necessary for a realistic scale, and oset cannot change the level or maxhp of a mob, thus making mset and oset both necessary for detailed, advanced scaling. For bosses, having it oload the item and ensuring the item is removed upon the mob's death is also easily accomplished. Unless the item seems relevant to the boss fight, perhaps a warrior swapping weapons, you may want the item to be inert so that the player will not see it when looking at the mob in question. <br />
<br />
There are two very important things to keep in mind when using this application. First of all, when osetting a piece of equipment, the changes do not affect the mob until the item is removed and re-equipped. This does not apply to VALUES but does apply to any affects (added with 'add' or 'apply'). Second of all, if you mset the maxhp, maxmana, or maxmove of a mob that is currently wearing armor that affects the hp, mana, or move of that mob, the result is NOT a total of (new maxhp/mana/move) + (benefit from armor), but rather the the benefit from the armor becomes part of the maxhp/mana/move of the mob. This means that if you have a piece of armor that increases hp by 500 and you mset the maxhp to be 1000, removing that piece of armor will result in 500 hp. ALSO NOTE: This can cause removal of armor to put the mob's HP below 0, putting it into a "dead" stasis that can only be fixed by immortal intervention. In practice, this means, don't mset the maxhp/mana/move of a mob that has any chance of wearing armor, i.e., a pet.<br />
<br />
For an example of this application with a pet that scales from 1 to 100, mpdump 7917.<br />
For an example of this application with a boss that scales from 50 to 100, but only gains stats at three different intervals, mpdump 8495.<br />
<br />
== COMPLEX BOSS PHASES ==<br />
<br />
<br />
Allow bosses (or any mob!) to change their stats on the fly for phases. It was already possible to add and remove affects, shields, and extra flags, but now you can also change their mana pools, health pools, damroll, magroll, hitroll, etc. without having to make new mob vnums for each phase.<br />
<br />
You can reliably and forcibly heal your mob by using mset maxhp and mset hp. If you wish to increase the total HP of the mob for a phase swap, but still keep it "damaged", simple mset the maxhp and then determine how much they should have left for the mset hp line. Obviously ensure this doesn't happen over and over, so that the mob is actually defeatable (unless it's not supposed to be!). The information under "mob scaling" in relation to setting different stats for a phase swap apply the same way.<br />
<br />
For an example of a boss phase swap using oset and mset, mpdump 8496 (8496 is called from fight prog 8490 for a more complete picture). Note this example is also a scaling boss.<br />
<br />
== BETTER EFFICIENCY USING SKILLS ==<br />
<br />
<br />
Allow pets or mobs to temporarily increase their level to be more successful at using skills. It was previously possible to use different leveled spells by utilizing scrolls and artifice, but since skills could not be put into scrolls, it was not possible to use them at greater efficiency.<br />
<br />
This is simply done by temporarily msetting the mob's level before the use of the skill, then returning it back immediately after the skill is executed. If the mob ALSO scales, you will need to make an individual 'if level $i == xx" check for each possible level of the mob before this sequence in order to return it to the accurate level!<br />
<br />
For an example of this application on a pet, mpdump 8430. This example pet is also a scaling pet.<br />
<br />
== SAVE ON VNUMS ==<br />
<br />
<br />
One of the simplest applications is using oset to make a wide variety of similar items without needing to use a large number of vnums. Be wary of overusing this application, as each type of osetted item will not appear in a vnum (name) search, making your osetted items hard for other immortals to find in case of potential problems! I would recommend making batches of similar items, and using new vnums for different areas or different applications of items. The vnum of the object will still be visible when the item is stat'd, but it may be a decent idea to add a name keyword into the object referencing the mprog where it is created.<br />
<br />
For an example of this oset application, mpdump 8445.<br />
<br />
== MAKE THINGS OWNED ==<br />
<br />
<br />
It is also possible to utilize another new item flag, "owned", with oset: when osetting the name field of the item you'd like to be "owned", ensure the variable representing the name of the player (either $n or $q) is present. ''Ex: mob oset (item) name (desired name keywords) $n'' Owned means only that player can equip it, allowing you to make strong quest items that can be dropped without worrying about someone who did not complete the quest picking it up and using it. You can also make unique items for unique pets as well, that even the owner can't wear! It also functions as an ID for the item if it gets dropped by accident!<br />
<br />
The owned flag is an extra3 flag. <br />
<br />
This does mean the item will be stat obj and searchable using the name of the player, so any owned equipment will show up in an "owhere (player name)" search.</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Flags_Compendium&diff=2488Flags Compendium2019-11-05T19:38:46Z<p>Pascal: /* ACT FLAGS */</p>
<hr />
<div>==FLAGS COMPENDIUM==<br />
===ROOM FLAGS===<br />
{|<br />
|dark || Need a light source <br />
|-<br />
|always_night || Room is always night; sun never rises, 'look sky' always shows stars.<br />
|-<br />
|no_mob || Mobs won't wander in here. Mobs on scripts and charmies are unaffected<br />
|-<br />
|indoors || Won't see [[weather]] or [[time|sunrise/set messages]]<br />
|-<br />
|private || Two people at a time<br />
|-<br />
|arena || Players don't leave corpses or lose XP when they die. Players also don't lose XP for fleeing combat.<br />
|-<br />
|safe || No fighting allowed<br />
|-<br />
|solitary || One person at a time<br />
|-<br />
|pet_shop || Can buy pets here. Pet cost is the 'wealth' of the mob, but purchased pets will be flat broke. Builders should reset the pet mobs into next room vnum.<br />
|-<br />
|no_recall || Can't recall from here<br />
|-<br />
|imp_only || MTS only<br />
|-<br />
|gods_only || Staff only<br />
|-<br />
|heroes_only || Also Staff only<br />
|-<br />
|newbies_only || Level 5 or less only<br />
|-<br />
|law || Prevents use of Charm, Tame, and Hypnotize spells (for some reason). Other stock ROM effects have been commented out.<br />
|-<br />
|nowhere || Can't Scan into this room<br />
|-<br />
|wilderness || Was supposed to involve some sort of overworld map? Doesn't do anything now.<br />
|-<br />
|overgrown_1 || Room has +1 level of overgrowth.<br />
|-<br />
|overgrown_2 || Room has +2 levels of overgrowth. This can stack with overgrown_1.<br />
|-<br />
|always_day || Room is always day; sun never sets, 'look sky' shows the sun.<br />
|-<br />
|lit || Room is always lit, don't require a light.<br />
|}<br />
====SECTOR====<br />
{|<br />
!Sector !! Movement Rate !! Properties !! Geomance Element !! Dance Element<br />
|-<br />
|Inside || 4 || Stays lit at night || Pierce || No effect<br />
|-<br />
|City || 4 || Stays lit at night || Bash || No effect<br />
|-<br />
|Field || 4 || || Slash || Pierce<br />
|-<br />
|Forest || 6 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Hills || 6 || || Slash || Pierce<br />
|-<br />
|Mountain || 8 || || Earth || Earth<br />
|-<br />
|Water (swim) || 4 || || Water || Water<br />
|-<br />
|Water (noswim) || 8 || Can't enter without a boat or the Swim affect || Water || Water<br />
|-<br />
|Unused || 1 || || Wind || No effect<br />
|-<br />
|Air || 4 || Can't enter without the Float affect || Wind || Wind<br />
|-<br />
|Desert || 8 || || Earth || Wind<br />
|-<br />
|Rock || 4 || || Earth || Earth<br />
|-<br />
|Road || 4 || || Wind || No effect<br />
|-<br />
|Enter || 4 || || Wind || No effect<br />
|-<br />
|Snow || 8 || || Cold || Cold<br />
|-<br />
|Swamp || 8 || || Water || Earth<br />
|-<br />
|Jungle || 8 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Ruins || 4 || || Bash || No effect <br />
|-<br />
|Mount2 || 16 || || Earth || No effect<br />
|-<br />
|Coastal || 4 || || Earth || Wind<br />
|-<br />
|Developed || 4 || || Bash || No effect <br />
|-<br />
|Void || 4 || || Wind || No effect<br />
|-<br />
|Lava || 8 || || Fire || Fire<br />
|}<br />
<br />
====[[Exits|EXITS]]====<br />
{|<br />
|door || Exit has a door -- Required for most other exit flags<br />
|-<br />
|closed || Door resets to closed<br />
|-<br />
|locked || Door resets to locked<br />
|-<br />
|pickproof || Door can't be picked<br />
|-<br />
|nopass || Door can't be Pass Door'd<br />
|-<br />
|easy || Pick Lock doesn't take many tries<br />
|-<br />
|hard || Pick Lock takes a few tries<br />
|-<br />
|infuriating || Keep pickin'<br />
|-<br />
|noclose || Door can't be closed<br />
|-<br />
|nolock || Door can't be locked<br />
|-<br />
|hidden || Exit can't be seen by normal means<br />
|-<br />
|swim || Only players who can fly or swim, or are on a flying or seaworthy [[vehicle]] can pass.<br />
|-<br />
|fly || Only players who can fly or are on a flying [[vehicle]] can pass.<br />
|}<br />
<br />
===MOB FLAGS===<br />
*Mobs with the None [[damage type]] will randomly have Slash, Pound, or Pierce.<br />
<br />
====FORM FLAGS====<br />
Most of these don't do anything. The ones that have a coded effect are listed below!<br />
{|<br />
|edible || Mob's parts are edible, and the corpse can be butchered into meat.<br />
|-<br />
|poison || Mob's edible parts are poisonous, and meat butchered from the corpse will be poisoned. Bloodsucking will poison the bloodsucker.<br />
|-<br />
|instant_decay || Mob doesn't leave a corpse at all. (Note: This means items on the mob are lost as well.)<br />
|-<br />
|animal || Mob is affected by the Tame spell.<br />
|-<br />
| || Mobs with any of the mammal, bird, reptile, amphibian, fish, or snake form flags can also be Tamed.<br />
|-<br />
|sentient || Mob is affected by the Hypnotize spell and can be haggled with if it's a shopkeeper.<br />
|-<br />
|undead || Mob takes extra non-elemental damage from weapons with disrupting weapon flag.<br />
|-<br />
|cold_blood || Mob has blood that can be bloodsuck'd.<br />
|-<br />
|warm_blood || Mob can be seen in the dark by characters with Infrared and can be bloodsuck'd.<br />
|}<br />
<br />
====PART FLAGS / WEARLOCS====<br />
Mob parts determine what equipment it can wear.<br />
<br />
{| <br />
! Wearloc !! Required Part flag<br />
|-<br />
|take || none<br />
|-<br />
|finger || fingers<br />
|-<br />
|neck || head<br />
|-<br />
|body || guts<br />
|-<br />
|head || head<br />
|-<br />
|legs || legs<br />
|-<br />
|feet || feet<br />
|-<br />
|hands || hands<br />
|-<br />
|arms || hands<br />
|-<br />
|shield || hands<br />
|-<br />
|about || guts<br />
|-<br />
|waist || legs<br />
|-<br />
|wrist || hands<br />
|-<br />
|shoulders || head<br />
|-<br />
|wield || hands<br />
|-<br />
|hold || hands<br />
|-<br />
|nosac || not actually a wearloc<br />
|-<br />
|wearfloat || none<br />
|-<br />
|face || head<br />
|}<br />
<br />
* The Brawling warrior style has special attacks that only execute if the opponent has certain parts; eye, tail, feet, or arms.<br />
* The guts, head, heart, arms, legs, and brains parts can cause dismembered mob organs to be created when the mob dies.<br />
* A mob requires the brains part in order to take any damage from the Brainbuster spell.<br />
* '''A mob without hands cannot hold items, use weapons, or equip shields.'''<br />
* Items which do not have the Take flag can't be sacrificed, so it is redundant to put nosac on these items also.<br />
* Items without a Take flag can't be held by players or mobs at all. Avoid resetting these onto mobs or trying to have mobs oload them.<br />
<br />
====ACT FLAGS====<br />
{|<br />
|sentinel || Mob won't wander between rooms (although it can still move if instructed to by an mprog).<br />
|-<br />
|scavenger || Mob will pick up takeable objects in the room, starting with the most valuable.<br />
|-<br />
|inert || Mob can't be seen in the room (but can still be interacted with).<br />
|-<br />
|omnisight || Mob can see everyone despite invisibility etc but can't necessarily see in the dark.<br />
|-<br />
|aggressive || should target a random PC, not more than 5 levels higher than the mob, chosen from an entire group entering the room at once - may be funky with portals<br />
|-<br />
|stay_area || Mob won't wander outside the area it was reset into.<br />
|-<br />
|wimpy || Mob will try to flee from combat at 20% hp or less.<br />
|-<br />
|pet || Mob is a pet? Probably reserved for pet code. Don't use this.<br />
|-<br />
|train || Players can Train at this mob -- defunct<br />
|-<br />
|practice || Players can Practice at this mob -- defunct<br />
|-<br />
|passive || Mob doesn't fight back with autoattacks, its current health isn't visible when you 'look' at it, nor will Peek work on it.<br />
|-<br />
|hyper || Mob wanders around real fast.<br />
|-<br />
|visdeath || Mob can only be seen by immortals and can't be interacted with by players.<br />
|-<br />
|mage || Mob gets -5 to Saves<br />
|-<br />
|thief || Mob has the Smokescreen skill<br />
|-<br />
|warrior || Mob has the Shield Block skill<br />
|-<br />
|noalign || Mob won't affect player alignment at all when killed.<br />
|-<br />
|nopurge || Mob can't be purged by immortals (the Mob Purge command from a mob can still affect these).<br />
|-<br />
|outdoors || Mob won't wander into Indoor flagged rooms.<br />
|-<br />
|indoors || Mob won't wander outdoors.<br />
|-<br />
|healer || Mob offers hardcoded heal-for-cash services (EG Selan).<br />
|-<br />
|gain || Doesn't do anything -- in stock ROM allows for gaining new skills.<br />
|-<br />
|update_always || Mob does things even when no player in the area. Avoid using this as it spikes CPU usage badly.<br />
|-<br />
|changer || Mob is a [[bank]].<br />
|-<br />
|hyper_res || Mob takes 1/4 damage from sources it resists (instead of 2/3) and double damage from sources it's vulnerable to (instead of 3/2).<br />
|}<br />
<br />
Notes on wandering mobs:<br />
* When mobs try to move, they make three attempts. Each attempt, they pick a random exit in the room and then look at it more closely. If they can't move, they try again. If they can move, they do.<br />
* Mobs will not wander through closed doors (even if affected by pass_door) or into no_mob rooms.<br />
* Mobs with the stay_area flag will not wander between areas (which area its' vnum is in doesn't matter).<br />
* Mobs with the Outdoors flag won't wander into Indoors rooms. Mobs with the Indoors flag won't wander into rooms that aren't flagged Indoors.<br />
* Only Flying mobs will move into Air sector rooms. Only mobs with the Swim affect will move into any sort of water room.<br />
<br />
====ACT2 FLAGS====<br />
{|<br />
|doublexp || Mob gives double XP.<br />
|-<br />
|halfxp || Mob gives half XP.<br />
|-<br />
|noxp || Mob gives no XP.<br />
|-<br />
|noparts || Mob leaves no parts when killed.<br />
|-<br />
|sociable || Mob talks to or slaps people that use socials on it.<br />
|-<br />
|aquatic || Mob won't wander outside water rooms.<br />
|-<br />
|xpandahalf || Mob gives 1.5x XP.<br />
|-<br />
|adept || Mob uses skills at 100% (instead of 75%).<br />
|-<br />
|inept || Mob uses skills at 50% (instead of 75%).<br />
|-<br />
|carryall || Mob has no weight or item# limits.<br />
|-<br />
|priority || Mob will be targetted first by opponents with the AI_1 flag.<br />
|-<br />
|antihyper || Mob wanders especially slowly.<br />
|-<br />
|parsename || Mob will have a unique name as its first name when it resets.<br />
|-<br />
|noattack || Mob can't be attacked by anyone.<br />
|-<br />
|necromancer || Mob offers corpse retrieval for cash services, as Xzar, Caroline, etc.<br />
|-<br />
|raidmob || Mob can be attacked by anyone with no regard to 'kill stealing'.<br />
|-<br />
|carrynone || Mob can't pick up or be given items<br />
|-<br />
|passivelite || Mob won't auto-attack but still has visible health and such<br />
|-<br />
|ally || Is treated as a PC for some attack-safety purposes -- EG Ally mobs won't hit other Ally mobs with area attacks<br />
|-<br />
|shopkeepitems || Shop will not slowly discard items sold to it.<br />
|}<br />
<br />
====OFF FLAGS====<br />
A lot of these are affected by the adept/inept Act flags<br />
{|<br />
|area_attack || Mob hits everything that's fighting it with its normal attacks.<br />
|-<br />
|backstab || Mob is capable of using the Backstab skill, and would if it aggroed, but mobs don't aggro, so it does nothing.<br />
|-<br />
|bash || Mob has a 12.5% chance of using the bash skill, if it's not lagged.<br />
|-<br />
|berserk || Mob has a 12.5% chance of using the berserk skill, if it's not lagged and isn't already berserk.<br />
|-<br />
|disarm || Mob has a 12.5% chance of using the disarm skill, if it's not lagged. The mob needs a [[weapon]].<br />
|-<br />
|dodge || Mob can dodge melee attacks as a player with the dodge skill at 75%.<br />
|-<br />
|fade || Doesn't do anything.<br />
|-<br />
|fast || Mob attacks twice always, doesn't stack with Haste. Mob will ignore Slow if affected. Mob gets +2 DEX when spawned.<br />
|-<br />
|kick || Mob has a 12.5% chance of using the kick skill, if it's not lagged.<br />
|-<br />
|dirt_kick || Mob has a 12.5% chance of using the dirt kick skill, if it's not lagged.<br />
|-<br />
|parry || Mob can parry attacks; works half as often with no [[weapon]].<br />
|-<br />
|rescue || Mob will try to rescue the target of its target, if that target is at 50% hp or less.<br />
|-<br />
|tail || Mob has a 12.5% chance of.. not doing anything (the code for this attack is commented out).<br />
|-<br />
|trip || Mob has a 12.5% chance of using the trip skill, if it's not lagged.<br />
|-<br />
|crush || Mob has a 12.5% chance of using the smash skill, if it's not lagged.<br />
|-<br />
|assist_all || Mob will assist all other '''mobs''' that it sees fighting.<br />
|-<br />
|assist_align || Mob will assist other mobs with a similar alignment, chunked out to good/neutral/evil.<br />
|-<br />
|assist_race || Mob will assist other mobs of the same race.<br />
|-<br />
|assist_players || Mob will assist players as long as the player isn't more than 5 levels above them. This has precedence over the other assist flags.<br />
|-<br />
|assist_leader || If following someone, mob will assist its leader.<br />
|-<br />
|assist_vnum || Mob will assist mobs of the same vnum.<br />
|-<br />
|second_attack || Mob has the 2x-Cut skill.<br />
|-<br />
|third_attack || Mob has the 3x-Cut skill.<br />
|-<br />
|ai_retargeting || Mob will aggro onto players that have recently fled from it, and selectively hit targets with the Priority act flag. If the mob's attacks are ineffective, it will re-target randomly to another member of the same group.<br />
|-<br />
|ai_flees || Mob will flee from sandstorms, flurries, miasmas, wildfires, etc unless it's immune to the appropriate damage type.<br />
|-<br />
|ai_rests || Mob will rest when injured (hp<50%), stand up when it's recovered (hp>75%).<br />
|-<br />
|}<br />
* Only one of the various 12.5% flags can trigger in any given round. A mob will all eight will try to use one (and only one) every single round.<br />
<br />
====BEHAV FLAGS====<br />
{|<br />
|random_innate || Mob randomly has one of the 6 elemental innates. This creates one resistance and one vulnerability.<br />
|-<br />
|rand_phys_resist || Mob randomly resists one of bashing, slashing, or piercing.<br />
|-<br />
|rand_misc_resist || Mob randomly resists one or two non-physical elements.<br />
|-<br />
|rand_phys_vuln || Mob is randomly vulnerable to one of bashing, slashing, or piercing.<br />
|-<br />
|rand_misc_vuln || Mob is randomly vulnerable to one or two non-physical elements.<br />
|-<br />
|travelingpet || Mob will automatically teleport to its master as long as it has one, and will otherwise despawn itself unless it is inside of a petshop room.<br />
|}<br />
<br />
====AFFECT FLAGS====<br />
{|<br />
|blind || Character can't see anything! Mobs ignore this flag so their mobprogs work<br />
<br />
|-<br />
|invisible || Character can only be seen and targetted by things with detect_invis.<br />
|-<br />
|detect_evil || Character sees evil objects and characters with a red aura.<br />
|-<br />
|detect_invis || Character can see invisible objects and characters, and knows they're invisible.<br />
|-<br />
|detect_magic || Character sees a blue aura around magical objects.<br />
|-<br />
|detect_hidden || Character can see hidden objects and characters, and knows they're hidden.<br />
|-<br />
|detect_good || Character sees good objects and characters with a gold aura.<br />
|-<br />
|sanctuary || Character is permanently under the effects of Nayru's Love (half damage from everything).<br />
|-<br />
|faerie_fire || Character has a pink aura. Negates invisibility.<br />
|-<br />
|infrared || Character can see warm_blood mobs in the dark.<br />
|-<br />
|curse || Character is flagged as cursed. All skill effectiveness is reduced by 15% while this flag is applied, but the character is immune to the Curse spell.<br />
|-<br />
|solidified || Character is completely frozen!<br />
|-<br />
|poison || Character is flagged as poisoned. This flag has no affect on stats but the character can't be poisoned again. Regeneration is decreased while this flag is applied, however.<br />
|-<br />
|protect_evil || Character takes 2/3 damage from evil foes.<br />
|-<br />
|protect_good || Character takes 2/3 damage from good foes.<br />
|-<br />
|sneak || Character doesn't generate echoes when moving from room to room. Triggers GRALL but not GREET progs.<br />
|-<br />
|hide || Character is hiding. Using any command removes this effect.<br />
|-<br />
|sleep || Character is under the effects of ''permanent'' magical sleep!!<br />
|-<br />
|charm || Character is under the effects of a Charm spell. Don't use.<br />
|-<br />
|flying || Character is flying: reduced MV costs everywhere (by 1 per room), can travel into air sector rooms, and doesn't need a boat to travel into noswim sector rooms. Also immune to Trip and Earthquake.<br />
|-<br />
|pass_door || Character can walk through some closed doors.<br />
|-<br />
|haste || Character is under the effects of Haste: '''always''' gets exactly 1 extra attack in combat, but regenerates at half speed. <br />
|-<br />
|calm || Character is under the effects of the Calm spell. Character can't use berserk.<br />
|-<br />
|plague || Character is flagged as plagued. Regeneration is decreased but the player can't be hit with the Bio 2 spell.<br />
|-<br />
|locusts || Character is a swarm of locusts per the Plague Swarm spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|dark_vision || Character can see anything in any kind of darkness without a light source.<br />
|-<br />
|berserk || Character is under the effects of Berserk! Character can't cast spells, everything the character sees is red, and they get a 50% penalty to all saving throws.<br />
|-<br />
|swim || Character doesn't need a boat to enter noswim sector rooms.<br />
|-<br />
|regeneration || Character regenerates HP twice as fast!<br />
|-<br />
|slow || Character has a chance to simply not attack during combat. 2x-cut and 3x-cut chances are reduced dramatically. Ignored if the mob is flagged off_fast. Character also regenerates at half speed AND spends more MV when traveling.<br />
|-<br />
|scarecrow || Character is affected by the Scarecrow spell -- can't eat, drink, or move, and melee attacks do reduced damage.<br />
|}<br />
<br />
====AFFECT2 FLAGS====<br />
{|<br />
|focus || double mana regeneration<br />
|-<br />
|motivation || slight movement regeneration<br />
|-<br />
|theatrical || takes damage when receiving an affect<br />
|-<br />
|frenzy || grants extra attack<br />
|-<br />
|vampirism || ??<br />
|-<br />
|paralysis|| ??<br />
|-<br />
|fast|| no command lag when moving rooms (like vehicle fast)<br />
|}<br />
<br />
====SHIELD FLAGS====<br />
{|<br />
|charge || Character does 1.5x damage with all applicable spells. DOES NOT DISSIPATE UNLESS IT IS APPLIED BY THE CHARGE SPELL.<br />
|-<br />
|sabotaged || Character takes damage when using skills or spells.<br />
|-<br />
|hallucinating || Character is under the effects of the Mushroomize spell; all MUD output turns wacky.<br />
|-<br />
|terrified || Character may cower helplessly in combat, with a greater chance is the foe's level is higher than the character's. Also makes the character try to flee.<br />
|-<br />
|haunted || Character is tormented by minighosts.<br />
|-<br />
|confused || Character hits itself sometimes in combat.<br />
|-<br />
|stat enhancement || Character is under the effects of one of Sage Aura, Brilliance, Limber, Valor, or Vigor/Warcry and can't be affected by another one.<br />
|-<br />
|ice shield || Returns 20 to 30% of melee damage as bash-type damage<br />
|-<br />
|thorn shield || Returns 20 to 30% of melee damage as pierce-type damage<br />
|-<br />
|crystal shield || Returns 20 to 30% of melee damage as slash-type damage<br />
|-<br />
|osmosis || Character loses MP steadily. Also decreases MP regeneration.<br />
|-<br />
|volta || Character does not auto-attack but has double normal dodge chances.<br />
|-<br />
|manashield || Character has Mana Shield permanently up. It will give the 'your shield broke' message with every attack if they're at 0MP but they'll still take full damage.<br />
|-<br />
|kamikaze || Character is going to Detonate. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|zeal || Character fails all saving throws but receives a bonus to damage for each bad affect<br />
|-<br />
|bleeding || Character loses HP steadily. Some types of bleeding make you bleed worse than others!<br />
|-<br />
|undead || Character is a zombie with a relentless hunger for delicious brains. All text is dark gray, healing spells do damage instead of healing, and the poor bastard doesn't necessarily die when they drop below 0hp! This is distinct from the undead form flag.<br />
|-<br />
|oozaru form || Character is an oozaru and can't cast spells.<br />
|-<br />
|double image || Character has a double image. It will take one attack and then vanish.<br />
|-<br />
|ink || Character has been inked. Display is all goofed up with large black splotches.<br />
|-<br />
|seraph form || Character has seraph form and can't cast spells.<br />
|-<br />
|reflect || Spells targetted at the character bounce back the wrong way<br />
|-<br />
|surefire casting || Character has surecasting on.<br />
|-<br />
|jinx || Character has a 33% chance of dropping any [[weapon]] they're wielding in any combat round.<br />
|-<br />
|leechseed || Character is under the effects of the Leech Seed spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bees || Character is covered in bees which deal periodic damage.<br />
|-<br />
|choke || Character is affected by Choke and casts spells at 3/4 the normal strength.<br />
|-<br />
|endure || Character cannot be reduced below 1hp.<br />
|-<br />
|sheltered || Character is being sheltered by a friendly Templar. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bide || Character is using the skill Bide. *Cannot be set on a mob's template or applied by an item.<br />
|}<br />
<br />
Some of these affects can't be applied to a mob's template, only by spells; homing attack, stat enhancement, extension, kamikaze, short term combat effect, oozaru form, double image, seraph form, Jumi empathy, surefire casting, and leechseed.<br />
<br />
===OBJ FLAGS===<br />
For more details on object types see [[Flags Compendium/Obj Types]]<br />
<br />
{|<br />
|[[light]] || Light sources, go in a special 'light' slot when equipped no matter what wear flags you use<br />
|-<br />
|[[scroll]] || Can be recited or read to cast 1-4 spells on a target. Works from base inventory, consumed when used, uses [[Artifice]] skill.<br />
|-<br />
|[[wand]] || Can be zapped or used to cast 1 spell a set number of times on a target. Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[staff]] || Can be brandished or used to cast 1 spell a set number of times on all targets in a room! Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[weapon]] || Changes wearer's melee autoattack damage to the type and amount specified in the object. Must be in the Wield slot to work.<br />
|-<br />
|[[treasure]] || No inherent properties, reserved for salable loot.<br />
|-<br />
|armor || Modifies wearer's armor values. Can be equipped anywhere.<br />
|-<br />
|[[potion]] || Can be quaffed or drunk to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|-<br />
|[[furniture]] || Various flags allow characters to sit, rest, stand, or sleep on, in, or at these objects. Recovery rates can be modified as well.<br />
|-<br />
|[[trash]] || No inherent properties, reserved for nonsalable loot.<br />
|-<br />
|[[container]] || Object that holds other objects. Can be closable/lockable like a door.<br />
|-<br />
|[[drinkcontainer]] || Holds a set quantity of a certain [[liquid]]. Liquids can be replaced with different liquids. Disappears when empty unless NOEXPLODE is set.<br />
|-<br />
|[[key]] || Object vanishes on logout. Has no other properties.<br />
|- <br />
|[[food]] || Can be eaten for food/full value and cast 1 spell on the eater.<br />
|- <br />
|[[money]] || Is abstracted into current wealth when picked up by a player. Dropped wealth turns into a money object. The Priest class can sacrifice money to recover mana for 1 MP per 50 silver.<br />
|- <br />
|boat || Can be equipped or in base inventory for players to move in water rooms. Defunct.<br />
|- <br />
|npccorpse || NPC [[Corpse]]. Reserved.<br />
|- <br />
|[[fountain]] || Like a drinkcontainer but the [[liquid]] inside can't be poisoned. Drinkcontainers can also be 'fill'ed from it.<br />
|- <br />
|[[pill]] || Can be eaten to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|- <br />
|protect || Uncoded junk. Don't use.<br />
|- <br />
|map || Uncoded junk. Don't use.<br />
|- <br />
|[[portal]] || Objects that can be 'entered' to take the character to a set room. Can be closable/lockable like a door.<br />
|- <br />
|warpstone || Used to be necessary for the Nexus spell.<br />
|- <br />
|roomkey || Uncoded junk. Don't use.<br />
|- <br />
|gem || Uncoded junk. Don't use.<br />
|- <br />
|[[jewelry]] || No inherent properties. Used for equippables that aren't armor.<br />
|- <br />
|[[Event Item|event]] || An object with both charges and cooldown capability, which executes an mprog when 'zap'ped or 'use'd. Uses [[Artifice]] skill.<br />
|- <br />
|slotmachine || <s>Type "Game slots" at a slot machine to spin the wheel. Slot machines can have their cost and jackpot size specified in the object template.</s> Just kidding! Disabled.<br />
|- <br />
|gun || Uncoded junk. Don't use.<br />
|- <br />
|ammo || Uncoded junk. Don't use.<br />
|- <br />
|[[vehicle]] || Vehicles allow players to consume less movement points as they travel, move faster, and/or travel to rooms they can't enter on foot.<br />
|- <br />
|exit || Uncoded junk. Don't use. Not the same as a real [[exit]].<br />
|- <br />
|[[rod]] || Can be zapped or used to cast 1 spell on a target with a set delay between uses. Must be equipped, any slot is OK. Uses [[Artifice]] skill.<br />
|}<br />
====EXTRA FLAGS====<br />
{|<br />
|glow || Item can be seen in the dark, shows (glowing) before its short desc<br />
|-<br />
|hum || Item shows (Humming) before its short desc<br />
|-<br />
|norecharge || Wand, staff, rod, or event can't be recharged with the Recharge spell. Weapon or armor can't be enchanted. Light can't be recharged with the Phlogiston spell.<br />
|-<br />
|autoconsume || Item is automatically used as soon as it's picked up off the ground. Works with [[potions]], [[pills]], and [[artifice]] items.<br />
|-<br />
|evil || Item has a red aura if you can detect evil, can be removed with Bless.<br />
|-<br />
|invis || Item can only be seen if you have detect invis, and shows (Invis) if you can<br />
|-<br />
|magic || Item shows as magic if you can detect magic<br />
|-<br />
|nodrop || Item can't be dropped, can be removed with Bless<br />
|-<br />
|bless || Item has a blue aura if you can detect good, can't be poisoned, and is a little easier to enchant. Is removed by Curse.<br />
|-<br />
|anti-good || Item cannot be worn, held, or wielded by characters at or above 350 alignment.<br />
|-<br />
|anti-evil || Item cannot be worn, held, or wielded by characters at or below -350 alignment.<br />
|-<br />
|anti-neutral || Item cannot be worn, held, or wielded by characters between -350 and 350 alignment.<br />
|-<br />
|noremove || Item can't be removed. This flag is removed by uncursing<br />
|-<br />
|inventory || Item is part of a shopkeeper's inventory and will be sold with infinite quantity left. Also evaporates when the holder dies, like rotdeath.<br />
|-<br />
|nopurge || Item can't be purged. Use sparingly!<br />
|-<br />
|rotdeath || Item poofs when whoever is holding it dies. If a mob dies with one of these, it will vanish.<br />
|-<br />
|visdeath || Item can only be seen by immortals<br />
|-<br />
|uncounted || Item doesn't count against the holder's carry number or weight capacities.<br />
|-<br />
|nonmetal || Item is unaffected by Heat Metal<br />
|-<br />
|meltdrop || Item poofs when dropped or stolen. If a mob dies with one of these, it will appear in the room. <br />
|-<br />
|decaying || Item loses 1 condition per minute, then disintegrates.<br />
|-<br />
|sellextract || Item poofs when sold to shopkeeper -- doesn't show up in their inventory<br />
|-<br />
|nodestroy || (AKA burn_proof in the code for some reason) Item can't be poisoned, and can't be destroyed by various item-destroying affects (which I think are disabled)<br />
|-<br />
|nouncurse || Item can't be uncursed. (nodrop, noremove flags)<br />
|-<br />
|runic || Unused<br />
|-<br />
|adhesive || Item stays with a player, not on their corpse<br />
|-<br />
|nochk || [[Wand]], [[Scroll]], [[Staff]], [[Rod]], and [[Event Item|Event]] items with this flag won't check a character's [[artifice]] skill when used, but just always work<br />
|-<br />
|noremort || Item can't be carried through a remort<br />
|-<br />
|inert || Item doesn't appear in rooms its in<br />
|-<br />
|noexplode || Wand and staff type item won't disintegrate when their charges are used up. Drinkcontainers won't poof when empty.<br />
|}<br />
<br />
====EXTRA2 FLAGS====<br />
{|<br />
|antihuman || Can't be equipped by Human race<br />
|-<br />
|antimoogle || Can't be equipped by Moogle race<br />
|-<br />
|antisaiyan || Can't be equipped by Saiyan race<br />
|-<br />
|antiesper || Can't be equipped by Esper race<br />
|-<br />
|antihylian || Can't be equipped by Hylian race<br />
|-<br />
|antikokiri || Can't be equipped by Kokiri race<br />
|-<br />
|antigiganto || Can't be equipped by Giganto race<br />
|-<br />
|antimatango || Can't be equipped by Matango race<br />
|-<br />
|antireploid || Can't be equipped by Reploid race<br />
|-<br />
|antikoopa || Can't be equipped by Koopa race<br />
|-<br />
|antipmpkn || Can't be equipped by Pumpkinhead race<br />
|-<br />
|antiknight || Can't be equipped by Knight class<br />
|-<br />
|antiwarrior || Can't be equipped by Warrior class<br />
|-<br />
|antithief || Can't be equipped by Thief class<br />
|-<br />
|antiwizard || Can't be equipped by Wizard class<br />
|-<br />
|antipriest || Can't be equipped by Priest class<br />
|-<br />
|antigeomancer || Can't be equipped by Geomancer class<br />
|-<br />
|antisummoner || Can't be equipped by Summoner class<br />
|-<br />
|antifemale || Can't be equipped by female characters<br />
|-<br />
|antimale || Can't be equipped by male characters<br />
|-<br />
|antineuter || Can't be equipped by sexless characters<br />
|-<br />
|cursed || Item becomes noremove when equipped<br />
|-<br />
|unique || Characters can't pick up one of these if they already have one.<br />
|-<br />
|remortable || Item was carried through a remort and won't vanish on logout if it's out of the player's level range.<br />
|-<br />
|antinu || Can't be equipped by Nu race<br />
|-<br />
|antikirby || Can't be equipped by Kirby race<br />
|-<br />
|antilobsterman || Can't be equipped by Lobster race<br />
|-<br />
|antiranboob || Can't be equipped by Ranboob race<br />
|-<br />
|antijumi || Can't be equipped by Jumi race<br />
|-<br />
|antidancer || Can't be equipped by Dancer class<br />
|-<br />
|antimob || Can't be equipped by mobs<br />
|}<br />
<br />
* NOTE: Old classes are affected by antiwizard, etc, just as new ones are.<br />
<br />
====EXTRA3 FLAGS====<br />
{|<br />
|exalted || Can only be equipped by players who have remorted at least once (if remort $n >= 2)<br />
|-<br />
|heroic || Can only be equipped by players who have remorted at least five times (if remort $n >= 6)<br />
|-<br />
|epic|| Can only be equipped by players who have remorted at least ten times (if remort $n >= 11)<br />
|-<br />
|perishable|| Object will disappear on logout if the character is not in the object's source area.<br />
|-<br />
|owned|| Object cannot be equipped unless it shares all name keywords with the character.<br />
|-<br />
|eventitem || A consumed food, potion, or pill, or recited scroll item won't cast a spell, but instead execute a mobprog specified by the item's data fields (v2, v0, v0, or v0 respectively).<br />
|}<br />
<br />
* NOTE 1: Objects restricted by number of remorts will also not be saved to unqualified player files when logging out, UNLESS they are somehow also flagged as remortable.<br />
* NOTE 2: Mobiles cannot remort, so exalted, heroic, and epic objects are effectively also antimob.<br />
<br />
===AREA EXFLAGS===<br />
{|<br />
|visdeath || Area is not visible on 'areas' display.<br />
|-<br />
|norecall || No recalling anywhere within this area.<br />
|-<br />
|nosummon || No summoning within this area.<br />
|-<br />
|noweather || Weather is always 0 wind, 0 sky, and the 'weather' command fails with no map displayed.<br />
|-<br />
|cold_weather || Weather messages mention snow instead of rain, and other tweaks to represent chilly areas.<br />
|-<br />
|norandoport || 'random' and 'buggy' portals will not send characters to rooms in this area.<br />
|}<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=September_2018:_Safari_Zone&diff=2331September 2018: Safari Zone2019-07-05T20:27:39Z<p>Pascal: </p>
<hr />
<div>Area of the Month for September 2018 is the [[Safari_Zone|Safari Zone]]!<br />
<br />
A template format for your review is below; click 'edit' at the top of the page, copy-pasta from the <nowiki>----</nowiki> to the next <nowiki>----</nowiki>, and fill in the gaps!<br />
<br />
('''''Yes,''''' a wiki account is required to edit the page and therefore post your review, but take heart: The wiki is hosted by the Cleft itself, not a third party!<br />
<br />
<br />
----<br />
<br />
'''Player: You!(Class/Level)'''<br />
<br />
'''Review Date(s): '''<br />
<br />
<br />
'''Descriptions: X/10'''<br />
<br />
How does the area's room descriptions(descs) work for you? Do they give you a good idea of the area? Do things that stand out in the desc and NEED explanation GET that, either from flavor text(extra-descs) or NPCs in the room or anything?<br />
<br />
What about mobiles(mobs) and their descriptions? Can you get a decent mental image of who or what this NPC/monster is? Do they respond when you talk or interact with them?<br />
<br />
Some areas have interact-able objects like fountains. Do they stack up well also?<br />
<br />
<br />
'''Balance: X/10 (OR N/A)'''<br />
<br />
(NOTE: combat will be most accurately gauged when your character is in the area's suggested level range.)<br />
<br />
If this area has combat, how does it feel? Does anything jump as horribly overpowered and impossible to deal with? What about the flipside, anything far too easy to beat? <br />
<br />
Are purchased or rewarded items at the appropriate strength levels? Is the effort required to obtain rewarded items reflected in their usefulness (or uniqueness and fancifulness)<br />
<br />
<br />
'''Attractions: X/10'''<br />
<br />
Why would you suggest someone come to this area?<br />
Is it just a good place to grind experience(lots of mobs)?<br />
Does the area provide a chunk of good gold and loot?<br />
<br />
What about the quests? Does this area's quests feel properly done, or is there some part of it that you feel needs work?<br />
<br />
For towns, are the shops good? Any other non-combative attraction for the area?<br />
<br />
<br />
'''Connections: X/10 '''<br />
<br />
How easily and well does this area connect to its nearby areas?<br />
Does it make sense thematically to be connected to the areas it is?<br />
<br />
<br />
'''Personal'''<br />
<br />
Any comments you'd like to make that you don't feel apply to the other sections can go here!<br />
<br />
<br />
<br />
----<br />
<br />
'''Player:''' Emouse (Dollmage, L100, ~5 remorts) --TOKEN'D<br />
<br />
'''Review Dates:''' 9/7/2018-9/8/2018<br />
<br />
'''Descriptions: 5/10'''<br />
<br />
The mobs in the Safari Zone are good, but not great: The lookdescs and combat progs are effective descriptions and show some personality, but outside of that the mobs are kinda lifeless. None of the pokemon have talkprogs to demonstrate non-violent interaction, there's no text while idle or interaction between pokemon in the wild, and Todd's involvement for his quest is... minimal. And easily sequence broken - you can walk straight to the Fearow and skip the rest of his requests. Of which I remember more than the one he currently makes, so I'm not sure if it's even operating as intended. You'd also think his enthusiasm would lead him to babble a lot about the pokemon in the region if prompted when following, but that's pure radio silence as well...<br />
<br />
Gotta say, the graffiti adds a lot of personality to the room descriptions. The river/pond region has a lot of little bonus descriptions that add life to the area... but the rest of the zone doesn't. The room descriptions in the caves and forest area are good, but there's little further details on items of interest from trying to 'look' at them, aside from one or two quest-related tidbits. Complete lack of detail on the Dustox colony in the forest and the various stalactites and water pools in the cave is saddening. It feels like the one N W W from the entrance of the caves would even be a fountain...?<br />
<br />
'''Balance: 7/10?'''; approximated by having level 30 pet solo battles<br />
<br />
The mostly-questing-prices Level 30 Knight-like pet that I brought here to fight could usually win solo battles before the Anger Rating maxxed out, but took nontrivial amounts of damage in the process, even with the modestly-interesting combat progs most of them had. Except against Gyrados, which is appropriate given the level jump. RIP.<br />
<br />
In terms of drops and loot, there are some finds here that... aren't very good, but have niche uses, and the pokemon in the area drop enough cash that the 100 silver entry fee isn't a huge deterrant. However, the drops have... pretty bad sell value, and feel rare for the narrow range where it's useful. For example, I managed to clear out the forest twice without getting the Scyther equipment drop.<br />
<br />
I'm not sure how to feel about the frequency of the pokemon food dropping from everything in the area: It's such a poor food item that it can't be used to stave off hunger, but I don't know how common it should be to have it as an option to offset the anger meter mechanic for classes that aren't damage-focused, or if it should offer much side use for players that don't. Would 1 satiation/1 fullness to make it at least count as a snack for the shameless be too much?<br />
<br />
'''Attractions: 3/10'''<br />
<br />
The Safari Zone is in a weird place in terms of attractiveness. If you know enough about it already and have an aggressive enough skillset, it can be a servicable levelling spot with some niche drops available, but if you haven't figured the area out already, there's no real indication that sticking around is worth it - especially since the main attraction to the area is fighting the pokemon without being caught by the warden, when both the warden and Todd appear to discourage you from fighting them. Some more guidance that "yeah, beat 'em up but be careful" is the real point would probably make the area clearer. Perhaps Todd could drop a hint that you'll need to at least provoke pokemon to get the photos he needs and let the rest happen as it will?<br />
<br />
There are some hidden things hinted at or with requirements from other zones that are definitely worthwhile, but I don't know whether to count those as attractions for the Safari Zone, or attractions for those other zones that require you to look around further. They don't really add incentives to stay at the safari zone - just to visit briefly to get something else in an area you're already overlevelled for and might as well leave immediately afterwards. The items available are... usable, but not especially impressive outside of some distinct niches.<br />
<br />
Outside of the purely pokemon-flavored sightseeing there's not a lot here that you can't do better at elsewhere. Tonoe and Arlia aren't much further from Viorar with significantly wider options and more relevant quests...<br />
<br />
'''Connections: 2/10'''<br />
<br />
Another rough spot. The Safari Zone is entirely pokemon-based aside from references in the graffiti and a few external quest things that are hard to count as the Safari Zone specifically. But... it is specifically an animal reserve for pokemon and that's exactly what the Warden would do, so it's hard to justify further connection to the rest of the Cleft.<br />
<br />
At most, other visitors of different races/whatever as NPCs with hints or advice could be added, or adding references to external resources that the Warden would be willing to employ to try and keep the pokemon safe; hidden Monotoli-brand security cameras, for example. Still, whether the warden would have/use the resources to do this is difficult to say.<br />
<br />
The connections for Safari Zone are poor, but adding more is also difficult to justify. Hard to say what to do with this one: Probably best left as a low priority outside of a serious zone overhaul.<br />
<br />
'''Bugs/Exploits:'''<br />
<br />
Something I'm not sure is a bug - you can attack and kill Todd, the starter NPC for the only real quest in the zone. No special response or acknowledgement is given for this, and he's level 0. Should he be classified as either noattack or a player ally?<br />
<br />
'''Overall: C-'''<br />
<br />
The Safari Zone is not one of the Cleft's stronger zones. Between the mediocre attractions there and its dead-end location it's very easy to skip over or forget about entirely, though there are some neat points hidden away if you make a point of looking. Is it worth doing more than once? Well... not really. Todd doesn't even offer a mini medal for his miniquest, which is so small and simple that's even understandable. There's not much to do here aside from get into fights to level, but the zone flavor even discourages that. It looks so promising when you start out with the river and pond areas and all the graffiti descriptions, but falls apart pretty quickly once you go further and start really interacting with the area. If anyone particularly feels like revamping things, this is probably a good candidate for it.<br />
<br />
<br />
----<br />
<br />
Player: Patapon(Warrior/25) - TOKEN'D<br />
<br />
Review Date(s): 9/19/18<br />
<br />
'''Descriptions: 5/10'''<br />
<br />
Marginal typographical errors throughout the area, not bad enough to really distract too terribly. The mobs are described well, however the descs are all short and formatted inconsistently. There are almost no extra descs except for some graffiti and one random lantern that is formatted kind of crazily and seems almost cryptic and meaningful, but isn't, like most things in this area.<br />
<br />
It's not the worst I've ever seen but it's right about bare minimum for acceptable.<br />
<br />
<br />
'''Balance: 4/10'''<br />
<br />
The fights are very easy, but I am also a warrior so that might be a side effect. There are a lot of mobs to fight so it's a pretty mindless grind. The anger mechanic exists. I'm sure it's helpful but it's mostly a non-issue, it's never difficult to toss a food at a pokemon, especially since they drop all over.<br />
<br />
The random rarer pokemon are marginally harder, which makes sense.<br />
<br />
The gear attained here is entirely ignorable. There is nothing significant that better can't be found before or at the same level, some of it from vendors. Even random drops from mobs should be better than vendor gear.<br />
<br />
<br />
'''Attractions: 1/10'''<br />
<br />
I immediately lost Todd in a tree before finding the pokemon he requested. Looking around the entire place, I'm not sure it even exists. The quest ends abruptly with screen spam. It could be tidied up with some delays. The quest could also be made better by not being so terrible.<br />
<br />
There is nothing here of value or interest, except for two different unrelated things from completely different areas that you wouldn't know about just from going here.<br />
<br />
I'm giving it 1 point because pokemon themselves are an attraction. It was fun finding the different pokemon, like gyarados. However, defeating them always let me down.<br />
<br />
<br />
'''Connections: 1/10'''<br />
<br />
From a straight-forward approach, the connections here are close enough to non-existent to be statistically insignificant. However, it could easily be speculated that the Safari Zone as a wildlife preserve is controlled by the nearby Fort Walla Walla, one of the only 'law and order' type establishments in this region of Fa'diel and possibly the only ones interested in preserving wildlife. Otherwise, the "don't fight the pokemon" command doesn't make any sense. As is, there is no connection, but potential exists to tie it in much better.<br />
<br />
<br />
'''Personal'''<br />
<br />
The way to get in is not straightforward. It says you have to pay, but what he means is you have to buy a ticket. I am not the only person who did not figure out that you had to actually buy a physical ticket from the guard via typical shop mechanics. The first time I came here I couldn't figure it out literally at all and got in by sneaking through. When I came back without sneak, it took me 10 minutes to figure out. He also says you need to put away your weapons, but you actually don't, which is lame.<br />
<br />
This area has great potential. Even with the mediocre descriptions, the aesthetic is nice. Just by merit of having pokemon and being the safari zone, this area is okay. If it was anything else, I would probably say it was terrible.<br />
<br />
----<br />
<br />
**Safari Zone has been updated since this review.<br />
<br />
[[Category:Area of the Month]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Apr_2018:Booster_Tower&diff=2330Apr 2018:Booster Tower2019-07-05T20:26:41Z<p>Pascal: </p>
<hr />
<div>Area of the Month for April 2018 is [[Booster_Tower|Booster Tower]]!<br />
<br />
A template format for your review is below; click 'edit' at the top of the page, copy-pasta from the <nowiki>----</nowiki> to the next <nowiki>----</nowiki>, and fill in the gaps!<br />
<br />
('''''Yes,''''' a wiki account is required to edit the page and therefore post your review, but take heart: The wiki is hosted by the Cleft itself, not a third party!<br />
<br />
**Post-reviews, Booster Tower was altered too significantly to note every change here, thanks. 9/27/2018<br />
<br />
<br />
----<br />
<br />
'''Player: You!(Class/Level)'''<br />
<br />
'''Review Date(s): '''<br />
<br />
<br />
'''Descriptions: X/10'''<br />
<br />
How does the area's room descriptions(descs) work for you? Do they give you a good idea of the area? Do things that stand out in the desc and NEED explanation GET that, either from flavor text(extra-descs) or NPCs in the room or anything?<br />
<br />
What about mobiles(mobs) and their descriptions? Can you get a decent mental image of who or what this NPC/monster is? Do they respond when you talk or interact with them?<br />
<br />
Some areas have interact-able objects like fountains. Do they stack up well also?<br />
<br />
<br />
'''Balance: X/10 (OR N/A)'''<br />
<br />
(NOTE: combat will be most accurately gauged when your character is in the area's suggested level range.)<br />
<br />
If this area has combat, how does it feel? Does anything jump as horribly overpowered and impossible to deal with? What about the flipside, anything far too easy to beat? <br />
<br />
Are purchased or rewarded items at the appropriate strength levels? Is the effort required to obtain rewarded items reflected in their usefulness (or uniqueness and fancifulness)<br />
<br />
<br />
'''Attractions: X/10'''<br />
<br />
Why would you suggest someone come to this area?<br />
Is it just a good place to grind experience(lots of mobs)?<br />
Does the area provide a chunk of good gold and loot?<br />
<br />
What about the quests? Does this area's quests feel properly done, or is there some part of it that you feel needs work?<br />
<br />
For towns, are the shops good? Any other non-combative attraction for the area?<br />
<br />
<br />
'''Connections: X/10 '''<br />
<br />
How easily and well does this area connect to its nearby areas?<br />
Does it make sense thematically to be connected to the areas it is?<br />
<br />
<br />
'''Personal'''<br />
<br />
Any comments you'd like to make that you don't feel apply to the other sections can go here!<br />
<br />
<br />
<br />
----<br />
<br />
'''Player: Scribble(Knight/16)''' - TOKEN'D<br />
<br />
'''Review Date(s): 4/1/2018'''<br />
<br />
<br />
'''Descriptions: 4/10'''<br />
<br />
The descriptions of the mobs are short and sweet, which is fine. They describe them rather well, but just somewhat unimaginatively. The Snifits all share a description except for one, describing them as Booster's "three main toadies" even though there is a fourth. This fourth one is also a shopkeeper, but looking at him still reveals his condition as if he were killable.<br />
<br />
The room descriptions are easy to ignore and very short. A few are even one sentence. The room you are sent to after taking the trip there refers to the event that sent you there, even though it's possible to leave from this room and then go back through it normally, obviously not having arrived there the same way as you did initially. There are very few things in the room descriptions to look at and nothing in them is ever important, every important interactable object and mob being plainly visible in the room.<br />
<br />
While reading the descriptions does help mildly paint a picture of the area, the tower is more or less a free for all killing spree zone without much to look at. The only location within this area that is actually interesting to read is the Marrymore Province, but it lacks extra descriptions. On that note, extra descriptions are highly lacking and the ones that *do* exist do not add much more to the area.<br />
<br />
This is somewhat an important note as, being a very popular, easily accessible area that nearly every newbie will visit, it does not help adjust them to the fact that reading room descriptions is typically very important in the Cleft. Though, arguably, completing the quests would still be very hard to do without reading the descriptions of the mobs involved.<br />
<br />
<br />
'''Balance: 8/10'''<br />
<br />
The balance here is good, in regards to mobs. There are large numbers of killable mobs all around the tower, ranging from 15 to 19. All of the named mobs, with sparse few exceptions, are killable and much higher level, however they are only so much more difficult than the regular mobs, except for a few (the Apprentice for example is rather tough). My character is perhaps slightly more well geared than your typical newbie, though these mobs will be harder for some classes than for others, as well. At level 17 (I leveled while writing this) I'm able to kill the level 25 mobs here, as long as I'm paying attention. For a lower level area, perhaps this is okay. The trash mobs are of varying difficulty and introduce some new status effects to new players, which is important, though annoying. <br />
<br />
For instance, I've just been not killing Orb Users because I can't re-equip my shield after using shield slam due to being blinded. This is just annoying and not really a huge issue. Bob-Ombs are probably the weakest enemies, but will explode for no experience if not killed quickly, which is a neat mechanic, teaching new players that not all fights will be so cut and dry.<br />
<br />
The items available here are decently balanced, though the level requirement for certain quest rewards is worth some discussion, mentioned below. The actual strength of these items is probably fine.<br />
<br />
<br />
'''Attractions: 7/10'''<br />
<br />
Booster Tower is obviously a hotspot for leveling and it's suggested quite frequently already. Its location is incredibly convenient, much closer to Truce than other similar leveled areas, and a useful spot for much longer than others. It's a good leveling spot for first life characters and newbies from its starting level (depending on the skill and class of the player, possibly earlier), though it tends to lose its steam quite a few levels before its suggested ending level range.<br />
<br />
There are useful pieces of gear, here, from quests or otherwise, that are typical standard fare for your general player. Some of the quest rewards are not useable until the very last level of the range of the tower. Even for a first life character, the quests are not difficult to complete before level 25, even *far* before 25, potentially teaching newbies the hard way that items will poof from your inventory if they are 10 levels out of reach. By the time you can actually use them, you probably won't even be in Booster Tower anymore.<br />
<br />
The "main" quest (the one with the most steps) is not too hard to follow and figure out, although considering its main mechanic is giving items to NPCs, it's unfortunate that some of the NPCs may keep these quest items when they are the incorrect recipient. There is inconsistency here, as some NPCs WILL give back wrong items and others will not. It's not clear if this is intentional, but if so, it's not really a great sort of 'difficulty modifier' in my opinion, and moreso just annoying.<br />
<br />
It's also worth questioning if it's worth preserving the situation within this quest where the final turn in item is a potentially useful item for certain classes to keep, while the final reward would be bad for those classes. It's possible to do the quest over again, but that would insist that if the final reward is not good for your class, you basically just do it again, while other people would not have to. I'm not sure this is a great mechanic, personally.<br />
<br />
One of the quests can be cheesed (I won't explain how publicly!) really easily, while another requires an item that requires level 20 to wear, but the reward requires level 25 to use. The item also doesn't *necessarily* require combat to acquire, so the jump in level requirements is potentially super annoying. Basically if you complete it as soon as you are able, you'll still have an unusable item in your inventory for five levels before you even know if it's worth the space to keep it.<br />
<br />
These level requirements for the quest rewards is the only thing I would really think to take a second look at, if only for the fact that Booster Tower - despite being level 16-25 - becomes less useful and will typically be finished significantly before its final level of 25, even by newbies, as has been demonstrated recently.<br />
<br />
<br />
'''Connections: 5/10 '''<br />
<br />
This is one of the most easily accessible, mob-dense areas for low level leveling in the game for a Truce start. Thematically, Booster Tower is questionable in its location. It's just a short walk from Truce, between there and Rocket Town. The entrance to the tower itself implies the tower is somewhat unpleasant looking, saying that the door has been broken down. For an area openly displayed between two neat and orderly towns, this seems like something that may be of interest to be addressed by the authorities. Maybe it's mentioned and I just haven't seen it.<br />
<br />
<br />
<br />
----<br />
'''Player:''' Aludra(Wizard/8) -- Token'd<br />
<br />
'''Review Date(s)''': 04/06/2018<br />
<br />
<br />
'''Descriptions''': 5/10<br />
<br />
The area itself is fairly decent. Some rooms have much shorter descriptions than others, but the environment is rather same-y all in all. Especially in the source material. There are only so many ways to say 'big ugly marble chessboard room.' I wouldn't mind seeing some colour pops though, just to highlight some of the more interesting things. There aren't really any extra descriptions of note other than the TV near the top. Cute, but not inspiring.<br />
<br />
Most of the mobs have strange formatting and linebreaks. Snifit 1 for example:<br />
<br />
He wears a grey coat over his whole body, a black belt, and a black gas <br />
mask covering his face. He is one of Booster's three main toadies and loves<br />
to catch beetles and eat cake. <br />
<br />
And, of course, a Spookum: <br />
<br />
Spookums are the same height and wear the same mask as Snifits, but their<br />
rank is lower and their robes are blue rather than grey. They came to<br />
become Snifits under Booster's training, but he only wants four. <br />
<br />
They all seem to be written under a very short linewrap. I'm not going to paste every single mob description, but there are a lot of them with this issue.<br />
<br />
Other than that, they're all nice and concise and give a good idea of what you're dealing with.<br />
<br />
As for area objects, such as the toy chest and therein, these objects suffer the same linewrap issue. One of the trains are barely described at all. Player-ownable objects (such as the balloons) have equally lackluster notes. Some colour pops would be great there too.<br />
<br />
All in all, the writing is decent, but it's lacking in content. Jazz it up!<br />
<br />
'''Balance''': 7/10 (OR N/A)<br />
<br />
The chain chomps are probably the most difficult thing here to fight. Disproportionately so, given their relative level.<br />
<br />
Fireballs are definitely the weakest, and their level/xp are true to that. Would be neat if they were more in line with the rest of the area.<br />
<br />
Second to fireballs, bombs are definitely probably the weakest. I just wish they didn't cease to give you XP if they delete themselves via explosion. If they survived that with 1hp, I'd be a lot happier. <br />
<br />
<br />
I wish the rewards were more consistently leveled though. Equipment and items you can get here range from 15 to 45. By level 25, there are definitely way better places to be and much better items to use. At least the level 45 item isn't terrible. It's very easy to lose track of though, especially at a lower level where it will disappear and you'll forget about it entirely.<br />
<br />
<br />
'''Attractions''': 7/10<br />
<br />
There's basically no reason not to come to this area if you're starting out on the Truce side. It's easily located, it's packed to the gills with things to kills. The money drops aren't too bad for the level. There are plenty of little hidden treasures you can acquire if you know what to do. And, most importantly, you can do the beetle hunting minigame and rack up all kinds of dosh if you're bored.<br />
<br />
The main questline here is pretty slick. It takes a little bit of trial and error, but once you get rolling, it's hard to stop!<br />
<br />
There are three shops. None of which have any weapons or armor, but you can get some useful goodies here, if you know where to use them!<br />
<br />
<br />
'''Connections''': 10/10<br />
<br />
It connects Truce, Rocket Town and Rabite forest. Or, I'm assuming. I've never found the key to the locked back door. But I'm assuming! If the door does go where I think it was, it's a quick trip through Booster's Tower to get to Neko's Cabin, which backdoors into Guardia Castle. Pretty handy shortcut, if true. But where's the key? This might be a Thief Only scenario.<br />
<br />
<br />
'''Personal'''<br />
<br />
All in all, this area is a great springboard into the teen-levels, and further adventure. At least one of the rewards is good for all levels. I just wish it were more visual.<br />
----<br />
<br />
<br />
'''Player: Kaze(Warrior/10ish, Theif 10-15)'''<br />
<br />
'''Review Date(s): April 1st for the Warrior, April 15th for the Thief'''<br />
<br />
<br />
'''Descriptions: 7/10'''<br />
<br />
I like the descriptions as a rule. It's good. Many of the rooms are pretty bland. One common issue is that the names are the primary way to get a feel for relative height short of mapping, not the descriptions.<br />
<br />
The rooms that are noteworthy locations are pretty well described. That includes the entryway, Thomp's room, Booster's room, and Marymore... Dodo, etc. The knifey dude is pretty much the only interesting feature of his room.<br />
<br />
Most of the puzzles are in the descriptions, fair dinkum. This is good. Some level of hand holding is appropriate such an early stage, even, so the clarity is welcome.<br />
<br />
Mobs are pretty descriptive and have a jovial feel. None stood out as particularly bad, but a few were especially good. Valentina's rich trailer-trash vibe was readily apparent. The train's animation played in my head.<br />
<br />
'''Balance: 9/10 (OR N/A)'''<br />
<br />
Fire vulnerability is NASTY in the tower. <br />
<br />
The Bob-ombs seem overpowered for their level. You need DPS to drop them. The boom is devastating or deadly at the low end of the level. (If you have the HP to survive, I suspect they are much easier. Warrior handled them much lower than thief, say) Still, if you ''have'' enough, they are otherwise a bit easy. They are pretty binary that way. Going into the tower at level, I'd recommend most steer clear. On your way out, waste them for the exp.<br />
<br />
Orb users can also be deadly, especially to the fire vulnerable, but their tricks mostly seem challenging to me, not unfair. They blind and hit hard, yet are a bit fragile. I think they're well balanced for level.<br />
<br />
Spookums are pretty fair, given they act as a pretty solid entry requirement. Must be this big to enter. They are pretty much average, Maybe a touch weak, but given their company, that's far from a bad thing.<br />
<br />
Chomps are tough little cookies at level. Got to use dirty tricks or resources to fight them until about mid level. They are fairly easy to avoid and, frankly, used quite well. <br />
<br />
The bosses are a bit of a ramp, as expected and desired. The only one that really seems out of range is Val. Especially if you have the wrong vulnerabilities, she's realy good at smacking a low level character around. It generally wise to come back to finish her off.<br />
<br />
Item rewards range from about what you'd purchase to nice for the level. Clown Gloves are really nice for their level. Otherwise things tend to be a bit light.<br />
<br />
All in all, this is pretty much my standard for combat balance. It's one of the best zones, that way.<br />
<br />
<br />
'''Attractions: 9/10'''<br />
<br />
It's got fun and amusing little secrets. It's got challenging MOBs. It's got some decent EQ. If you like MUDs, it's for you. <br />
<br />
Loot isn't much of a draw, though the shops are. Gold is decent.<br />
<br />
Quests are average. They mostly aren't hard. The Chain Chomp thing is pretty obscure. The Sniffits are humerous but the rewards are pretty pointless. Marymore is cool looking but one of its quest elements is tricky to even spot, much less solve. <br />
<br />
A few more scattered hints are in order. Given the nature of the area, that's probably best solved in other zones, predominantly, but some on site would be good, too.<br />
<br />
<br />
'''Connections: 7/10 '''<br />
<br />
''Why'' it's where it is isn't clear, but it does link to its surroundings in a rational way. Really ought to have a bit more description on the road, though. A tower that big would be visible from quite a ways off.<br />
<br />
<br />
'''Personal'''<br />
<br />
It's my favorite low-level area. <br />
<br />
A clever way across the fireball floor without an encounter would be welcome, as would some more flavor in the interstitial floors.<br />
<br />
<br />
<br />
----<br />
<br />
'''Kolem (Playing as Belle, L. 8-13 Moogle Geomancer, with various others; also Paisley, L~10 thief)'''<br />
<br />
'''Review Date(s): 4/26/2918'''<br />
<br />
As is standard with my reviews, all sections begin with five points. Consistent positives or excellent examples gain points; consistent negatives lose points or half points. Here we go!<br />
<br />
<br />
'''Descriptions: 5/10'''<br />
<br />
Oh, Booster tower. You hold a special place in my heart, but you show your age in a lotta places. One of them is the near-dearth of extra look descriptions--the only ones there are for interactables, as well as a single T.V. On the bright side, all monsters in the tower respond to talking, and spookums and snifits aside, seem to be desced decently. I was gonna ding this area half a point for lack of extra descriptions, but it doesn't really IMPEDE the player--it just feels like a missed opportunity, especially given the bonkers nature of the source material. I'll give it functional marks, but this is an area for improvement.<br />
<br />
<br />
'''Balance: 5/10'''<br />
<br />
This is a hard one, and I feel like it's one of Booster Tower's high points--and low points. The real problem I have with the zone is that, outside of the boss enemies and quest items, there aren't any real 'drops' to speak of in the tower. Spookums, Bob-ombs, Orb Users, Chain Chomps, and Remo Cons don't appear to have any drops whatsoever, and the boss rewards are either high-end of the range or storebought at the very lowest end of the scale (as is the case with Valentia's drops). <br />
<br />
On the other hand, I have nothing but praises to sing ABOUT those mobs. Booster Tower's mobs--the ones above, before we get to the bosses--all have interesting, engaging combat tricks. Analyze reveals that chain chomps have a random major weapon resistance, making melee classes have to think and plan, while Bob-Ombs will severely punish, say, a caster who bungles a few spells (this happened to me more than once). Orb users introduce low level blind and fire attacks into the mix, while Remo Cons inflict the Curse ailment, which can lead to real problems. Coupled with the levels you might attempt the tower being the introduction to the necro mechanics, these monsters are incredible teaching moments. Which leads us to...<br />
<br />
The bosses. They can and WILL thrash players who are much too low level to challenge them, with powerful attacks. One sore point is the Apprentice miniboss, who can come off as a nasty surprise the first time you encounter them, and is probably single handedly responsible for most of the new player deaths in the tower. Fireballs are also fairly obnoxious, but much less challenging than just about everybody else in the zone. Some sort of trick mechanic to switch them 'off' for a bit might be cool, similar to the trick for the chain chomps and spookum at the doorway. Maybe a minor in-room puzzle? Booster can call for help, and Valentia has powerful spells for the level. <br />
<br />
Another sore spot is the items--not just the lack thereof from the main common monsters, but the boss drops, as well, and those items gleaned through quests and mini-quests. They're all over the scale, swinging wildly from cheap but usable to high level and very useful, with levels that don't really quite suit their placement. The Balloons item, wands, and rod in particular in this zone are all handy to have, but have caveats--whether they be rot-death, high level, or simply hidden in a multi-level quest with a slightly obscure (but fun!) beginning. I kinda wish it was possible to expand the entry point to the quest, just because I enjoy it personally.<br />
<br />
All in all: Plus one full point for dynamic, interesting monsters that have multiple approaches to fights, minus one half for a lack of drops, and minus another half for the swinginess of item level and placement--it's items that hold this zone back, and that's a pity, because the combats here are genuinely a blast. (Hah!)<br />
<br />
<br />
'''Attractions: 7/10'''<br />
<br />
Hmm. While Booster Tower has solid experience payouts, the treasures--once you know what is here--are pretty useful, even though their levels are skewed. Additionally, there's at least one major item for a tie in quest later. I wish there were more to recommend here, especially in Marrymore--it's just big enough and themed enough with enough facilities to suggest expanding it to a mini-town, like Monstro Town or Medina. It'd really add some zing to the tower! There are also some mini-quests available in other areas that tie here, and a little lateral thinking can net you an nice piece of equipment. I can award one point for that--the distinctive items that are here are pretty fun, but I wish there was more reward for the lower end challenges here. See the Suggestions section for more. <br />
<br />
Additionally, the Beetle-catching minigame--and the hidden quest given by it--is really fun, but as others have pointed out, the mobs in the tower don't return items. I'll award another half point to the beetle game, and I wish there was more to do with it. There's also a minigame miniboss, which is always nice to see! I'll award it another point for that.<br />
<br />
<br />
'''Connections: 5/10 '''<br />
<br />
Booster tower itself has been worked on, off and on, by different builders for several years. This sorta patchwork addition is fine, but the surrounding environments--truce and Rocket town--refer to it only sparsely. It might be nice if it being obnoxious and visible played into more areas.<br />
<br />
Ultimately, it only has two exits, and one of them is locked by default. Which is... ehhhn. I wish there was more to Marrymore, and I wish there were more connections to external zones--it feels like the sort of place a Cannon Travel guy would totally make an installation on a balcony, or something. <br />
<br />
Five points for a functional, easy connection to one of the starting towns, but it could always stand to be improved.<br />
<br />
'''Personal'''<br />
<br />
Woof. What do I even say here? Booster's tower is practically a fixture of my time in the cleft, and it really sold me on the kind of lateral-thinking fighting on your feet that comes more into play as you fight later monsters. I love the flavor of the enemies here, but the tower itself could use a lot of touch ups. <br />
<br />
FINAL AVERAGE: Out of four categories, average score is '''5.5'''.<br />
<br />
SUGGESTIONS FOR IMPROVEMENT:<br />
<br />
*Rebalance item levels and flags and grant minor loot drops to the lower end monsters. One suggestion that sticks out in my mind is a hunk of Cosmo Brimstone as an uncommon drop from bob-ombs, regardless of if they explode or not--one gold treasures are decent enough for the level, and it would reward players with crafting components that they could feasibly use to start poking the crafting shops. It would also be thematically consistent with the bob-omb recipe sold in cosmo canyon.<br />
<br />
*Touch up room, mob, and extra descriptions. For being such a gaudy place, Booster Tower uses criminally little color--the portraits are begging for ascii art or at least extra descriptions, along with loads of other spots it'd be easy to add more un-style.<br />
<br />
*Expand the beetle minigame! Yes this is silly and dumb and unnecessary but I love it, and I wish more beetle-based enemies yielded special rewards / there were more variants of beetle / a beetle box event item. Shush don't judge me.<br />
<br />
*Add additional resources to Marrymore. It has a fountain and even benches--expanding it into a minitown would reward adventurous players, and would be a great spot for 'toys' and the like to be sold in the future.<br />
<br />
*Give more external clues about the way to bypass the guard / get various prizes / bypass the chomps with the use of a logically fitting item.<br />
<br />
<br />
----<br />
<br />
**Booster Tower has been updated since these reviews.<br />
<br />
[[Category:Area of the Month]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mar_2018:_Chocobo_Forest&diff=2329Mar 2018: Chocobo Forest2019-07-05T20:26:02Z<p>Pascal: </p>
<hr />
<div>Area of the Month for March 2018 is [[Chocobo_Forest|Chocobo Forest]]!<br />
<br />
A template format for your review is below; click 'edit' at the top of the page, copy-pasta from the <nowiki>----</nowiki> to the next <nowiki>----</nowiki>, and fill in the gaps!<br />
<br />
<br />
----<br />
<br />
'''Player: You!(Class/Level)'''<br />
<br />
'''Review Date(s): '''<br />
<br />
<br />
'''Descriptions: X/10'''<br />
<br />
How does the area's room descriptions(descs) work for you? Do they give you a good idea of the area? Do things that stand out in the desc and NEED explanation GET that, either from flavor text(extra-descs) or NPCs in the room or anything?<br />
<br />
What about mobiles(mobs) and their descriptions? Can you get a decent mental image of who or what this NPC/monster is? Do they respond when you talk or interact with them?<br />
<br />
Some areas have interact-able objects like fountains. Do they stack up well also?<br />
<br />
<br />
'''Balance: X/10 (OR N/A)'''<br />
<br />
(NOTE: combat will be most accurately gauged when your character is in the area's suggested level range.)<br />
<br />
If this area has combat, how does it feel? Does anything jump as horribly overpowered and impossible to deal with? What about the flipside, anything far too easy to beat? <br />
<br />
Are purchased or rewarded items at the appropriate strength levels? Is the effort required to obtain rewarded items reflected in their usefulness (or uniqueness and fancifulness)<br />
<br />
<br />
'''Attractions: X/10'''<br />
<br />
Why would you suggest someone come to this area?<br />
Is it just a good place to grind experience(lots of mobs)?<br />
Does the area provide a chunk of good gold and loot?<br />
<br />
What about the quests? Does this area's quests feel properly done, or is there some part of it that you feel needs work?<br />
<br />
For towns, are the shops good? Any other non-combative attraction for the area?<br />
<br />
<br />
'''Connections: X/10 '''<br />
<br />
How easily and well does this area connect to its nearby areas?<br />
Does it make sense thematically to be connected to the areas it is?<br />
<br />
<br />
'''Personal'''<br />
<br />
Any comments you'd like to make that you don't feel apply to the other sections can go here!<br />
<br />
<br />
<br />
----<br />
<br />
<br />
'''Player: Kaze (Ninja L50)''' - Token'd<br />
<br />
'''Review Date(s): 3/2/2018'''<br />
<br />
'''Descriptions: 7/10'''<br />
<br />
The general navigation worked to a point. The descriptions were were generally serviceable.<br />
The description when you pop the box is one of the better ones, but I don't like that it's a weird special room that teleports you around. (More on that later)<br />
<br />
One thing that isn't clear from the descriptions is any sort of progression from place to place. Forest becomes rocky. Go up and you're on a hill or in the sky. It's rather abrupt, really. The layout is probably part of that issue. <br />
<br />
The descriptions of the chocobo are pretty good. I can tell which each is, readily. I'm not convinced someone who hadn't played as much FF as I would, but such tend not to stick around that long, so... eh?<br />
<br />
Chocobo should either spook and run/fight or react with curiosity when you talk to them. They tend to be portrayed as quite friendly, which doesn't come through. Maybe that's intentional. Dunno.<br />
<br />
The nooks are suggested in the descriptions, so that seems fair. The cave is rather vague.<br />
<br />
The biggest thing that seemed off, though was the inability to ride Boco or one of the others. What a gyp!<br />
<br />
'''Balance: 7/10 (OR N/A)'''<br />
<br />
The chocobo are pretty straightforward foes. (Some teamwork would ramp up the difficulty tremendously, as would inserting a white one should you do so.) <br />
<br />
<br />
<br />
'''Attractions: 4/10'''<br />
<br />
Honestly, mostly this zone is accessible exp. While they are giving good experience and you can drop them, the zone is a goldmine. Otherwise, it's not all that great. The gold chocobo feather was less than exciting. Note that part of that is the difficulty in obtaining Float status. If you could snag such things while there was exp to be had, it wouldn't seem so lackluster but you'd have less reason to return. The Sky Armor pet I now have is... interesting, but not very useful.<br />
<br />
Now, I say all this knowing that I haven't gotten into the cave, yet. (I was going to experiment with trying to get the red chocobo to cast comet on the boulder, but I haven't come up with a good way to do so.)<br />
<br />
Okay: The fact that completing a leg of the quest leads to a special smoky room and then forces you to exit back to the clearing is irritating because that sleep thing. When you wake you can easily abandon a vehicle in the void. It's not too hard to avoid, if you're thinking about it, but I don't like it.<br />
<br />
I'd like there to be more quests, honestly. A quest to set up safer spots for nesting might be interesting. If there's going to be a free pet available, why not a chocobo buddy that's one of those fancy ones that levels and, thus, scales? Apparently, there is code in place to do that, so even if not a mount, (which, obviously, would be cool) at least a battle buddy could be a nice touch. A quest one-shot flag would make this something to be very careful of. (opening up the possibility of one or more resurrection quests) I'm seeing this as a difficult quest, though possibly more on the mind than the body. Don't know; kinda spit-balling. Some spirit of the forest could need something done to fix stuff for Big Bird's cousins.<br />
<br />
<br />
<br />
'''Connections: 4/10'''<br />
<br />
It's not hard to find but it's certainly out of the way. I have no idea what the thematic reason for its placement was. It actually seems like something that might fit better between Viorar and Truce, whether north of the Veldt or more southerly.<br />
<br />
<br />
<br />
----<br />
<br />
'''Player: Aludra???(Gambler/100)''' - Token'd<br />
<br />
'''Review Date(s): 03/04/2018'''<br />
<br />
<br />
'''Descriptions: 8/10'''<br />
<br />
The room descriptions aren't too short, nor are they too long to the point where it's a bother to read them. The different sections of the area are color coded in the short description, which is a nice touch. It really helps to remind you which part of the area you're in at a glance. <br />
<br />
The mobs themselves are all described fairly decently except for Mene, the moogle. It isn't badly written so much as it's more backstory than appearance. A little jarring compared to the rest of the zone. The color in his name also makes me spell it wrong constantly. Although this could be contributed to my font as well.<br />
<br />
The hidden objects and other looktraps are also quite nice. Plenty of secrets if you know where to look.<br />
<br />
<br />
'''Balance: 7/10 (OR N/A)'''<br />
<br />
The combat in the area is fairly engaging. The enemies use a variety of different abilities, which is only natural given the nature of different coloured chocobos. Some of the enemies drop wands that help out. The merchant in the area sells a few goodies as well. Though those are mostly used to access the rest of the zone. Aside from the boss of the zone, the enemies themselves aren't too rough. The only exception to this is the boss, and depending on your level, the Sky Armours. They can be a little mean if you're there kind of early. There's not much aggro to deal with. It's just too bad the zone is lacking in actual mobs. It's kind of deserted.<br />
<br />
<br />
<br />
<br />
'''Attractions: 10/10'''<br />
<br />
The main reason I'd come to this zone is for the quests. They're short, fun, and the rewards are very nice. It's worth a trip just to check them out, even if you're out of range for the forest itself.<br />
<br />
The secondary reason? Taming chocobos. They make great pets and each colour offers a different utility - though Red would be my favorite, as it's a berserker with a lot to offer. <br />
<br />
Like I mentioned previously, there aren't very many mobs to kill. Maybe ten enemies in the entire area, assuming you can swim and/or fly, and then you have to wait for a repop.<br />
<br />
But again, like I mentioned before, the enemies drop some feathers - wands - which prove to be fairly useful if you remember to use them. It's just too bad you can't buy them in the shop.<br />
<br />
'''Connections: 2/10 '''<br />
<br />
There's only one place this really connects to, and that's the road outside of Wutai. The plus side, is it's super quick and easy to get to whether you're coming from the pier or walking through Truce Canyon. You don't even have to worry about recall scrolls because it's such a short distance. It's just a shame there isn't an area beyond it. <br />
<br />
<br />
'''Personal'''<br />
<br />
Great zone, very iconic. Easily one of my favorite areas when I was a lower level. Just wish it was more populated. Throw out some chocobo eaters and some extra chocobos or something, you know?<br />
<br />
<br />
----<br />
<br />
'''Player: RedMage(Wizard/26)''' - Token'd<br />
<br />
'''Review Date(s): 3/15/18'''<br />
<br />
Under Descriptions, I will list all of the typos/bad Engrish I've encountered while minimizing potential spoilers. I'll be posting only partial room descriptions to point these things out. Attractions has some problems too. Some of my comments are maked by ((parenthesis)).<br />
<br />
*EDITOR NOTE As we address these errors and other types of description afflictions, we'll be deleting these comments to keep track of what has and has not been addressed. Thanks for the handy checklist!<br />
<br />
'''Descriptions/Problems: 1/10'''<br />
<br />
>talk breeder<br />
You think 'Do you have any work needs doing?'<br />
((*Do you have any work that needs doing?))<br />
You think 'I've got the feathers you wanted!'<br />
((This line showed up the first time I talked to him then mysteriously disappeared the second time, strange.))<br />
<br />
*Chocobo Forest - Riverside Path<br />
creatures drinking from the water. A river crossing made up of solid white<br />
((Why can't I drink the water? Other rooms describe it as being pristine and pure.))<br />
<br />
*Choco Falls - East Side<br />
The river that the waterfall creates flows gently to the norhtwest,<br />
((*northwest.))<br />
<br />
*Top of the Cliff<br />
A small alcove set agains the side of the mountain, accessible only by climbing from the plateua below.<br />
((*against, *plateau.))<br />
<br />
*Stepping Stones<br />
To the south you can spy a waterfall at its origin.<br />
((There's that you again.))<br />
<br />
*Singed Forest<br />
woods, aside from the occasional reslilent tree proving too stubborn to die. The cause of the devestation is made strikingly clear from the constant<br />
((The only thing that's strikingly clear are these typos. *resilient, *devastation.))<br />
patrol of crimson fowl, their sharp determined glare speaks volumes of their disdain for anyone who would intrude upon their sacred ground. <br />
((What crimson fowl?))<br />
<br />
*Chocobo Trail<br />
To the northwest you can spot a large clearing surrounded by thick brush and large rock formations. To the east the trail widens, and you can hear the faint sound of running water in the distance. <br />
((I should start a 'you' counter.))<br />
<br />
*Chocobo Lake: Shallow Water<br />
The creatures in this lake live in a peculiar casual harmony, the chocobos acting as both predator and proector, another sign of their strange but astonishing intelligence.<br />
((Their intelligence is so astonishing that they have become the legendary proectors of the forest. *protector))<br />
<br />
*While in ??? foggy rooms<br />
Looking around you see:<br />
This doesn't matter probably? , right here.<br />
((GUESS AGAIN MOTHERWARKER!))<br />
<br />
*Cumulus Ridge<br />
Comfortable and sturdy, it provides an excellent place to lean against or sit for a spell without fear of falling to the ground below.<br />
((So why is there no furniture to rest on?))<br />
<br />
*Chocobo Forest - Chocobo Paradise <br />
<br />
(] Exits: sw [)<br />
A shimmering golden chocobo observes you sagely.<br />
Choco is sitting here.<br />
Choco is sitting here.<br />
An enormous, rotund chocobo occupies a throne here, endlessly devouring a pile of food next to him.<br />
((Choco look, it's your long lost twin brothers! I wonder how many Chocos we'll get in here before a despawn prog is put in.))<br />
<br />
Throne extra desc<br />
At the side of the throne sits a giant pile of food of every type and variety.<br />
((Why not just list some greens?))<br />
<br />
*Fat Chocobo's ?????<br />
seals off any hope of escape. <br />
((Divine recall is reserved for those of lower levels than you. - GUESS AGAIN MOTHERCLUCKER! Huh, deja vu.))<br />
is lined with a series of protusions which should allow safe descent;*<br />
((Not that anything has had any extra descriptions in this zone, but it'd be nice to know what those protusions are that I can climb down. Erm, I mean *protrusions.))<br />
<br />
*After Recalling with Choco present at any time<br />
((So nice of Choco to wait for me if I recall while he's following and return later. That can get messy fast if people keep abandoning their Chocos and nothing is there to despawn them.))<br />
<br />
*Chocobos going past the boulder<br />
((Hey wouldn't it be nice if the only red chocobo in the entire zone wandered past the boulder where no one who's done the quests yet could get to it to attempt to grind for red chocobo feathers? That can totally happen.))<br />
<br />
pecks you hard on the forehead! ( (39))<br />
That'll yeach ya!<br />
((That sure did yeach me.)<br />
<br />
((Post-Mene Quest Choco no longer seems to be afraid of fighting. It can now be a useless follower, yay!))<br />
<br />
*Aspik description<br />
Its body is extremely weak and vulnerable to physical attack, and its sole tendril fares poorly in combat. In order to survive the Aspik has developed a natural defense in the form of an extremely high voltage current, which it can generate at will. <br />
((Hey thanks, now I don't have to read an analysis scroll!))<br />
<br />
*Mene the Moogle's description<br />
All other ways, however, Mene stands alone. An outcast from his moogle brethren, he identifies more with his best friend Choco than anyone from his own race. Alone together, they travel to find their place in the world.<br />
((Well I'm glad I got to know Mene better just by looking at him.))<br />
<br />
*Choco's description<br />
Choco is no different; though smaller than most and strangley distant from his choco brethren. Choco is particuarly gifted in his intellect, especially in his ability to determine a person's worth. A shy bird, Choco's only friend is a moogle named Mene. Alone together, they travel to find their place in the world. <br />
((Well I'm glad I got to know choco better just by looking at him. Huh, deja vu. *strangely, *particularly))<br />
<br />
''In summary: Most of the room descriptions are okay, typos can be fixed, but they are lacking severely in extra descriptions. There are many instances of capitalized improper nouns and the hidden areas are really easy to find (found them all before I was even tasked to). What really drags this score down are the mob descriptions. There is a lot of copy and pasting across the different chocobos as well as background elements in some parts, which don't belong in a mob's description. This area is also lacking in furniture/fountains/fishing spots/mining spots, all the things that make a zone interesting.''<br />
<br />
<br />
'''Balance: 7/10'''<br />
<br />
While I have a bit more HP/Mana than most Wizards at my level, my armor was 100's across and I had vulnerability to Pierce, which EVERYTHING here uses. Despite these drawbacks I didn't have much trouble fighting anything. Red Chocobos could pull me down pretty quickly if I failed enough casts. They're also resistant to mental for some reason, so watch out Dancers! The other mobs had reasonable resistances/vulnerabilities and their combat progs certainly filled them with some life.<br />
<br />
The main problem here is that there's BARELY any chocobos to fight. This ties into the quest mentioned below, so if these reviews are to accomplish anything, Chocobo Forest needs more spawns. A lot of spawns. Maybe even a few other critters from the source material (or from the cleft. Chocobos are Pokemon, aren't they? Look how they evolve into new colors! Someone should CATCH THEM ALL!).<br />
<br />
Oh yeah, no mobs reward any money, at all. That's most likely a bug so I won't subtract any points, but it certainly needs to be addressed.<br />
<br />
<br />
'''Attractions/Problems: 0/10'''<br />
*Loot<br />
The Sky Armor now follows you.<br />
((Oh, uh...ok. Thanks? Wait, your name is SKY ARMOR and you can't fly? How are you even..nevermind. Nice lack of teleport prog there, too.))<br />
[*SAY*] The Sky Armor 'I can wear equipment in these locations:'<br />
[*SAY*] The Sky Armor 'Hold, float, and light.'<br />
[*SAY*] The Sky Armor 'I have 4 damroll 6 hitroll 0 magroll. My average damage is 22.'<br />
[*SAY*] The Sky Armor 'My armor modifies damage by 105 / 105 / 105 / 105 percent. I have 0 Saves.'<br />
((Well aren't you a keeper. No wonder you were free.))<br />
<br />
Chocobo Wing(L32) is uh...semi-mediocre. Garbage as a shield since its -AC is worse than a L10 shield and there are better ways to get Haste. A +Dex shield with proper AC would probably be better.<br />
<br />
The Dislodge Quest Reward isn't clear about what level you have to be to use it. I'm L31 now and I still can't use it properly.<br />
<br />
''-Quest Issues-''<br />
*Mene Quest<br />
Mene says 'But...this place is way too big, and there's dangers all around. Sad to say, but I'm simply of no help to choco in this situation...'<br />
((I left all the capitalized non-proper nouns alone in the room descriptions, but I think Mene owes his buddy a capital C at the very least. Mene's dialogue is very uh, interestingly spaced out by the way.))<br />
You think, "No thanks."<br />
((This option literally does nothing.))<br />
Mene takes a moment to catch his breath<br />
((Hey Mene finally decided to do an emote instead of spamming say, too bad he forgot his period.))<br />
<br />
((Mene seems to enjoy copy and pasting parts of his dialogue between quest sessions. Choco definately enjoys copy and pasting throughout when QINFO happens.))<br />
<br />
Mene says 'I guess I'll have to forgo a life in the lap of luxury...but hey, at least I can always pay for food from that Chinese Delivery place.'<br />
((Not for long!))<br />
You say 'I lost my [QINFO ITEM], can I have another?'<br />
Mene says 'Sure! Here you go! '<br />
(10) [QINFO ITEM] is here.<br />
((Miiight want to add melt_drop to those suckers. Too bad I'm not L30 yet, I'd totally max Artifice here.))<br />
<br />
Mene says 'Sorry, looks like your party's a little too full, Choco's really shy.'<br />
((I know other zones use pet mechanics, but does Chocobo Forest really -need- one? You can't even order Choco to do anything let alone get in a battle with it. Well Sky Armor, it's been nice while it lasted. ...You uh..you can go home now. You know, wander on home? HOME! Shoo!...or you can just stay at Mene, that's fine too.))<br />
<br />
((A mob post-Mene Quest has a description that describes the outcome of Mene Quest when you look at it. Spoilers!))<br />
<br />
*Chocobo Breeder Quest<br />
((Chocobo Breeder Turn-in didn't remove the black and blue feathers from my inventory. Free items!))<br />
<br />
*Dislodging Quest<br />
((This is handled pretty messily. Can't go into detail because it's qinfo, but anyone is welcome to message me in private if they want the details as to why I say that. I'll just sum it up as 'It can be progged better.' It's also level locked.))<br />
*Fat Chocobo<br />
Fatty C says 'Well, well, well, what do we have here? QINFO, I haven't had one of those in ages! '<br />
((I always wanted to call the Fat Chocobo Fatty C and make fat jokes about it.))<br />
*Dislodge Quest Boss<br />
((Um...it's really hard to talk about this without breaking QINFO rules. Just like above, anyone is free to ask me in private if they want a detailed opinion. But it's really BAD. On-kill dialogue makes NO sense and it is a very immature way to implement a very notable boss from its source material.))<br />
<br />
''Summary: The quests are boring and unimaginative. There is no immersion, there is no reason why you should care about anyone or anything in this zone. There were so many ways the quests here could have been better and more clefty and the finale is just downright immature. There are not enough mobs to support the fetch quest or its other level locks. The quest rewards aren't worth the effort either.''<br />
<br />
<br />
'''Connections: 1/1'''<br />
<br />
Chocobo Forest fits where it's been connected to. What else is there to say? It does its job on this front. 1/1.<br />
<br />
<br />
'''Personal'''<br />
<br />
*Breeder's Courtyard<br />
It definitely smells like chocobo here, for all the wrong reasons. <br />
((Well I did keep saying this was a shitty area, seems the zone itself agrees.))<br />
<br />
*Chocobo Breeder Quest<br />
((This quest is awful. You need to turn in items dropped by mobs in the area, which there are very, VERY few of.))<br />
<br />
*Chocobo Lake: Shallow Water<br />
This rather shallow section of the lake butts up against a high wall of rock and earth, making land access impossible.<br />
((Well that's just an excuse to put the word butt in the description. I guess this area really is ass.))<br />
<br />
*Chocobo Lagoon<br />
The walls sparkle with occasional gems, but are otherwise bare and smooth. <br />
((I want those gems. Why can't I mine them?))<br />
<br />
Redmage's group:<br />
[ 0 Mob] Choco 501/ 501 hp 0/ 0 mana 100/ 100 mv 0 xp<br />
[26 Wiz] Redmage 505/ 505 hp 593/ 593 mana 490/ 490 mv 59017 xp<br />
((I feel like Choco should just ride me.))<br />
<br />
You are in Chocobo Forest. Have you:<br />
- Talked to the friend of a Chocobo?<br />
- Discovered the truth behind the legend?<br />
- Dislodged an obstruction?<br />
- Finished a stupid fetch quest?<br />
((I guess even the zone acknowledges one of its quests is stupid.))<br />
<br />
''Final Observation: It looked like Ademisk was pretty good with the combat from the source material and I wouldn't mind seeing him in charge of designing possible action heavy events in the future. Just leave the creativity to someone else.''<br />
<br />
<br />
----<br />
<br />
'''Player: Poochie(Geomancer/27)''' - Token'd<br />
<br />
'''Review Date(s): 3/16/18'''<br />
<br />
<br />
'''Descriptions: 6/10'''<br />
<br />
Some of the room descriptions are somewhat clunky and awkward to read. There are several spelling and grammatical errors sprinkled throughout as well. Some sentences are fragments entirely, while others lack or misuse certain types of punctuation. One room in the float section of the area is particularly clunky with multiple errors. Some rooms may need to be entirely rewritten to fix these types of problems.<br />
<br />
Aside from logistics, the descriptions are adequate on a room by room basis. The area is set up in different types of terrains, somewhat quartered off from each other, which makes reading through them interesting. The rooms linking the different terrains describe their transitions adequately for some areas, but not so much for others, specifically the forest into mountain sector. It's mentioned, but easily overlooked.<br />
<br />
In the Scorched Forest quadrant of the area, three of the rooms suddenly lack the "Chocobo Forest" title. They become one phrase titles in the default room name color. If this is intended, it's somewhat odd and makes it feel somewhat disjointed.<br />
<br />
The chocobos are fancifully described for the most part, with one exception - the first sentence appears copy-pasted and simply altered for colored adjectives of each chocobo. The black chocobo's description is disjointed, as it starts off describing them as 'standing' on their legs and ends with clarification that they are in fact floating. It's also clear they are floating from the fact that they are only in the float area. The copy-pasting of the first sentence is likely to blame for this inconsistency, as all the other chocobos begin with the same 'standing' sentence. <br />
<br />
<br />
'''Balance: 6/10'''<br />
<br />
The yellow chocobos in the beginning of the area are rather easy. The red chocobos are slightly dangerous, especially for a caster with their use of bash. This would make sense, since the yellow ones are 25 and the red ones are 30. The problem I see with this specifically is that it's not like there is a large amount of progress to make between the beginning of the area and the "end". Additionally, there are only 2-3 (that I could tell) of each chocobo type and not many other mobs. An entire five level difference in this area seems somewhat broad considering it's mostly quest focused. In order to not be highly threatened by the higher level mobs in this area, you have to level elsewhere and come back at the high-end of the level range, more or less, unless you're a remorter or of a particular class.<br />
<br />
<br />
'''Attractions: 4/10'''<br />
<br />
The 'first' quest has a strange set-up, where when you go into the room you can't actually begin the quest until you 'come back later'. I'm not sure if this is just as simple as leaving and re-entering the room immediately, as I actually did go out and read some more room descriptions and what not at that point. Mene abrutly speaks with you, and then says that he is busy if you speak with him afterwards.<br />
<br />
You are required to dismiss your pet to begin this quest, which is never something people are excited about. It also is likely entirely unecessary, especially because Mene explicitly states that Choco will not engage in combat. There is no benefit to having Choco be your actual pet rather than simply follow you.<br />
<br />
The area lists one of its own quests as "a stupid fetch quest" and it is unfortunately right on the money. This collection quest requires a drop from one of each of the chocobo types, of which, as mentioned, there are only 2-3 reset into the area at a time. Even doing this passively while working on the other quests may not net you all of the items and it could easily be incomplete by the time you're done everything else. There is nothing else to do except leave the area and wait for it to repop, come back, and hope - or just not do the 'final' quest.<br />
<br />
The other aspects of the quests are adequate, if unexpected.<br />
<br />
There are some pets here, which may be enticing for some, but unfortunately they lack some of the normal, expected functions of most pets. They also don't despawn on dismissal. There are some interesting quest rewards and there is a useful item for a relatively low level, readily available. There are too few mobs here with no other similar level areas nearby where it could be considered a pit stop to kill everything and then move on to somewhere else. <br />
<br />
I would recommend it if someone were specifically looking for something that they could find here, but probably not for leveling purposes.<br />
<br />
<br />
'''Connections: 3/10 '''<br />
<br />
Chocobo Forest sort of pops out of nowhere and doesn't seem to have any connection to the area around it. Logistically, it's easy to find and not too far for its level range. It is, however, the end of the line for anything else in that direction, which feels odd for some reason. <br />
<br />
<br />
'''Personal'''<br />
<br />
Despite several rooms clearly describing forests and trees, there was only a default level of overgrowth in one such room that I attempted to fight in. In reference to Mene's speech when you enter the room, the extra spaces between output lines is annoying. There don't need to be extra spaces for any reason, and anyone with compact off is going to be spammed by it.<br />
<br />
Of note, if you do happen to die in the swim or float areas, you either need assistance to retrieve your corpse or you have to necro your corpse, unless you can float or swim naturally.<br />
<br />
----<br />
<br />
'''Player: Alyse Wizard/39 no remort - Token'd<br />
<br />
'''Review Date: March 2018'''<br />
<br />
<br />
'''Descriptions 1/10'''<br />
<br />
While some things can certainly be overlooked, it is hard to ignore the abundance of issues in Chocobo Forest with the writing. It is littered with typos, awkward grammatical errors, bland and lacking in substance, minimal with extra descriptions, as well as full of useless repetitive ideas used in order to make the rooms appear more fleshed out at first glance out than they actually are. Sometimes they are even unclear in what idea they are trying to portray as some of the writing can allow for misinterpretation. There are even inconsistencies between the room descriptions and the exits.<br />
<br />
The room descriptions sometimes talk about the mobs that are in the area rather than the scenery and provide information that the player may not or should not know. For example many times it assumes that the player entering knows about chocobos, sometimes referring to their calls, signs, and smells but giving no description to exactly what any of those are like. While we can assume many of our players might have some familiarity with games we can't assume they have knowledge of all the content within the cleft or remember everything about the games they played, even when it comes to popular titles.<br />
<br />
More than once you can encounter places described as 'serene' or 'grimdark' which basically tell the player how they should be feeling about the area when time could be better spent setting the stage to show these things. 'You' also makes an appearance here more than once. This would be fine if the player was reading a Choose Your Own Adventure book, but it doesn't belong in a room description for a MUD. The area description should have no control over the player and should not be addressing the player in any way.<br />
<br />
NPCs when spoken to have weird random spacing in their dialogue and bombard the player with repetitive says for just about every single sentence with nothing like even a sigh, pause, or smile to break it up. When looked at, players are presented with their back story, or in the case of the chocobo's descriptions a copied and pasted description with no difference or variation aside from the bird's color.<br />
<br />
The only positive about the descriptions is that the use of color in some places is done well. Particularly when you are in a place obscured by fog.<br />
<br />
<br />
<br />
'''Balance 6/10'''<br />
<br />
Hopefully any pets the player has are not important to them or difficult to get because in order to do half the quests in this area they will have to be dismissed. This also goes for the pets you gain from the area itself as the Flying Armor will sometimes make itself the player's pet rather than attacking the player.<br />
<br />
The mobs seem to be decently balanced, and each are slightly different from one another as far as attacks go. The green chocobos assist each other which came as a surprise, and the red ones were appropriately aggressive by comparison to the others (even though getting slapped by stars seemed kind of silly for an attack).<br />
<br />
There isn't a whole lot to fight here though, making the place feel kind of empty and devoid of life. Save for the Aspik and the flying armor, the only things moving about the area are chocobos and they are not very plentiful in number, having only two mobs of each type wandering through each sub area. It is not a good place to level because of it. It makes it a pain when trying to collect a specific drop and produces a problem for players who enter the area at the minimum level requirement as some of the items in the area are level locked. Many will have to venture elsewhere or else deal with a slow and drawn out level grind.<br />
<br />
The area's final 'boss' really wasn't much of a boss. It did nothing to attack or defend itself for most rounds of fighting. While it eventually cast rainbow before it died it basically just amounted to the player hacking at it until it is out of hp making it no real challenge or threat.<br />
<br />
For the area's level, the reward for the last quest on the list is passable, but not particularly exciting. The reward in completing Choco's quest and dealing with the obstruction is either not working correctly, is not well explained, or has a ridiculous level requirement (I am 9 levels past the maximum level recommended for the area and still unable to use it).<br />
<br />
Players entering this area better hope they brought some money with them for the shop because the mobs here are sparse and do not drop any amount of gold or silver when they are killed. This isn't a huge issue though, as Wutai and its bank is just around the corner and easy enough to go back to when a player needs funds.<br />
<br />
<br />
<br />
'''Attractions 2/10'''<br />
<br />
There are also a lot of missed opportunities to add features such as mining, fishing or mini games to make the area more fun to explore. Especially since there is a lot of waiting involved in the area.<br />
<br />
*Talked to the friend of a Chocobo?<br />
<br />
There is not much to comment on about this quest as it just involves finding and talking to an NPC. It is simple enough, and not uncommon to see goals like this in some areas. You will have to wait before continuing on to the next quest on the list however. And while waiting for a quest isn't so bad, forcing the player to wait is used a bit too much in this area.<br />
<br />
*Discovered the truth behind the legend?<br />
<br />
This quest is a repetitive, dull game of hot and cold. While the idea itself isn't bad it wasn't very well executed. The quest goes as follows;<br />
<br />
Talk to Mene and take Choco → Enter a special room→ Talk to Choco → wait → exit room → wait again → Repeat<br />
<br />
The repetition wouldn't be so bad if there was some variation in the text. For example, Mene reacts by having to catch his breath and saying the exact same thing every time the player returns. While it is understandable the moogle could be startled by the appearance of the player and Choco suddenly appearing the first time, it doesn't make as much sense the 3rd or 4th time it happens. By then Mene should be expecting it to happen by that point.<br />
<br />
The waiting is also a bit annoying with the frequency in which it happens. Not only do you have to wait on Choco after finding each chest, but you have to wait again for Mene to talk to him regarding his new abilities. As mentioned in the Balance portion of the review, there really isn't a whole lot of things to do in the area during this downtime, and there is no indication as to just how long the downtime is.<br />
<br />
Part of what makes this quest so boring and tedious is a lack of variation when it comes to finding the locations of the treasure. All save for one can be found in rooms hidden only by extra descriptions. And by the time players get to this quest (Particularly those used to looking for hidden things in descriptions) they have likely already found all of these spots negating the need to even play the mini game with Choco in the first place. It isn't a far jump in logic to assume hidden places that have nothing in them are connected with finding the treasure chests for this quest.<br />
<br />
Some variation could go a long way and provide players with a little more challenge as they work their way through this quest. For example instead of only leaving the treasure in a hidden room (or completely out in the open at the end of the route as the last one is) What about putting them behind a puzzle, or placed at a seemingly random spot along the path that the player has walked past a dozen times? There is no increase in difficulty or challenge in locating them and it is the the same gimmick every time. The only obstacle getting in the way of the player is the wait time and traveling from point A to point B.<br />
<br />
*Dislodged an obstruction?<br />
<br />
Something tells me there needs to be a talk about maturity. While Chocobo Forest's other quests are bland with room for improvement, this one just ends up being flat out juvenile and inappropriate. The fat jokes, the boss's death line of “I'm a pretty princess, dammit!”, and the matter of both the player and reward being defecated from a bird's ass really isn't in the spirit of the source material. It's degrading to the player. Hopefully no one going through this part of the quest wanted to leave it with any degree of dignity. The only suggestion that can be made here is to just get rid of the entire thing.<br />
<br />
*Finished a stupid fetch quest?<br />
<br />
When an area calls its own quest stupid, it is basically telling the player they are not in for anything fun. You are basically required to collect feathers from different types of chocobo which may or may not be so easy to do as there are only 2 of each chocobo type and the drop is random. It is not particularly exciting or interesting.<br />
<br />
There are a lot of ways the 'Collect 20 Bear Asses' trope could be avoided. A possible way to make the quest more engaging and maybe a little less frustrating to players who just have poor luck would be to make obtaining the feathers more of a puzzle. Maybe each type of chocobo needs something and the player has to figure out how to help them in order to get the feather. It would even potentially make use of the breeder's hut and shop and maybe open up the possibilities in adding features to the surroundings.<br />
<br />
<br />
<br />
'''Connections 4/10'''<br />
<br />
The location is not the best nor the worst. It can be found roughly in a spot of similar leveled locations but at the same time it could go somewhere else if it needed and nothing would be lost. The only reference it makes in relation to its place in the world is a description mentioning Wutai in the distance. While it is tucked away in the corner of the continent, making it a little more hidden would be more fitting to the original content. It feels like an optional area.<br />
<br />
<br />
<br />
'''Personal'''<br />
<br />
I do not know why this area was linked. Even now after a number of immortals have combed through it and fixed things it still looks like a mess. Maybe it is less so than when first introduced to the players, but it is still a place I would consider low in quality and not one I would recommend unless an overhaul was done for the entire thing.<br />
<br />
Though not as demanding of attention as the balance or the mechanics, descriptions are an important part of the game. And that was one of my biggest disappointments here. Descriptions create a setting and tone for the player as they venture through each of the zones as well as provide important clues for the quests and puzzles they are to solve. They are what give the area life and personality. Most MUDs out there do not use their descriptions they way the Cleft does. It is something that the game prides itself upon when comparing it to other games out there so this is why the writing for an area should never be overlooked, its typos never brushed aside, and its inaccuracies and other flaws ignored.<br />
<br />
It is understandable to find a hiccup or two within an area and overlook something. But there are just so many problems here with the writing that it lessens the experience. It is kind of embarrassing to present this area to future players who might see these and develop an impression on the game and what is acceptable building standards based on them.<br />
<br />
There is potential to improve on it and make it a decent and even interesting. I am not suggesting it is so bad that it cannot be salvaged. It felt like there were a lot of missed opportunities to do something neat with the place. Rewrite and edit a large chunk of the descriptions, add more things to look at and see, clean up the weird quirks in the dialogue, add more mobs and this area, and completely drop everything beyond the boulder and would not be so bad. While it has improved since its first release, it still needs a lot of work and attention. <br />
<br />
----<br />
<br />
<br />
'''Player: Kolem (Various, primarily Playback L. 22 Dancer)''' - Token'd.<br />
<br />
'''Review Date(s): 3/23/18 '''<br />
<br />
Well, here we go. I haven't been looking forward to this, but sometimes that just means it's more necessary. Having read through the other reviews, I am going to do my best to focus on suggestions for improvement in areas that have not been extensively covered already, and thanks everyone for tackling this particular zone. It always stinks when a less than stellar area is up for review, because I have a harder time being negative than positive. But Chocobo Forest seems to fall into a contentious area: A lot of effort has gone into improving it already, and some are so frustrated they suggest just wiping it entirely. I don't feel that's quite needed, here; this is no Zork or old-version Lelanol. But I'll discuss this further in the personal section.<br />
<br />
As always, I begin each category at Five, with generalized positives and negatives swaying the score higher or lower as needed. Exceptionally poor or wonderful examples may merit points on their own.<br />
<br />
<br />
'''Descriptions: 4/10'''<br />
<br />
<br />
There have been countless detailed descriptions of the many issues with the descriptions in prior reviews. In order to avoid beating a zombie horse, I will say that most descriptions are technically functional but poorly implemented. There are very few look commands other than those utilized to hide specific areas, and since there are no non-consequential look commands, the area feels very hollow and the areas are easily discovered. I am going to ding one point for general poor implementation, but I have seen (much, much) worse.<br />
<br />
<br />
'''Balance: 3/10 '''<br />
<br />
<br />
Here is where I start to feel like the real problems of the Chocobo Forest come in to play, and as previous reviews have not really gone into extreme depth with the issues here, it's where I'm going to be focusing a fair bit of my attention.<br />
<br />
-Let's start with the items. Specifically, the lack thereof, and the imbalance on the items that exist in the zone. (This will tie in to the Attractions section shortly.) One of the primary quests in this location is to kill chocobos until at least three drop specific items--feathers corresponding to the color of chocobo in question. Given the low numbers of those mobs present and the general disapproval of the quest on Kill X Mob quests to start wish, this is an issue in and of itself. But the real issue I'm taking with this is that for some reason the dropped items are all one shot wands-and NONE of them are on level. Two are below, and one is above. It's straight up baffling. Additionally, the one store sells held items that grant either swim or float. You can get one of the two nearby if you're investigative, but by level twenty, the player will have had plenty of opportunities to get swim vehicles or equipment regardless of starting town. Purchasing float in any equipment slot is NICE, technically, but held is a very competitive spot--giving up a shield, weapon, or other bonus, to say nothing of two handed weapons. The quest reward items are also underwhelming, with one exception (which I will discuss in Attractions). Dead Peppers are ripe for change, as well; there is no reason not to make them an interesting pill and not unique.<br />
<br />
-Moving on from the items, let's discuss the early-zone mobs. Playing as a level twenty two dancer, defeating yellow, red, and green chocobos was fairly effortless. I recall Sky Armor being rough, and I grasp WHY these mobs are so weak, but there are other problems: Their low drop rate, the fact that they apparently award half experience if that, and complete lack of money, for starters. Aspiks were also a complete breeze. Given the nature of the farming quest this is particularly egregious. Even the reward for collecting all the feathers is outshone in general by various consumables obtainable elsewhere.<br />
<br />
Starting at 5 points:<br />
<br />
-1 for all items being level inappropriate<br />
-1 for mobs which are not built to challenge on-level players<br />
<br />
The boss and sky armors, as I recall, are somewhat rough; but gated behind float.<br />
<br />
<br />
'''Attractions: 5/10'''<br />
<br />
<br />
This is something of a difficult call. The upshot of the final portion of the quest here is that you can obtain any one of the chocobos as a pet--and they are surprisingly decent pets, for the level they are. However, players will need to be a higher level than the pets to obtain them, and there is considerable competition for the Pet / Companion slot as it is. They all lack wander-home progs, as well. I go into some alternatives in the closing section, but alone--as fun as flavorful having a Chocobo is, and as nice as them all having 'moves' are is, alone that can't balance the consequences of the rest of the zone. I will give the zone credit for attempting it, though. Chocobo forest is a terrible place to grind; with few monsters to challenge and fewer rewards. The one shop could use considerable tweaking. Additionally, it feels like the Item you get as a result of defeating the boss ought to have better implementation outside of its zone of origin. There are definite missed possibilities here.<br />
<br />
Beginning at five points:<br />
-plus one and a half points for an attempt at a full pet subcategory, which must have took concerted effort to pull off<br />
-Minus half a point for poor implementation of said mobs as pets<br />
-Minus one for the complete lack of valuable treasure, experience, and other rewards from the zone apropos to level<br />
<br />
Final score of this category is Five: It is *tolerable*, in this area, but any number of small or large adjustments or additions could really improve matters.<br />
<br />
<br />
'''Connections: 2.5/10 '''<br />
<br />
<br />
Oh. Oh dear. The issue with Chocobo forest is this:<br />
<br />
Chocobo Forest has all of one connection point. None of its items have major or minor consequences outside, even though in all fairness it seems like its quest item is the exact sort of item that could or should have small easter eggs or benefits used outside of its initial introduction. While its foresty introduction fits OKAY I GUESS with the outside, the complete mishmash of areas it itself is means it could technically be linked any sort of place, and I try to not give extra credit for bare minimums. This is a pity, but I would suggest focusing on improving the rest of the areas first--it has enough need for retools and improvement that improving linkage can take a back seat. This is a pity, as I go into in the personal section.<br />
<br />
'''Personal'''<br />
<br />
Whoof. Just... whoof. The problem with Chocobo forest is that the effort is SHOWING. There is a very hard=pressed debate currently over whether to nuke or improve the zone, since there has been a lot of effort into the zone already to improve it from its initial drop into the cleft, and it sounds like those improvements have started to take hold. I am never in favor of a complete gutting of a zone unless it is completely beyond the pale, and I do not think Chocobo Forest as it is now is in that territory. <br />
<br />
It just needs several passes and improvements. That probably isn't anything the imms want to hear, but there are opportunities inherent to Chocobo Forest that it would be criminal not to take advantage of.<br />
<br />
FINAL SCORE:<br />
<br />
Averaging four categories, Chocobo Forest gets an approximate '''3.5 / 10''' -- a score that is not beyond reach, but speaks out for significant need for improvements. <br />
<br />
Therefore in the interest of working toward a better, brighter cleft and Chocobo Forest, I will make some suggestions for improvement, from the least to most effort intensive on the part of the imms.<br />
<br />
--An Item and fetch quest Rebalance and reconsideration.<br />
There is no reason to gate the Fetch reward as it is. In fact, it is generally a lackluster item. I would suggest Chocobos 'disappear'--<br />
leaving a feather behind in their haste to escape. Whether these feathers remain wands or not is still up for evaluation; certainly some level<br />
or spell adjustment is needed. I would suggest changing them from mediocre protective or offensive spells to utility items, if this avenue is <br />
taken.<br />
<br />
--General redescing mobs and areas in a more cohesive, collective fashion. No one likes to do this, but the zone does need it. Refer to other reviews for specific trouble spots.<br />
<br />
--Reevaluating mob drop rates, spawn frequencies, and rewards.<br />
<br />
Now for some tougher suggestions:<br />
<br />
--Reevaluate whether Chocobos should be pets. There are two broad categories of idea I have for these birds, owing to their origin: One, if these mobs are to continue to exist as is, append a "ranch quest" to the end of the current questline wherein Caught chocobos follow you into a 'ranch' type area, where they will mill about and offer to follow the player not as a pet but a follower. Given the approximate level of the zone, it is a fantastic opportunity to teach players the mechanics of followers that are not pets. Refer to the Runaway Five for similar examples of this; this would mean fetching a chocobo and ensuring it stay with you via Gather wands or scrolls, which could be sold here, could be fantastic training for certain late-game rewards. Given the relatively low strength of individual chocobos, this is unlikely to break anything in any major way. Alternatively, a reward of an reusable cooldown event Chocobo Call for temporary assistance from a random bird would be a cool, flavorful addition that would be considerably more compact and random enough to be engaging. <br />
<br />
The second idea is that, for each breed of Chocobo caught and returned, the player could have a transport to a specific nearby location in the <br />
cleft corresponding to the Chocobos in question: Mandala for Green Chocobo, for instance; Rocket Town for Yellow Chocobo, etc. This would improve both the area's linkage and attractions, and it could be expanded through the use of the major quest reward to chocobos present outside this zone, such as the Chocobos on Luon Highway--a quick way to hop back to viorar if your recall was not set there--or the Kakkara Desert chocobo.<br />
<br />
I know this is a bit of an ask, but Chocobo forest is too nice a source material to waste, imo. Given the diverse nature of the cleft, it's no shock seeing these creatures find a place in it.<br />
<br />
<br />
----<br />
<br />
**Chocobo Forest has been reworked since this review.<br />
<br />
[[Category:Area of the Month]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2315Mprog Compendium2019-06-28T22:39:03Z<p>Pascal: </p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khcount if khcount $n > 30 - did $n kill more than 30 things?<br />
khexists if khexists $n 1234 - did $n kill a mob of vnum 1234? <br />
enchant if enchant $o > 10 - has $o been enchanted more than 10 times?<br />
<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;MCLONE:mob mclone <target><br />
This command creates a perfect duplicate of a target mobile, including any modifications to it, such as restring/face fields, equipment, inventory, affects, etc. It cannot clone PCs.<br />
<br />
;OCLONE:mob oclone <target> [I]<br />
This command creates a perfect duplicate of a target object, including any modifications to it, such as restringed fields, affects, etc. By default, it will load the cloned object into the room, regardless of where the original object was. "I" can be added to the command to force the new object to appear in the mob's inventory instead.<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [scaled]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'scaled' argument is optional, which causes awarded experience to scale by 0-200% based on the level difference between target and mob, like XP gained from kills. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area when not using scaled.<br />
<br />
It's possible to use 'mob award $i' but ONLY do this in event progs, where $i is the player.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;ADVANCE:mob advance <target> <value><br />
This command will advance the target to the specified level. This command MUST be used carefully, as it can reduce the target's level as well. The target can only be a player and not a mob. This command should also be used SPARINGLY as we should not be providing multiple level skips in the game and is mostly intended for use in RARE, PROMO-TYPE event objects and event content. To properly use this command without accidentally over- or under-leveling the player, the following set-up should be used, where the final 'mob counter' is the amount of levels you wish to grant the player:<br />
<br />
mob remember $n<br />
mob counter $B<br />
mob counter 1<br />
mob advance $n $z<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 16 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-16 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), alignment(#), wealth(#), damtype(a), hitroll(#), damroll(#), magroll(#), saves(#), dicecount(#), dicetype(#), acbash(#), acslash(#), acpierce(#), acexotic(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;RSET: mob rset <field> <value><br />
This allows a mob to temporarily edit the room they are standing in. These changes will not save through copyovers or crashes. Available fields: name <string>, desc <string>, heal <value>, mana <value>. There is a 255 character limit to 'mob rset desc <string>'.<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2295Mprog Compendium2019-06-20T16:33:14Z<p>Pascal: </p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [scaled]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'scaled' argument is optional, which causes awarded experience to scale by 0-200% based on the level difference between target and mob, like XP gained from kills. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area when not using scaled.<br />
<br />
It's possible to use 'mob award $i' but ONLY do this in event progs, where $i is the player.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;ADVANCE:mob advance <target> <value><br />
This command will advance the target to the specified level. This command MUST be used carefully, as it can reduce the target's level as well. The target can only be a player and not a mob. This command should also be used SPARINGLY as we should not be providing multiple level skips in the game and is mostly intended for use in RARE, PROMO-TYPE event objects and event content. To properly use this command without accidentally over- or under-leveling the player, the following set-up should be used, where the final 'mob counter' is the amount of levels you wish to grant the player:<br />
<br />
mob remember $n<br />
mob counter $B<br />
mob counter 1<br />
mob advance $n $z<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 16 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-16 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), alignment(#), wealth(#), damtype(a), hitroll(#), damroll(#), magroll(#), saves(#), dicecount(#), dicetype(#), acbash(#), acslash(#), acpierce(#), acexotic(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;RSET: mob rset <field> <value><br />
This allows a mob to temporarily edit the room they are standing in. These changes will not save through copyovers or crashes. Available fields: name <string>, desc <string>, heal <value>, mana <value>. There is a 255 character limit to 'mob rset desc <string>'.<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Atlas&diff=2279Atlas2019-06-15T12:57:16Z<p>Pascal: Created page with "The atlas is a full sized map of the Cleft. Certain areas are not drawn on it, as they may be in places like the sky, space, or other planes of existence. File:Atlas_pictu..."</p>
<hr />
<div>The atlas is a full sized map of the Cleft. Certain areas are not drawn on it, as they may be in places like the sky, space, or other planes of existence. <br />
<br />
[[File:Atlas_picture.png]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=File:Atlas_picture.png&diff=2278File:Atlas picture.png2019-06-15T12:55:18Z<p>Pascal: </p>
<hr />
<div></div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2277Mprog Compendium2019-06-09T20:05:56Z<p>Pascal: /* IFCHECKS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
It's possible to use 'mob award $i' but ONLY do this in event progs, where $i is the player.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;ADVANCE:mob advance <target> <value><br />
This command will advance the target to the specified level. This command MUST be used carefully, as it can reduce the target's level as well. The target can only be a player and not a mob. This command should also be used SPARINGLY as we should not be providing multiple level skips in the game and is mostly intended for use in RARE, PROMO-TYPE event objects and event content. To properly use this command without accidentally over- or under-leveling the player, the following set-up should be used, where the final 'mob counter' is the amount of levels you wish to grant the player:<br />
<br />
mob remember $n<br />
mob counter $B<br />
mob counter 1<br />
mob advance $n $z<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 16 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-16 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), alignment(#), wealth(#), damtype(a), hitroll(#), damroll(#), magroll(#), saves(#), dicecount(#), dicetype(#), acbash(#), acslash(#), acpierce(#), acexotic(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;RSET: mob rset <field> <value><br />
This allows a mob to temporarily edit the room they are standing in. These changes will not save through copyovers or crashes. Available fields: name <string>, desc <string>, heal <value>, mana <value>. There is a 255 character limit to 'mob rset desc <string>'.<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2272Mprog Compendium2019-05-28T14:18:23Z<p>Pascal: /* IFCHECKS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
It's possible to use 'mob award $i' but ONLY do this in event progs, where $i is the player.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;ADVANCE:mob advance <target> <value><br />
This command will advance the target to the specified level. This command MUST be used carefully, as it can reduce the target's level as well. The target can only be a player and not a mob. This command should also be used SPARINGLY as we should not be providing multiple level skips in the game and is mostly intended for use in RARE, PROMO-TYPE event objects and event content. To properly use this command without accidentally over- or under-leveling the player, the following set-up should be used, where the final 'mob counter' is the amount of levels you wish to grant the player:<br />
<br />
mob remember $n<br />
mob counter $B<br />
mob counter 1<br />
mob advance $n $z<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 16 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-16 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), alignment(#), wealth(#), damtype(a), hitroll(#), damroll(#), magroll(#), saves(#), dicecount(#), dicetype(#), acbash(#), acslash(#), acpierce(#), acexotic(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;RSET: mob rset <field> <value><br />
This allows a mob to temporarily edit the room they are standing in. These changes will not save through copyovers or crashes. Available fields: name <string>, desc <string>, heal <value>, mana <value>. There is a 255 character limit to 'mob rset desc <string>'.<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2243Mprog Compendium2019-02-24T14:58:36Z<p>Pascal: /* MOB COMMANDS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
It's possible to use 'mob award $i' but ONLY do this in event progs, where $i is the player.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;ADVANCE:mob advance <target> <value><br />
This command will advance the target to the specified level. This command MUST be used carefully, as it can reduce the target's level as well. The target can only be a player and not a mob. This command should also be used SPARINGLY as we should not be providing multiple level skips in the game and is mostly intended for use in RARE, PROMO-TYPE event objects and event content. To properly use this command without accidentally over- or under-leveling the player, the following set-up should be used, where the final 'mob counter' is the amount of levels you wish to grant the player:<br />
<br />
mob remember $n<br />
mob counter $B<br />
mob counter 1<br />
mob advance $n $z<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), alignment(#), wealth(#), damtype(a), hitroll(#), damroll(#), magroll(#), saves(#), dicecount(#), dicetype(#), acbash(#), acslash(#), acpierce(#), acexotic(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;RSET: mob rset <field> <value><br />
This allows a mob to temporarily edit the room they are standing in. These changes will not save through copyovers or crashes. Available fields: name <string>, desc <string>, heal <value>, mana <value>. There is a 255 character limit to 'mob rset desc <string>'.<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2242Mprog Compendium2019-02-24T14:56:34Z<p>Pascal: /* MOB COMMANDS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
It's possible to use 'mob award $i' but ONLY do this in event progs, where $i is the player.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;ADVANCE:mob advance <target> <value><br />
This command will advance the target to the specified level. This command MUST be used carefully, as it can reduce the target's level as well. The target can only be a player and not a mob. This command should also be used SPARINGLY as we should not be providing multiple level skips in the game and is mostly intended for use in RARE, PROMO-TYPE event objects and event content. To properly use this command without accidentally over- or under-leveling the player, the following set-up should be used, where the final 'mob counter' is the amount of levels you wish to grant the player:<br />
<br />
mob remember $n<br />
mob counter $B<br />
mob counter 1<br />
mob advance $n $z<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), alignment(#), wealth(#), damtype(a), hitroll(#), damroll(#), magroll(#), saves(#), dicecount(#), dicetype(#), acbash(#), acslash(#), acpierce(#), acexotic(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;RSET: mob rset <field> <value><br />
This allows a mob to temporarily edit the room they are standing in. These changes will not save through copyovers or crashes.<br />
Available fields: name <string>, desc <string>, heal <value>, mana <value><br />
There is a 255 character limit to 'mob rset desc <string'.<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2241Mprog Compendium2019-02-24T14:47:45Z<p>Pascal: </p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
It's possible to use 'mob award $i' but ONLY do this in event progs, where $i is the player.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;ADVANCE:mob advance <target> <value><br />
This command will advance the target to the specified level. This command MUST be used carefully, as it can reduce the target's level as well. The target can only be a player and not a mob. This command should also be used SPARINGLY as we should not be providing multiple level skips in the game and is mostly intended for use in RARE, PROMO-TYPE event objects and event content. To properly use this command without accidentally over- or under-leveling the player, the following set-up should be used, where the final 'mob counter' is the amount of levels you wish to grant the player:<br />
<br />
mob remember $n<br />
mob counter $B<br />
mob counter 1<br />
mob advance $n $z<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), alignment(#), wealth(#), damtype(a), hitroll(#), damroll(#), magroll(#), saves(#), dicecount(#), dicetype(#), acbash(#), acslash(#), acpierce(#), acexotic(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Flags_Compendium&diff=2240Flags Compendium2019-02-24T14:42:45Z<p>Pascal: /* BEHAV FLAGS */</p>
<hr />
<div>==FLAGS COMPENDIUM==<br />
===ROOM FLAGS===<br />
{|<br />
|dark || Need a light source <br />
|-<br />
|always_night || Room is always night; sun never rises, 'look sky' always shows stars.<br />
|-<br />
|no_mob || Mobs won't wander in here. Mobs on scripts and charmies are unaffected<br />
|-<br />
|indoors || Won't see [[weather]] or [[time|sunrise/set messages]]<br />
|-<br />
|private || Two people at a time<br />
|-<br />
|arena || Players don't leave corpses or lose XP when they die. Players also don't lose XP for fleeing combat.<br />
|-<br />
|safe || No fighting allowed<br />
|-<br />
|solitary || One person at a time<br />
|-<br />
|pet_shop || Can buy pets here. Pet cost is the 'wealth' of the mob, but purchased pets will be flat broke. Builders should reset the pet mobs into next room vnum.<br />
|-<br />
|no_recall || Can't recall from here<br />
|-<br />
|imp_only || MTS only<br />
|-<br />
|gods_only || Staff only<br />
|-<br />
|heroes_only || Also Staff only<br />
|-<br />
|newbies_only || Level 5 or less only<br />
|-<br />
|law || Prevents use of Charm, Tame, and Hypnotize spells (for some reason). Other stock ROM effects have been commented out.<br />
|-<br />
|nowhere || Can't Scan into this room<br />
|-<br />
|wilderness || Was supposed to involve some sort of overworld map? Doesn't do anything now.<br />
|-<br />
|overgrown_1 || Room has +1 level of overgrowth.<br />
|-<br />
|overgrown_2 || Room has +2 levels of overgrowth. This can stack with overgrown_1.<br />
|-<br />
|always_day || Room is always day; sun never sets, 'look sky' shows the sun.<br />
|-<br />
|lit || Room is always lit, don't require a light.<br />
|}<br />
====SECTOR====<br />
{|<br />
!Sector !! Movement Rate !! Properties !! Geomance Element !! Dance Element<br />
|-<br />
|Inside || 4 || Stays lit at night || Pierce || No effect<br />
|-<br />
|City || 4 || Stays lit at night || Bash || No effect<br />
|-<br />
|Field || 4 || || Slash || Pierce<br />
|-<br />
|Forest || 6 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Hills || 6 || || Slash || Pierce<br />
|-<br />
|Mountain || 8 || || Earth || Earth<br />
|-<br />
|Water (swim) || 4 || || Water || Water<br />
|-<br />
|Water (noswim) || 8 || Can't enter without a boat or the Swim affect || Water || Water<br />
|-<br />
|Unused || 1 || || Wind || No effect<br />
|-<br />
|Air || 4 || Can't enter without the Float affect || Wind || Wind<br />
|-<br />
|Desert || 8 || || Earth || Wind<br />
|-<br />
|Rock || 4 || || Earth || Earth<br />
|-<br />
|Road || 4 || || Wind || No effect<br />
|-<br />
|Enter || 4 || || Wind || No effect<br />
|-<br />
|Snow || 8 || || Cold || Cold<br />
|-<br />
|Swamp || 8 || || Water || Earth<br />
|-<br />
|Jungle || 8 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Ruins || 4 || || Bash || No effect <br />
|-<br />
|Mount2 || 16 || || Earth || No effect<br />
|-<br />
|Coastal || 4 || || Earth || Wind<br />
|-<br />
|Developed || 4 || || Bash || No effect <br />
|-<br />
|Void || 4 || || Wind || No effect<br />
|-<br />
|Lava || 8 || || Fire || Fire<br />
|}<br />
<br />
====[[Exits|EXITS]]====<br />
{|<br />
|door || Exit has a door -- Required for most other exit flags<br />
|-<br />
|closed || Door resets to closed<br />
|-<br />
|locked || Door resets to locked<br />
|-<br />
|pickproof || Door can't be picked<br />
|-<br />
|nopass || Door can't be Pass Door'd<br />
|-<br />
|easy || Pick Lock doesn't take many tries<br />
|-<br />
|hard || Pick Lock takes a few tries<br />
|-<br />
|infuriating || Keep pickin'<br />
|-<br />
|noclose || Door can't be closed<br />
|-<br />
|nolock || Door can't be locked<br />
|-<br />
|hidden || Exit can't be seen by normal means<br />
|-<br />
|swim || Only players who can fly or swim, or are on a flying or seaworthy [[vehicle]] can pass.<br />
|-<br />
|fly || Only players who can fly or are on a flying [[vehicle]] can pass.<br />
|}<br />
<br />
===MOB FLAGS===<br />
*Mobs with the None [[damage type]] will randomly have Slash, Pound, or Pierce.<br />
<br />
====FORM FLAGS====<br />
Most of these don't do anything. The ones that have a coded effect are listed below!<br />
{|<br />
|edible || Mob's parts are edible, and the corpse can be butchered into meat.<br />
|-<br />
|poison || Mob's edible parts are poisonous, and meat butchered from the corpse will be poisoned. Bloodsucking will poison the bloodsucker.<br />
|-<br />
|instant_decay || Mob doesn't leave a corpse at all. (Note: This means items on the mob are lost as well.)<br />
|-<br />
|animal || Mob is affected by the Tame spell.<br />
|-<br />
| || Mobs with any of the mammal, bird, reptile, amphibian, fish, or snake form flags can also be Tamed.<br />
|-<br />
|sentient || Mob is affected by the Hypnotize spell and can be haggled with if it's a shopkeeper.<br />
|-<br />
|undead || Mob takes extra non-elemental damage from weapons with disrupting weapon flag.<br />
|-<br />
|cold_blood || Mob has blood that can be bloodsuck'd.<br />
|-<br />
|warm_blood || Mob can be seen in the dark by characters with Infrared and can be bloodsuck'd.<br />
|}<br />
<br />
====PART FLAGS / WEARLOCS====<br />
Mob parts determine what equipment it can wear.<br />
<br />
{| <br />
! Wearloc !! Required Part flag<br />
|-<br />
|take || none<br />
|-<br />
|finger || fingers<br />
|-<br />
|neck || head<br />
|-<br />
|body || guts<br />
|-<br />
|head || head<br />
|-<br />
|legs || legs<br />
|-<br />
|feet || feet<br />
|-<br />
|hands || hands<br />
|-<br />
|arms || hands<br />
|-<br />
|shield || hands<br />
|-<br />
|about || guts<br />
|-<br />
|waist || legs<br />
|-<br />
|wrist || hands<br />
|-<br />
|shoulders || head<br />
|-<br />
|wield || hands<br />
|-<br />
|hold || hands<br />
|-<br />
|nosac || not actually a wearloc<br />
|-<br />
|wearfloat || none<br />
|-<br />
|face || head<br />
|}<br />
<br />
* The Brawling warrior style has special attacks that only execute if the opponent has certain parts; eye, tail, feet, or arms.<br />
* The guts, head, heart, arms, legs, and brains parts can cause dismembered mob organs to be created when the mob dies.<br />
* A mob requires the brains part in order to take any damage from the Brainbuster spell.<br />
* '''A mob without hands cannot hold items, use weapons, or equip shields.'''<br />
* Items which do not have the Take flag can't be sacrificed, so it is redundant to put nosac on these items also.<br />
* Items without a Take flag can't be held by players or mobs at all. Avoid resetting these onto mobs or trying to have mobs oload them.<br />
<br />
====ACT FLAGS====<br />
{|<br />
|sentinel || Mob won't wander between rooms (although it can still move if instructed to by an mprog).<br />
|-<br />
|scavenger || Mob will pick up takeable objects in the room, starting with the most valuable.<br />
|-<br />
|inert || Mob can't be seen in the room (but can still be interacted with).<br />
|-<br />
|omnisight || Mob can see everyone despite invisibility etc but can't necessarily see in the dark.<br />
|-<br />
|aggressive || Doesn't do anything; the code for this function has been commented out.<br />
|-<br />
|stay_area || Mob won't wander outside the area it was reset into.<br />
|-<br />
|wimpy || Mob will try to flee from combat at 20% hp or less.<br />
|-<br />
|pet || Mob is a pet? Probably reserved for pet code. Don't use this.<br />
|-<br />
|train || Players can Train at this mob -- defunct<br />
|-<br />
|practice || Players can Practice at this mob -- defunct<br />
|-<br />
|passive || Mob doesn't fight back with autoattacks, its current health isn't visible when you 'look' at it, nor will Peek work on it.<br />
|-<br />
|hyper || Mob wanders around real fast.<br />
|-<br />
|visdeath || Mob can only be seen by immortals and can't be interacted with by players.<br />
|-<br />
|mage || Mob gets -5 to Saves<br />
|-<br />
|thief || Mob has the Smokescreen skill<br />
|-<br />
|warrior || Mob has the Shield Block skill<br />
|-<br />
|noalign || Mob won't affect player alignment at all when killed.<br />
|-<br />
|nopurge || Mob can't be purged by immortals (the Mob Purge command from a mob can still affect these).<br />
|-<br />
|outdoors || Mob won't wander into Indoor flagged rooms.<br />
|-<br />
|indoors || Mob won't wander outdoors.<br />
|-<br />
|healer || Mob offers hardcoded heal-for-cash services (EG Selan).<br />
|-<br />
|gain || Doesn't do anything -- in stock ROM allows for gaining new skills.<br />
|-<br />
|update_always || Mob does things even when no player in the area.<br />
|-<br />
|changer || Mob is a [[bank]].<br />
|-<br />
|hyper_res || Mob takes 1/4 damage from sources it resists (instead of 2/3) and double damage from sources it's vulnerable to (instead of 3/2).<br />
|}<br />
<br />
Notes on wandering mobs:<br />
* When mobs try to move, they make three attempts. Each attempt, they pick a random exit in the room and then look at it more closely. If they can't move, they try again. If they can move, they do.<br />
* Mobs will not wander through closed doors (even if affected by pass_door) or into no_mob rooms.<br />
* Mobs with the stay_area flag will not wander between areas (which area its' vnum is in doesn't matter).<br />
* Mobs with the Outdoors flag won't wander into Indoors rooms. Mobs with the Indoors flag won't wander into rooms that aren't flagged Indoors.<br />
* Only Flying mobs will move into Air sector rooms. Only mobs with the Swim affect will move into any sort of water room. <br />
** A mob without the Swim affect ''will'' attempt to move into a noswim sector room (and fail to move, unless it has a boat object), but will not even try to get into a swim sector room unless it has the affect (even though it would be allowed to move there if it tried). This doesn't make a lot of sense but that's how it is.<br />
<br />
====ACT2 FLAGS====<br />
{|<br />
|doublexp || Mob gives double XP.<br />
|-<br />
|halfxp || Mob gives half XP.<br />
|-<br />
|noxp || Mob gives no XP.<br />
|-<br />
|noparts || Mob leaves no parts when killed.<br />
|-<br />
|sociable || Mob talks to or slaps people that use socials on it.<br />
|-<br />
|aquatic || Mob won't wander outside water rooms.<br />
|-<br />
|xpandahalf || Mob gives 1.5x XP.<br />
|-<br />
|adept || Mob uses skills at 100% (instead of 75%).<br />
|-<br />
|inept || Mob uses skills at 50% (instead of 75%).<br />
|-<br />
|carryall || Mob has no weight or item# limits.<br />
|-<br />
|priority || Mob will be targetted first by opponents with the AI_1 flag.<br />
|-<br />
|antihyper || Mob wanders especially slowly.<br />
|-<br />
|parsename || Mob will have a unique name as its first name when it resets.<br />
|-<br />
|noattack || Mob can't be attacked by anyone.<br />
|-<br />
|necromancer || Mob offers corpse retrieval for cash services, as Xzar, Caroline, etc.<br />
|-<br />
|raidmob || Mob can be attacked by anyone with no regard to 'kill stealing'.<br />
|-<br />
|carrynone || Mob can't pick up or be given items<br />
|-<br />
|passivelite || Mob won't auto-attack but still has visible health and such<br />
|-<br />
|ally || Is treated as a PC for some attack-safety purposes -- EG Ally mobs won't hit other Ally mobs with area attacks<br />
|-<br />
|shopkeepitems || Shop will not slowly discard items sold to it.<br />
|}<br />
<br />
====OFF FLAGS====<br />
A lot of these are affected by the adept/inept Act flags<br />
{|<br />
|area_attack || Mob hits everything that's fighting it with its normal attacks.<br />
|-<br />
|backstab || Mob is capable of using the Backstab skill, and would if it aggroed, but mobs don't aggro, so it does nothing.<br />
|-<br />
|bash || Mob has a 12.5% chance of using the bash skill, if it's not lagged.<br />
|-<br />
|berserk || Mob has a 12.5% chance of using the berserk skill, if it's not lagged and isn't already berserk.<br />
|-<br />
|disarm || Mob has a 12.5% chance of using the disarm skill, if it's not lagged. The mob needs a [[weapon]].<br />
|-<br />
|dodge || Mob can dodge melee attacks as a player with the dodge skill at 75%.<br />
|-<br />
|fade || Doesn't do anything.<br />
|-<br />
|fast || Mob attacks twice always, doesn't stack with Haste. Mob will ignore Slow if affected. Mob gets +2 DEX when spawned.<br />
|-<br />
|kick || Mob has a 12.5% chance of using the kick skill, if it's not lagged.<br />
|-<br />
|dirt_kick || Mob has a 12.5% chance of using the dirt kick skill, if it's not lagged.<br />
|-<br />
|parry || Mob can parry attacks; works half as often with no [[weapon]].<br />
|-<br />
|rescue || Mob will try to rescue the target of its target, if that target is at 50% hp or less.<br />
|-<br />
|tail || Mob has a 12.5% chance of.. not doing anything (the code for this attack is commented out).<br />
|-<br />
|trip || Mob has a 12.5% chance of using the trip skill, if it's not lagged.<br />
|-<br />
|crush || Mob has a 12.5% chance of using the smash skill, if it's not lagged.<br />
|-<br />
|assist_all || Mob will assist all other '''mobs''' that it sees fighting.<br />
|-<br />
|assist_align || Mob will assist other mobs with a similar alignment, chunked out to good/neutral/evil.<br />
|-<br />
|assist_race || Mob will assist other mobs of the same race.<br />
|-<br />
|assist_players || Mob will assist players as long as the player isn't more than 5 levels above them. This has precedence over the other assist flags.<br />
|-<br />
|assist_leader || If following someone, mob will assist its leader.<br />
|-<br />
|assist_vnum || Mob will assist mobs of the same vnum.<br />
|-<br />
|second_attack || Mob has the 2x-Cut skill.<br />
|-<br />
|third_attack || Mob has the 3x-Cut skill.<br />
|-<br />
|ai_retargeting || Mob will aggro onto players that have recently fled from it, and selectively hit targets with the Priority act flag. If the mob's attacks are ineffective, it will re-target randomly to another member of the same group.<br />
|-<br />
|ai_flees || Mob will flee from sandstorms, flurries, miasmas, wildfires, etc unless it's immune to the appropriate damage type.<br />
|-<br />
|ai_rests || Mob will rest when injured (hp<50%), stand up when it's recovered (hp>75%).<br />
|-<br />
|}<br />
* Only one of the various 12.5% flags can trigger in any given round. A mob will all eight will try to use one (and only one) every single round.<br />
<br />
====BEHAV FLAGS====<br />
{|<br />
|random_innate || Mob randomly has one of the 6 elemental innates. This creates one resistance and one vulnerability.<br />
|-<br />
|rand_phys_resist || Mob randomly resists one of bashing, slashing, or piercing.<br />
|-<br />
|rand_misc_resist || Mob randomly resists one or two non-physical elements.<br />
|-<br />
|rand_phys_vuln || Mob is randomly vulnerable to one of bashing, slashing, or piercing.<br />
|-<br />
|rand_misc_vuln || Mob is randomly vulnerable to one or two non-physical elements.<br />
|-<br />
|travelingpet || Mob will automatically teleport to its master as long as it has one, and will otherwise despawn itself unless it is inside of a petshop room.<br />
|}<br />
<br />
====AFFECT FLAGS====<br />
{|<br />
|blind || Character can't see anything! Mobs ignore this flag so their mobprogs work<br />
<br />
|-<br />
|invisible || Character can only be seen and targetted by things with detect_invis.<br />
|-<br />
|detect_evil || Character sees evil objects and characters with a red aura.<br />
|-<br />
|detect_invis || Character can see invisible objects and characters, and knows they're invisible.<br />
|-<br />
|detect_magic || Character sees a blue aura around magical objects.<br />
|-<br />
|detect_hidden || Character can see hidden objects and characters, and knows they're hidden.<br />
|-<br />
|detect_good || Character sees good objects and characters with a gold aura.<br />
|-<br />
|sanctuary || Character is permanently under the effects of Nayru's Love (half damage from everything).<br />
|-<br />
|faerie_fire || Character has a pink aura. Negates invisibility.<br />
|-<br />
|infrared || Character can see warm_blood mobs in the dark.<br />
|-<br />
|curse || Character is flagged as cursed. All skill effectiveness is reduced by 15% while this flag is applied, but the character is immune to the Curse spell.<br />
|-<br />
|solidified || Character is completely frozen!<br />
|-<br />
|poison || Character is flagged as poisoned. This flag has no affect on stats but the character can't be poisoned again. Regeneration is decreased while this flag is applied, however.<br />
|-<br />
|protect_evil || Character takes 2/3 damage from evil foes.<br />
|-<br />
|protect_good || Character takes 2/3 damage from good foes.<br />
|-<br />
|sneak || Character doesn't generate echoes when moving from room to room. Triggers GRALL but not GREET progs.<br />
|-<br />
|hide || Character is hiding. Using any command removes this effect.<br />
|-<br />
|sleep || Character is under the effects of ''permanent'' magical sleep!!<br />
|-<br />
|charm || Character is under the effects of a Charm spell. Don't use.<br />
|-<br />
|flying || Character is flying: reduced MV costs everywhere (by 1 per room), can travel into air sector rooms, and doesn't need a boat to travel into noswim sector rooms. Also immune to Trip and Earthquake.<br />
|-<br />
|pass_door || Character can walk through some closed doors.<br />
|-<br />
|haste || Character is under the effects of Haste: '''always''' gets exactly 1 extra attack in combat, but regenerates at half speed. <br />
|-<br />
|calm || Character is under the effects of the Calm spell. Character can't use berserk.<br />
|-<br />
|plague || Character is flagged as plagued. Regeneration is decreased but the player can't be hit with the Bio 2 spell.<br />
|-<br />
|locusts || Character is a swarm of locusts per the Plague Swarm spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|dark_vision || Character can see anything in any kind of darkness without a light source.<br />
|-<br />
|berserk || Character is under the effects of Berserk! Character can't cast spells, everything the character sees is red, and they get a 50% penalty to all saving throws.<br />
|-<br />
|swim || Character doesn't need a boat to enter noswim sector rooms.<br />
|-<br />
|regeneration || Character regenerates HP twice as fast!<br />
|-<br />
|slow || Character has a chance to simply not attack during combat. 2x-cut and 3x-cut chances are reduced dramatically. Ignored if the mob is flagged off_fast. Character also regenerates at half speed AND spends more MV when traveling.<br />
|-<br />
|scarecrow || Character is affected by the Scarecrow spell -- can't eat, drink, or move, and melee attacks do reduced damage.<br />
|}<br />
<br />
====AFFECT2 FLAGS====<br />
{|<br />
|focus || double mana regeneration<br />
|-<br />
|motivation || slight movement regeneration<br />
|-<br />
|theatrical || takes damage when receiving an affect<br />
|-<br />
|frenzy || grants extra attack<br />
|-<br />
|vampirism || ??<br />
|-<br />
|paralysis|| ??<br />
|-<br />
|fast|| no command lag when moving rooms (like vehicle fast)<br />
|}<br />
<br />
====SHIELD FLAGS====<br />
{|<br />
|charge || Character does 1.5x damage with all applicable spells. DOES NOT DISSIPATE UNLESS IT IS APPLIED BY THE CHARGE SPELL.<br />
|-<br />
|sabotaged || Character takes damage when using skills or spells.<br />
|-<br />
|hallucinating || Character is under the effects of the Mushroomize spell; all MUD output turns wacky.<br />
|-<br />
|terrified || Character may cower helplessly in combat, with a greater chance is the foe's level is higher than the character's. Also makes the character try to flee.<br />
|-<br />
|haunted || Character is tormented by minighosts.<br />
|-<br />
|confused || Character hits itself sometimes in combat.<br />
|-<br />
|stat enhancement || Character is under the effects of one of Sage Aura, Brilliance, Limber, Valor, or Vigor/Warcry and can't be affected by another one.<br />
|-<br />
|ice shield || Returns 20 to 30% of melee damage as bash-type damage<br />
|-<br />
|thorn shield || Returns 20 to 30% of melee damage as pierce-type damage<br />
|-<br />
|crystal shield || Returns 20 to 30% of melee damage as slash-type damage<br />
|-<br />
|osmosis || Character loses MP steadily. Also decreases MP regeneration.<br />
|-<br />
|volta || Character does not auto-attack but has double normal dodge chances.<br />
|-<br />
|manashield || Character has Mana Shield permanently up. It will give the 'your shield broke' message with every attack if they're at 0MP but they'll still take full damage.<br />
|-<br />
|kamikaze || Character is going to Detonate. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|zeal || Character fails all saving throws but receives a bonus to damage for each bad affect<br />
|-<br />
|bleeding || Character loses HP steadily. Some types of bleeding make you bleed worse than others!<br />
|-<br />
|undead || Character is a zombie with a relentless hunger for delicious brains. All text is dark gray, healing spells do damage instead of healing, and the poor bastard doesn't necessarily die when they drop below 0hp! This is distinct from the undead form flag.<br />
|-<br />
|oozaru form || Character is an oozaru and can't cast spells.<br />
|-<br />
|double image || Character has a double image. It will take one attack and then vanish.<br />
|-<br />
|ink || Character has been inked. Display is all goofed up with large black splotches.<br />
|-<br />
|seraph form || Character has seraph form and can't cast spells.<br />
|-<br />
|reflect || Spells targetted at the character bounce back the wrong way<br />
|-<br />
|surefire casting || Character has surecasting on.<br />
|-<br />
|jinx || Character has a 33% chance of dropping any [[weapon]] they're wielding in any combat round.<br />
|-<br />
|leechseed || Character is under the effects of the Leech Seed spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bees || Character is covered in bees which deal periodic damage.<br />
|-<br />
|choke || Character is affected by Choke and casts spells at 3/4 the normal strength.<br />
|-<br />
|endure || Character cannot be reduced below 1hp.<br />
|-<br />
|sheltered || Character is being sheltered by a friendly Templar. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bide || Character is using the skill Bide. *Cannot be set on a mob's template or applied by an item.<br />
|}<br />
<br />
Some of these affects can't be applied to a mob's template, only by spells; homing attack, stat enhancement, extension, kamikaze, short term combat effect, oozaru form, double image, seraph form, Jumi empathy, surefire casting, and leechseed.<br />
<br />
===OBJ FLAGS===<br />
For more details on object types see [[Flags Compendium/Obj Types]]<br />
<br />
{|<br />
|[[light]] || Light sources, go in a special 'light' slot when equipped no matter what wear flags you use<br />
|-<br />
|[[scroll]] || Can be recited or read to cast 1-4 spells on a target. Works from base inventory, consumed when used, uses [[Artifice]] skill.<br />
|-<br />
|[[wand]] || Can be zapped or used to cast 1 spell a set number of times on a target. Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[staff]] || Can be brandished or used to cast 1 spell a set number of times on all targets in a room! Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[weapon]] || Changes wearer's melee autoattack damage to the type and amount specified in the object. Must be in the Wield slot to work.<br />
|-<br />
|[[treasure]] || No inherent properties, reserved for salable loot.<br />
|-<br />
|armor || Modifies wearer's armor values. Can be equipped anywhere.<br />
|-<br />
|[[potion]] || Can be quaffed or drunk to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|-<br />
|[[furniture]] || Various flags allow characters to sit, rest, stand, or sleep on, in, or at these objects. Recovery rates can be modified as well.<br />
|-<br />
|[[trash]] || No inherent properties, reserved for nonsalable loot.<br />
|-<br />
|[[container]] || Object that holds other objects. Can be closable/lockable like a door.<br />
|-<br />
|[[drinkcontainer]] || Holds a set quantity of a certain [[liquid]]. Liquids can be replaced with different liquids. Disappears when empty unless NOEXPLODE is set.<br />
|-<br />
|[[key]] || Object vanishes on logout. Has no other properties.<br />
|- <br />
|[[food]] || Can be eaten for food/full value and cast 1 spell on the eater.<br />
|- <br />
|[[money]] || Is abstracted into current wealth when picked up by a player. Dropped wealth turns into a money object. The Priest class can sacrifice money to recover mana for 1 MP per 50 silver.<br />
|- <br />
|boat || Can be equipped or in base inventory for players to move in water rooms. Defunct.<br />
|- <br />
|npccorpse || NPC [[Corpse]]. Reserved.<br />
|- <br />
|[[fountain]] || Like a drinkcontainer but the [[liquid]] inside can't be poisoned. Drinkcontainers can also be 'fill'ed from it.<br />
|- <br />
|[[pill]] || Can be eaten to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|- <br />
|protect || Uncoded junk. Don't use.<br />
|- <br />
|map || Uncoded junk. Don't use.<br />
|- <br />
|[[portal]] || Objects that can be 'entered' to take the character to a set room. Can be closable/lockable like a door.<br />
|- <br />
|warpstone || Used to be necessary for the Nexus spell.<br />
|- <br />
|roomkey || Uncoded junk. Don't use.<br />
|- <br />
|gem || Uncoded junk. Don't use.<br />
|- <br />
|[[jewelry]] || No inherent properties. Used for equippables that aren't armor.<br />
|- <br />
|[[Event Item|event]] || An object with both charges and cooldown capability, which executes an mprog when 'zap'ped or 'use'd. Uses [[Artifice]] skill.<br />
|- <br />
|slotmachine || <s>Type "Game slots" at a slot machine to spin the wheel. Slot machines can have their cost and jackpot size specified in the object template.</s> Just kidding! Disabled.<br />
|- <br />
|gun || Uncoded junk. Don't use.<br />
|- <br />
|ammo || Uncoded junk. Don't use.<br />
|- <br />
|[[vehicle]] || Vehicles allow players to consume less movement points as they travel, move faster, and/or travel to rooms they can't enter on foot.<br />
|- <br />
|exit || Uncoded junk. Don't use. Not the same as a real [[exit]].<br />
|- <br />
|[[rod]] || Can be zapped or used to cast 1 spell on a target with a set delay between uses. Must be equipped, any slot is OK. Uses [[Artifice]] skill.<br />
|}<br />
====EXTRA FLAGS====<br />
{|<br />
|glow || Item can be seen in the dark, shows (glowing) before its short desc<br />
|-<br />
|hum || Item shows (Humming) before its short desc<br />
|-<br />
|norecharge || Wand, staff, rod, or event can't be recharged with the Recharge spell.<br />
|-<br />
|autoconsume || Item is automatically used as soon as it's picked up off the ground. Works with [[potions]], [[pills]], and [[artifice]] items.<br />
|-<br />
|evil || Item has a red aura if you can detect evil, can be removed with Bless.<br />
|-<br />
|invis || Item can only be seen if you have detect invis, and shows (Invis) if you can<br />
|-<br />
|magic || Item shows as magic if you can detect magic<br />
|-<br />
|nodrop || Item can't be dropped, can be removed with Bless<br />
|-<br />
|bless || Item has a blue aura if you can detect good, can't be poisoned, and is a little easier to enchant. Is removed by Curse.<br />
|-<br />
|noremove || Item can't be removed. This flag is removed by uncursing<br />
|-<br />
|inventory || Item is part of a shopkeeper's inventory and will be sold with infinite quantity left. Also evaporates when the holder dies, like rotdeath.<br />
|-<br />
|nopurge || Item can't be purged. Use sparingly!<br />
|-<br />
|rotdeath || Item poofs when whoever is holding it dies. If a mob dies with one of these, it will vanish.<br />
|-<br />
|visdeath || Item can only be seen by immortals<br />
|-<br />
|uncounted || Item doesn't count against the holder's carry number or weight capacities.<br />
|-<br />
|nonmetal || Item is unaffected by Heat Metal<br />
|-<br />
|meltdrop || Item poofs when dropped or stolen. If a mob dies with one of these, it will appear in the room. <br />
|-<br />
|decaying || Item loses 1 condition per minute, then disintegrates.<br />
|-<br />
|sellextract || Item poofs when sold to shopkeeper -- doesn't show up in their inventory<br />
|-<br />
|nodestroy || (AKA burn_proof in the code for some reason) Item can't be poisoned, and can't be destroyed by various item-destroying affects (which I think are disabled)<br />
|-<br />
|nouncurse || Item can't be uncursed. (nodrop, noremove flags)<br />
|-<br />
|runic || Unused<br />
|-<br />
|adhesive || Item stays with a player, not on their corpse<br />
|-<br />
|nochk || [[Wand]], [[Scroll]], [[Staff]], [[Rod]], and [[Event Item|Event]] items with this flag won't check a character's [[artifice]] skill when used, but just always work<br />
|-<br />
|noremort || Item can't be carried through a remort<br />
|-<br />
|inert || Item doesn't appear in rooms its in<br />
|-<br />
|noexplode || Wand and staff type item won't disintegrate when their charges are used up. Drinkcontainers won't poof when empty.<br />
|}<br />
<br />
====EXTRA2 FLAGS====<br />
{|<br />
|antihuman || Can't be equipped by Human race<br />
|-<br />
|antimoogle || Can't be equipped by Moogle race<br />
|-<br />
|antisaiyan || Can't be equipped by Saiyan race<br />
|-<br />
|antiesper || Can't be equipped by Esper race<br />
|-<br />
|antihylian || Can't be equipped by Hylian race<br />
|-<br />
|antikokiri || Can't be equipped by Kokiri race<br />
|-<br />
|antigiganto || Can't be equipped by Giganto race<br />
|-<br />
|antimatango || Can't be equipped by Matango race<br />
|-<br />
|antireploid || Can't be equipped by Reploid race<br />
|-<br />
|antikoopa || Can't be equipped by Koopa race<br />
|-<br />
|antipmpkn || Can't be equipped by Pumpkinhead race<br />
|-<br />
|antiknight || Can't be equipped by Knight class<br />
|-<br />
|antiwarrior || Can't be equipped by Warrior class<br />
|-<br />
|antithief || Can't be equipped by Thief class<br />
|-<br />
|antiwizard || Can't be equipped by Wizard class<br />
|-<br />
|antipriest || Can't be equipped by Priest class<br />
|-<br />
|antigeomancer || Can't be equipped by Geomancer class<br />
|-<br />
|antisummoner || Can't be equipped by Summoner class<br />
|-<br />
|antifemale || Can't be equipped by female characters<br />
|-<br />
|antimale || Can't be equipped by male characters<br />
|-<br />
|antineuter || Can't be equipped by sexless characters<br />
|-<br />
|cursed || Item becomes noremove when equipped<br />
|-<br />
|unique || Characters can't pick up one of these if they already have one.<br />
|-<br />
|remortable || Item was carried through a remort and won't vanish on logout if it's out of the player's level range.<br />
|-<br />
|antinu || Can't be equipped by Nu race<br />
|-<br />
|antikirby || Can't be equipped by Kirby race<br />
|-<br />
|antilobsterman || Can't be equipped by Lobster race<br />
|-<br />
|antiranboob || Can't be equipped by Ranboob race<br />
|-<br />
|antijumi || Can't be equipped by Jumi race<br />
|-<br />
|antidancer || Can't be equipped by Dancer class<br />
|-<br />
|antimob || Can't be equipped by mobs<br />
|}<br />
<br />
* NOTE: Old classes are affected by antiwizard, etc, just as new ones are.<br />
<br />
====EXTRA3 FLAGS====<br />
{|<br />
|exalted || Can only be equipped by players who have remorted at least once (if remort $n >= 2)<br />
|-<br />
|heroic || Can only be equipped by players who have remorted at least five times (if remort $n >= 6)<br />
|-<br />
|epic|| Can only be equipped by players who have remorted at least ten times (if remort $n >= 11)<br />
|-<br />
|perishable|| Object will disappear on logout if the character is not in the object's source area.<br />
|-<br />
|owned|| Object cannot be equipped unless it shares all name keywords with the character.<br />
|}<br />
<br />
* NOTE 1: Objects restricted by number of remorts will also not be saved to unqualified player files when logging out, UNLESS they are somehow also flagged as remortable.<br />
* NOTE 2: Mobiles cannot remort, so exalted, heroic, and epic objects are effectively also antimob.<br />
<br />
===AREA EXFLAGS===<br />
{|<br />
|visdeath || Area is not visible on 'areas' display.<br />
|-<br />
|norecall || No recalling anywhere within this area.<br />
|-<br />
|nosummon || No summoning within this area.<br />
|-<br />
|noweather || Weather is always 0 wind, 0 sky, and the 'weather' command fails with no map displayed.<br />
|}<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2239Mprog Compendium2019-02-24T14:37:47Z<p>Pascal: </p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
It's possible to use 'mob award $i' but ONLY do this in event progs, where $i is the player.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), alignment(#), wealth(#), damtype(a), hitroll(#), damroll(#), magroll(#), saves(#), dicecount(#), dicetype(#), acbash(#), acslash(#), acpierce(#), acexotic(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2232Mprog Compendium2019-02-13T15:40:15Z<p>Pascal: /* MOB COMMANDS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls. IMPORTANT: Even if there is a break inside of a called prog, this only breaks the called prog. The original prog will still continue afterwards. Do not add a 'mob purge self' or any other potentially crashy command in a called prog unless there is an additional break within the main prog right after the called prog.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), align(#), damtype(a), hitroll(#), magroll(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2229Mprog Compendium2019-02-09T19:15:37Z<p>Pascal: /* MOB COMMANDS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
3 - (unused)<br />
4 - plural<br />
5 - spivak<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
-If you want to get REALLY in-depth, you can use both 'and' & 'or' in a prog, too!<br />
<br />
if vnum $i == ####<br />
if affected $i haste<br />
or affected $i slow<br />
and shielded $i zombie<br />
say I can have either haste or slow, but I'll always have zombie!<br />
else<br />
say I have neither haste nor slow, and I totes don't have zombie, either.<br />
endif<br />
endif<br />
<br />
Just be sure to watch the order of your ifchecks, it can make the difference between a working prog and a malfunctioning one!<br />
<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> $i<br />
This command makes the mob using the command the pet of the target. It works almost exactly like the staff command of the same name. Mob petify will not work if the target already has a pet. Mobs can only petify themselves, this command only works with 'self' (variable $i) as the victim.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), align(#), damtype(a), hitroll(#), magroll(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Flags_Compendium&diff=2220Flags Compendium2019-02-07T22:40:09Z<p>Pascal: /* FORM FLAGS */</p>
<hr />
<div>==FLAGS COMPENDIUM==<br />
===ROOM FLAGS===<br />
{|<br />
|dark || Need a light source <br />
|-<br />
|always_night || Room is always night; sun never rises, 'look sky' always shows stars.<br />
|-<br />
|no_mob || Mobs won't wander in here. Mobs on scripts and charmies are unaffected<br />
|-<br />
|indoors || Won't see [[weather]] or [[time|sunrise/set messages]]<br />
|-<br />
|private || Two people at a time<br />
|-<br />
|arena || Players don't leave corpses or lose XP when they die. Players also don't lose XP for fleeing combat.<br />
|-<br />
|safe || No fighting allowed<br />
|-<br />
|solitary || One person at a time<br />
|-<br />
|pet_shop || Can buy pets here. Pet cost is the 'wealth' of the mob, but purchased pets will be flat broke. Builders should reset the pet mobs into next room vnum.<br />
|-<br />
|no_recall || Can't recall from here<br />
|-<br />
|imp_only || MTS only<br />
|-<br />
|gods_only || Staff only<br />
|-<br />
|heroes_only || Also Staff only<br />
|-<br />
|newbies_only || Level 5 or less only<br />
|-<br />
|law || Prevents use of Charm, Tame, and Hypnotize spells (for some reason). Other stock ROM effects have been commented out.<br />
|-<br />
|nowhere || Can't Scan into this room<br />
|-<br />
|wilderness || Was supposed to involve some sort of overworld map? Doesn't do anything now.<br />
|-<br />
|overgrown_1 || Room has +1 level of overgrowth.<br />
|-<br />
|overgrown_2 || Room has +2 levels of overgrowth. This can stack with overgrown_1.<br />
|-<br />
|always_day || Room is always day; sun never sets, 'look sky' shows the sun.<br />
|-<br />
|lit || Room is always lit, don't require a light.<br />
|}<br />
====SECTOR====<br />
{|<br />
!Sector !! Movement Rate !! Properties !! Geomance Element !! Dance Element<br />
|-<br />
|Inside || 4 || Stays lit at night || Pierce || No effect<br />
|-<br />
|City || 4 || Stays lit at night || Bash || No effect<br />
|-<br />
|Field || 4 || || Slash || Pierce<br />
|-<br />
|Forest || 6 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Hills || 6 || || Slash || Pierce<br />
|-<br />
|Mountain || 8 || || Earth || Earth<br />
|-<br />
|Water (swim) || 4 || || Water || Water<br />
|-<br />
|Water (noswim) || 8 || Can't enter without a boat or the Swim affect || Water || Water<br />
|-<br />
|Unused || 1 || || Wind || No effect<br />
|-<br />
|Air || 4 || Can't enter without the Float affect || Wind || Wind<br />
|-<br />
|Desert || 8 || || Earth || Wind<br />
|-<br />
|Rock || 4 || || Earth || Earth<br />
|-<br />
|Road || 4 || || Wind || No effect<br />
|-<br />
|Enter || 4 || || Wind || No effect<br />
|-<br />
|Snow || 8 || || Cold || Cold<br />
|-<br />
|Swamp || 8 || || Water || Earth<br />
|-<br />
|Jungle || 8 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Ruins || 4 || || Bash || No effect <br />
|-<br />
|Mount2 || 16 || || Earth || No effect<br />
|-<br />
|Coastal || 4 || || Earth || Wind<br />
|-<br />
|Developed || 4 || || Bash || No effect <br />
|-<br />
|Void || 4 || || Wind || No effect<br />
|-<br />
|Lava || 8 || || Fire || Fire<br />
|}<br />
<br />
====[[Exits|EXITS]]====<br />
{|<br />
|door || Exit has a door -- Required for most other exit flags<br />
|-<br />
|closed || Door resets to closed<br />
|-<br />
|locked || Door resets to locked<br />
|-<br />
|pickproof || Door can't be picked<br />
|-<br />
|nopass || Door can't be Pass Door'd<br />
|-<br />
|easy || Pick Lock doesn't take many tries<br />
|-<br />
|hard || Pick Lock takes a few tries<br />
|-<br />
|infuriating || Keep pickin'<br />
|-<br />
|noclose || Door can't be closed<br />
|-<br />
|nolock || Door can't be locked<br />
|-<br />
|hidden || Exit can't be seen by normal means<br />
|-<br />
|swim || Only players who can fly or swim, or are on a flying or seaworthy [[vehicle]] can pass.<br />
|-<br />
|fly || Only players who can fly or are on a flying [[vehicle]] can pass.<br />
|}<br />
<br />
===MOB FLAGS===<br />
*Mobs with the None [[damage type]] will randomly have Slash, Pound, or Pierce.<br />
<br />
====FORM FLAGS====<br />
Most of these don't do anything. The ones that have a coded effect are listed below!<br />
{|<br />
|edible || Mob's parts are edible, and the corpse can be butchered into meat.<br />
|-<br />
|poison || Mob's edible parts are poisonous, and meat butchered from the corpse will be poisoned. Bloodsucking will poison the bloodsucker.<br />
|-<br />
|instant_decay || Mob doesn't leave a corpse at all. (Note: This means items on the mob are lost as well.)<br />
|-<br />
|animal || Mob is affected by the Tame spell.<br />
|-<br />
| || Mobs with any of the mammal, bird, reptile, amphibian, fish, or snake form flags can also be Tamed.<br />
|-<br />
|sentient || Mob is affected by the Hypnotize spell and can be haggled with if it's a shopkeeper.<br />
|-<br />
|undead || Mob takes extra non-elemental damage from weapons with disrupting weapon flag.<br />
|-<br />
|cold_blood || Mob has blood that can be bloodsuck'd.<br />
|-<br />
|warm_blood || Mob can be seen in the dark by characters with Infrared and can be bloodsuck'd.<br />
|}<br />
<br />
====PART FLAGS / WEARLOCS====<br />
Mob parts determine what equipment it can wear.<br />
<br />
{| <br />
! Wearloc !! Required Part flag<br />
|-<br />
|take || none<br />
|-<br />
|finger || fingers<br />
|-<br />
|neck || head<br />
|-<br />
|body || guts<br />
|-<br />
|head || head<br />
|-<br />
|legs || legs<br />
|-<br />
|feet || feet<br />
|-<br />
|hands || hands<br />
|-<br />
|arms || hands<br />
|-<br />
|shield || hands<br />
|-<br />
|about || guts<br />
|-<br />
|waist || legs<br />
|-<br />
|wrist || hands<br />
|-<br />
|shoulders || head<br />
|-<br />
|wield || hands<br />
|-<br />
|hold || hands<br />
|-<br />
|nosac || not actually a wearloc<br />
|-<br />
|wearfloat || none<br />
|-<br />
|face || head<br />
|}<br />
<br />
* The Brawling warrior style has special attacks that only execute if the opponent has certain parts; eye, tail, feet, or arms.<br />
* The guts, head, heart, arms, legs, and brains parts can cause dismembered mob organs to be created when the mob dies.<br />
* A mob requires the brains part in order to take any damage from the Brainbuster spell.<br />
* '''A mob without hands cannot hold items, use weapons, or equip shields.'''<br />
* Items which do not have the Take flag can't be sacrificed, so it is redundant to put nosac on these items also.<br />
* Items without a Take flag can't be held by players or mobs at all. Avoid resetting these onto mobs or trying to have mobs oload them.<br />
<br />
====ACT FLAGS====<br />
{|<br />
|sentinel || Mob won't wander between rooms (although it can still move if instructed to by an mprog).<br />
|-<br />
|scavenger || Mob will pick up takeable objects in the room, starting with the most valuable.<br />
|-<br />
|inert || Mob can't be seen in the room (but can still be interacted with).<br />
|-<br />
|omnisight || Mob can see everyone despite invisibility etc but can't necessarily see in the dark.<br />
|-<br />
|aggressive || Doesn't do anything; the code for this function has been commented out.<br />
|-<br />
|stay_area || Mob won't wander outside the area it was reset into.<br />
|-<br />
|wimpy || Mob will try to flee from combat at 20% hp or less.<br />
|-<br />
|pet || Mob is a pet? Probably reserved for pet code. Don't use this.<br />
|-<br />
|train || Players can Train at this mob -- defunct<br />
|-<br />
|practice || Players can Practice at this mob -- defunct<br />
|-<br />
|passive || Mob doesn't fight back with autoattacks, its current health isn't visible when you 'look' at it, nor will Peek work on it.<br />
|-<br />
|hyper || Mob wanders around real fast.<br />
|-<br />
|visdeath || Mob can only be seen by immortals and can't be interacted with by players.<br />
|-<br />
|mage || Mob gets -5 to Saves<br />
|-<br />
|thief || Mob has the Smokescreen skill<br />
|-<br />
|warrior || Mob has the Shield Block skill<br />
|-<br />
|noalign || Mob won't affect player alignment at all when killed.<br />
|-<br />
|nopurge || Mob can't be purged by immortals (the Mob Purge command from a mob can still affect these).<br />
|-<br />
|outdoors || Mob won't wander into Indoor flagged rooms.<br />
|-<br />
|indoors || Mob won't wander outdoors.<br />
|-<br />
|healer || Mob offers hardcoded heal-for-cash services (EG Selan).<br />
|-<br />
|gain || Doesn't do anything -- in stock ROM allows for gaining new skills.<br />
|-<br />
|update_always || Mob does things even when no player in the area.<br />
|-<br />
|changer || Mob is a [[bank]].<br />
|-<br />
|hyper_res || Mob takes 1/4 damage from sources it resists (instead of 2/3) and double damage from sources it's vulnerable to (instead of 3/2).<br />
|}<br />
<br />
Notes on wandering mobs:<br />
* When mobs try to move, they make three attempts. Each attempt, they pick a random exit in the room and then look at it more closely. If they can't move, they try again. If they can move, they do.<br />
* Mobs will not wander through closed doors (even if affected by pass_door) or into no_mob rooms.<br />
* Mobs with the stay_area flag will not wander between areas (which area its' vnum is in doesn't matter).<br />
* Mobs with the Outdoors flag won't wander into Indoors rooms. Mobs with the Indoors flag won't wander into rooms that aren't flagged Indoors.<br />
* Only Flying mobs will move into Air sector rooms. Only mobs with the Swim affect will move into any sort of water room. <br />
** A mob without the Swim affect ''will'' attempt to move into a noswim sector room (and fail to move, unless it has a boat object), but will not even try to get into a swim sector room unless it has the affect (even though it would be allowed to move there if it tried). This doesn't make a lot of sense but that's how it is.<br />
<br />
====ACT2 FLAGS====<br />
{|<br />
|doublexp || Mob gives double XP.<br />
|-<br />
|halfxp || Mob gives half XP.<br />
|-<br />
|noxp || Mob gives no XP.<br />
|-<br />
|noparts || Mob leaves no parts when killed.<br />
|-<br />
|sociable || Mob talks to or slaps people that use socials on it.<br />
|-<br />
|aquatic || Mob won't wander outside water rooms.<br />
|-<br />
|xpandahalf || Mob gives 1.5x XP.<br />
|-<br />
|adept || Mob uses skills at 100% (instead of 75%).<br />
|-<br />
|inept || Mob uses skills at 50% (instead of 75%).<br />
|-<br />
|carryall || Mob has no weight or item# limits.<br />
|-<br />
|priority || Mob will be targetted first by opponents with the AI_1 flag.<br />
|-<br />
|antihyper || Mob wanders especially slowly.<br />
|-<br />
|parsename || Mob will have a unique name as its first name when it resets.<br />
|-<br />
|noattack || Mob can't be attacked by anyone.<br />
|-<br />
|necromancer || Mob offers corpse retrieval for cash services, as Xzar, Caroline, etc.<br />
|-<br />
|raidmob || Mob can be attacked by anyone with no regard to 'kill stealing'.<br />
|-<br />
|carrynone || Mob can't pick up or be given items<br />
|-<br />
|passivelite || Mob won't auto-attack but still has visible health and such<br />
|-<br />
|ally || Is treated as a PC for some attack-safety purposes -- EG Ally mobs won't hit other Ally mobs with area attacks<br />
|-<br />
|shopkeepitems || Shop will not slowly discard items sold to it.<br />
|}<br />
<br />
====OFF FLAGS====<br />
A lot of these are affected by the adept/inept Act flags<br />
{|<br />
|area_attack || Mob hits everything that's fighting it with its normal attacks.<br />
|-<br />
|backstab || Mob is capable of using the Backstab skill, and would if it aggroed, but mobs don't aggro, so it does nothing.<br />
|-<br />
|bash || Mob has a 12.5% chance of using the bash skill, if it's not lagged.<br />
|-<br />
|berserk || Mob has a 12.5% chance of using the berserk skill, if it's not lagged and isn't already berserk.<br />
|-<br />
|disarm || Mob has a 12.5% chance of using the disarm skill, if it's not lagged. The mob needs a [[weapon]].<br />
|-<br />
|dodge || Mob can dodge melee attacks as a player with the dodge skill at 75%.<br />
|-<br />
|fade || Doesn't do anything.<br />
|-<br />
|fast || Mob attacks twice always, doesn't stack with Haste. Mob will ignore Slow if affected. Mob gets +2 DEX when spawned.<br />
|-<br />
|kick || Mob has a 12.5% chance of using the kick skill, if it's not lagged.<br />
|-<br />
|dirt_kick || Mob has a 12.5% chance of using the dirt kick skill, if it's not lagged.<br />
|-<br />
|parry || Mob can parry attacks; works half as often with no [[weapon]].<br />
|-<br />
|rescue || Mob will try to rescue the target of its target, if that target is at 50% hp or less.<br />
|-<br />
|tail || Mob has a 12.5% chance of.. not doing anything (the code for this attack is commented out).<br />
|-<br />
|trip || Mob has a 12.5% chance of using the trip skill, if it's not lagged.<br />
|-<br />
|crush || Mob has a 12.5% chance of using the smash skill, if it's not lagged.<br />
|-<br />
|assist_all || Mob will assist all other '''mobs''' that it sees fighting.<br />
|-<br />
|assist_align || Mob will assist other mobs with a similar alignment, chunked out to good/neutral/evil.<br />
|-<br />
|assist_race || Mob will assist other mobs of the same race.<br />
|-<br />
|assist_players || Mob will assist players as long as the player isn't more than 5 levels above them. This has precedence over the other assist flags.<br />
|-<br />
|assist_leader || If following someone, mob will assist its leader.<br />
|-<br />
|assist_vnum || Mob will assist mobs of the same vnum.<br />
|-<br />
|second_attack || Mob has the 2x-Cut skill.<br />
|-<br />
|third_attack || Mob has the 3x-Cut skill.<br />
|-<br />
|ai_retargeting || Mob will aggro onto players that have recently fled from it, and selectively hit targets with the Priority act flag. If the mob's attacks are ineffective, it will re-target randomly to another member of the same group.<br />
|-<br />
|ai_flees || Mob will flee from sandstorms, flurries, miasmas, wildfires, etc unless it's immune to the appropriate damage type.<br />
|-<br />
|ai_rests || Mob will rest when injured (hp<50%), stand up when it's recovered (hp>75%).<br />
|-<br />
|}<br />
* Only one of the various 12.5% flags can trigger in any given round. A mob will all eight will try to use one (and only one) every single round.<br />
<br />
====BEHAV FLAGS====<br />
{|<br />
|random_innate || Mob randomly has one of the 6 elemental innates. This creates one resistance and one vulnerability.<br />
|-<br />
|rand_phys_resist || Mob randomly resists one of bashing, slashing, or piercing.<br />
|-<br />
|rand_misc_resist || Mob randomly resists one or two non-physical elements.<br />
|}<br />
<br />
====AFFECT FLAGS====<br />
{|<br />
|blind || Character can't see anything! Mobs ignore this flag so their mobprogs work<br />
<br />
|-<br />
|invisible || Character can only be seen and targetted by things with detect_invis.<br />
|-<br />
|detect_evil || Character sees evil objects and characters with a red aura.<br />
|-<br />
|detect_invis || Character can see invisible objects and characters, and knows they're invisible.<br />
|-<br />
|detect_magic || Character sees a blue aura around magical objects.<br />
|-<br />
|detect_hidden || Character can see hidden objects and characters, and knows they're hidden.<br />
|-<br />
|detect_good || Character sees good objects and characters with a gold aura.<br />
|-<br />
|sanctuary || Character is permanently under the effects of Nayru's Love (half damage from everything).<br />
|-<br />
|faerie_fire || Character has a pink aura. Negates invisibility.<br />
|-<br />
|infrared || Character can see warm_blood mobs in the dark.<br />
|-<br />
|curse || Character is flagged as cursed. All skill effectiveness is reduced by 15% while this flag is applied, but the character is immune to the Curse spell.<br />
|-<br />
|solidified || Character is completely frozen!<br />
|-<br />
|poison || Character is flagged as poisoned. This flag has no affect on stats but the character can't be poisoned again. Regeneration is decreased while this flag is applied, however.<br />
|-<br />
|protect_evil || Character takes 2/3 damage from evil foes.<br />
|-<br />
|protect_good || Character takes 2/3 damage from good foes.<br />
|-<br />
|sneak || Character doesn't generate echoes when moving from room to room. Triggers GRALL but not GREET progs.<br />
|-<br />
|hide || Character is hiding. Using any command removes this effect.<br />
|-<br />
|sleep || Character is under the effects of ''permanent'' magical sleep!!<br />
|-<br />
|charm || Character is under the effects of a Charm spell. Don't use.<br />
|-<br />
|flying || Character is flying: reduced MV costs everywhere (by 1 per room), can travel into air sector rooms, and doesn't need a boat to travel into noswim sector rooms. Also immune to Trip and Earthquake.<br />
|-<br />
|pass_door || Character can walk through some closed doors.<br />
|-<br />
|haste || Character is under the effects of Haste: '''always''' gets exactly 1 extra attack in combat, but regenerates at half speed. <br />
|-<br />
|calm || Character is under the effects of the Calm spell. Character can't use berserk.<br />
|-<br />
|plague || Character is flagged as plagued. Regeneration is decreased but the player can't be hit with the Bio 2 spell.<br />
|-<br />
|locusts || Character is a swarm of locusts per the Plague Swarm spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|dark_vision || Character can see anything in any kind of darkness without a light source.<br />
|-<br />
|berserk || Character is under the effects of Berserk! Character can't cast spells, everything the character sees is red, and they get a 50% penalty to all saving throws.<br />
|-<br />
|swim || Character doesn't need a boat to enter noswim sector rooms.<br />
|-<br />
|regeneration || Character regenerates HP twice as fast!<br />
|-<br />
|slow || Character has a chance to simply not attack during combat. 2x-cut and 3x-cut chances are reduced dramatically. Ignored if the mob is flagged off_fast. Character also regenerates at half speed AND spends more MV when traveling.<br />
|-<br />
|scarecrow || Character is affected by the Scarecrow spell -- can't eat, drink, or move, and melee attacks do reduced damage.<br />
|}<br />
<br />
====AFFECT2 FLAGS====<br />
{|<br />
|focus || double mana regeneration<br />
|-<br />
|motivation || slight movement regeneration<br />
|-<br />
|theatrical || takes damage when receiving an affect<br />
|-<br />
|frenzy || grants extra attack<br />
|-<br />
|vampirism || ??<br />
|-<br />
|paralysis|| ??<br />
|-<br />
|fast|| no command lag when moving rooms (like vehicle fast)<br />
|}<br />
<br />
====SHIELD FLAGS====<br />
{|<br />
|charge || Character does 1.5x damage with all applicable spells. DOES NOT DISSIPATE UNLESS IT IS APPLIED BY THE CHARGE SPELL.<br />
|-<br />
|sabotaged || Character takes damage when using skills or spells.<br />
|-<br />
|hallucinating || Character is under the effects of the Mushroomize spell; all MUD output turns wacky.<br />
|-<br />
|terrified || Character may cower helplessly in combat, with a greater chance is the foe's level is higher than the character's. Also makes the character try to flee.<br />
|-<br />
|haunted || Character is tormented by minighosts.<br />
|-<br />
|confused || Character hits itself sometimes in combat.<br />
|-<br />
|stat enhancement || Character is under the effects of one of Sage Aura, Brilliance, Limber, Valor, or Vigor/Warcry and can't be affected by another one.<br />
|-<br />
|ice shield || Returns 20 to 30% of melee damage as bash-type damage<br />
|-<br />
|thorn shield || Returns 20 to 30% of melee damage as pierce-type damage<br />
|-<br />
|crystal shield || Returns 20 to 30% of melee damage as slash-type damage<br />
|-<br />
|osmosis || Character loses MP steadily. Also decreases MP regeneration.<br />
|-<br />
|volta || Character does not auto-attack but has double normal dodge chances.<br />
|-<br />
|manashield || Character has Mana Shield permanently up. It will give the 'your shield broke' message with every attack if they're at 0MP but they'll still take full damage.<br />
|-<br />
|kamikaze || Character is going to Detonate. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|zeal || Character fails all saving throws but receives a bonus to damage for each bad affect<br />
|-<br />
|bleeding || Character loses HP steadily. Some types of bleeding make you bleed worse than others!<br />
|-<br />
|undead || Character is a zombie with a relentless hunger for delicious brains. All text is dark gray, healing spells do damage instead of healing, and the poor bastard doesn't necessarily die when they drop below 0hp! This is distinct from the undead form flag.<br />
|-<br />
|oozaru form || Character is an oozaru and can't cast spells.<br />
|-<br />
|double image || Character has a double image. It will take one attack and then vanish.<br />
|-<br />
|ink || Character has been inked. Display is all goofed up with large black splotches.<br />
|-<br />
|seraph form || Character has seraph form and can't cast spells.<br />
|-<br />
|reflect || Spells targetted at the character bounce back the wrong way<br />
|-<br />
|surefire casting || Character has surecasting on.<br />
|-<br />
|jinx || Character has a 33% chance of dropping any [[weapon]] they're wielding in any combat round.<br />
|-<br />
|leechseed || Character is under the effects of the Leech Seed spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bees || Character is covered in bees which deal periodic damage.<br />
|-<br />
|choke || Character is affected by Choke and casts spells at 3/4 the normal strength.<br />
|-<br />
|endure || Character cannot be reduced below 1hp.<br />
|-<br />
|sheltered || Character is being sheltered by a friendly Templar. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bide || Character is using the skill Bide. *Cannot be set on a mob's template or applied by an item.<br />
|}<br />
<br />
Some of these affects can't be applied to a mob's template, only by spells; homing attack, stat enhancement, extension, kamikaze, short term combat effect, oozaru form, double image, seraph form, Jumi empathy, surefire casting, and leechseed.<br />
<br />
===OBJ FLAGS===<br />
For more details on object types see [[Flags Compendium/Obj Types]]<br />
<br />
{|<br />
|[[light]] || Light sources, go in a special 'light' slot when equipped no matter what wear flags you use<br />
|-<br />
|[[scroll]] || Can be recited or read to cast 1-4 spells on a target. Works from base inventory, consumed when used, uses [[Artifice]] skill.<br />
|-<br />
|[[wand]] || Can be zapped or used to cast 1 spell a set number of times on a target. Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[staff]] || Can be brandished or used to cast 1 spell a set number of times on all targets in a room! Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[weapon]] || Changes wearer's melee autoattack damage to the type and amount specified in the object. Must be in the Wield slot to work.<br />
|-<br />
|[[treasure]] || No inherent properties, reserved for salable loot.<br />
|-<br />
|armor || Modifies wearer's armor values. Can be equipped anywhere.<br />
|-<br />
|[[potion]] || Can be quaffed or drunk to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|-<br />
|[[furniture]] || Various flags allow characters to sit, rest, stand, or sleep on, in, or at these objects. Recovery rates can be modified as well.<br />
|-<br />
|[[trash]] || No inherent properties, reserved for nonsalable loot.<br />
|-<br />
|[[container]] || Object that holds other objects. Can be closable/lockable like a door.<br />
|-<br />
|[[drinkcontainer]] || Holds a set quantity of a certain [[liquid]]. Liquids can be replaced with different liquids. Disappears when empty unless NOEXPLODE is set.<br />
|-<br />
|[[key]] || Object vanishes on logout. Has no other properties.<br />
|- <br />
|[[food]] || Can be eaten for food/full value and cast 1 spell on the eater.<br />
|- <br />
|[[money]] || Is abstracted into current wealth when picked up by a player. Dropped wealth turns into a money object. The Priest class can sacrifice money to recover mana for 1 MP per 50 silver.<br />
|- <br />
|boat || Can be equipped or in base inventory for players to move in water rooms. Defunct.<br />
|- <br />
|npccorpse || NPC [[Corpse]]. Reserved.<br />
|- <br />
|[[fountain]] || Like a drinkcontainer but the [[liquid]] inside can't be poisoned. Drinkcontainers can also be 'fill'ed from it.<br />
|- <br />
|[[pill]] || Can be eaten to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|- <br />
|protect || Uncoded junk. Don't use.<br />
|- <br />
|map || Uncoded junk. Don't use.<br />
|- <br />
|[[portal]] || Objects that can be 'entered' to take the character to a set room. Can be closable/lockable like a door.<br />
|- <br />
|warpstone || Used to be necessary for the Nexus spell.<br />
|- <br />
|roomkey || Uncoded junk. Don't use.<br />
|- <br />
|gem || Uncoded junk. Don't use.<br />
|- <br />
|[[jewelry]] || No inherent properties. Used for equippables that aren't armor.<br />
|- <br />
|[[Event Item|event]] || An object with both charges and cooldown capability, which executes an mprog when 'zap'ped or 'use'd. Uses [[Artifice]] skill.<br />
|- <br />
|slotmachine || <s>Type "Game slots" at a slot machine to spin the wheel. Slot machines can have their cost and jackpot size specified in the object template.</s> Just kidding! Disabled.<br />
|- <br />
|gun || Uncoded junk. Don't use.<br />
|- <br />
|ammo || Uncoded junk. Don't use.<br />
|- <br />
|[[vehicle]] || Vehicles allow players to consume less movement points as they travel, move faster, and/or travel to rooms they can't enter on foot.<br />
|- <br />
|exit || Uncoded junk. Don't use. Not the same as a real [[exit]].<br />
|- <br />
|[[rod]] || Can be zapped or used to cast 1 spell on a target with a set delay between uses. Must be equipped, any slot is OK. Uses [[Artifice]] skill.<br />
|}<br />
====EXTRA FLAGS====<br />
{|<br />
|glow || Item can be seen in the dark, shows (glowing) before its short desc<br />
|-<br />
|hum || Item shows (Humming) before its short desc<br />
|-<br />
|norecharge || Wand, staff, rod, or event can't be recharged with the Recharge spell.<br />
|-<br />
|autoconsume || Item is automatically used as soon as it's picked up off the ground. Works with [[potions]], [[pills]], and [[artifice]] items.<br />
|-<br />
|evil || Item has a red aura if you can detect evil, can be removed with Bless.<br />
|-<br />
|invis || Item can only be seen if you have detect invis, and shows (Invis) if you can<br />
|-<br />
|magic || Item shows as magic if you can detect magic<br />
|-<br />
|nodrop || Item can't be dropped, can be removed with Bless<br />
|-<br />
|bless || Item has a blue aura if you can detect good, can't be poisoned, and is a little easier to enchant. Is removed by Curse.<br />
|-<br />
|noremove || Item can't be removed. This flag is removed by uncursing<br />
|-<br />
|inventory || Item is part of a shopkeeper's inventory and will be sold with infinite quantity left. Also evaporates when the holder dies, like rotdeath.<br />
|-<br />
|nopurge || Item can't be purged. Use sparingly!<br />
|-<br />
|rotdeath || Item poofs when whoever is holding it dies. If a mob dies with one of these, it will vanish.<br />
|-<br />
|visdeath || Item can only be seen by immortals<br />
|-<br />
|uncounted || Item doesn't count against the holder's carry number or weight capacities.<br />
|-<br />
|nonmetal || Item is unaffected by Heat Metal<br />
|-<br />
|meltdrop || Item poofs when dropped or stolen. If a mob dies with one of these, it will appear in the room. <br />
|-<br />
|decaying || Item loses 1 condition per minute, then disintegrates.<br />
|-<br />
|sellextract || Item poofs when sold to shopkeeper -- doesn't show up in their inventory<br />
|-<br />
|nodestroy || (AKA burn_proof in the code for some reason) Item can't be poisoned, and can't be destroyed by various item-destroying affects (which I think are disabled)<br />
|-<br />
|nouncurse || Item can't be uncursed. (nodrop, noremove flags)<br />
|-<br />
|runic || Unused<br />
|-<br />
|adhesive || Item stays with a player, not on their corpse<br />
|-<br />
|nochk || [[Wand]], [[Scroll]], [[Staff]], [[Rod]], and [[Event Item|Event]] items with this flag won't check a character's [[artifice]] skill when used, but just always work<br />
|-<br />
|noremort || Item can't be carried through a remort<br />
|-<br />
|inert || Item doesn't appear in rooms its in<br />
|-<br />
|noexplode || Wand and staff type item won't disintegrate when their charges are used up. Drinkcontainers won't poof when empty.<br />
|}<br />
<br />
====EXTRA2 FLAGS====<br />
{|<br />
|antihuman || Can't be equipped by Human race<br />
|-<br />
|antimoogle || Can't be equipped by Moogle race<br />
|-<br />
|antisaiyan || Can't be equipped by Saiyan race<br />
|-<br />
|antiesper || Can't be equipped by Esper race<br />
|-<br />
|antihylian || Can't be equipped by Hylian race<br />
|-<br />
|antikokiri || Can't be equipped by Kokiri race<br />
|-<br />
|antigiganto || Can't be equipped by Giganto race<br />
|-<br />
|antimatango || Can't be equipped by Matango race<br />
|-<br />
|antireploid || Can't be equipped by Reploid race<br />
|-<br />
|antikoopa || Can't be equipped by Koopa race<br />
|-<br />
|antipmpkn || Can't be equipped by Pumpkinhead race<br />
|-<br />
|antiknight || Can't be equipped by Knight class<br />
|-<br />
|antiwarrior || Can't be equipped by Warrior class<br />
|-<br />
|antithief || Can't be equipped by Thief class<br />
|-<br />
|antiwizard || Can't be equipped by Wizard class<br />
|-<br />
|antipriest || Can't be equipped by Priest class<br />
|-<br />
|antigeomancer || Can't be equipped by Geomancer class<br />
|-<br />
|antisummoner || Can't be equipped by Summoner class<br />
|-<br />
|antifemale || Can't be equipped by female characters<br />
|-<br />
|antimale || Can't be equipped by male characters<br />
|-<br />
|antineuter || Can't be equipped by sexless characters<br />
|-<br />
|cursed || Item becomes noremove when equipped<br />
|-<br />
|unique || Characters can't pick up one of these if they already have one.<br />
|-<br />
|remortable || Item was carried through a remort and won't vanish on logout if it's out of the player's level range.<br />
|-<br />
|antinu || Can't be equipped by Nu race<br />
|-<br />
|antikirby || Can't be equipped by Kirby race<br />
|-<br />
|antilobsterman || Can't be equipped by Lobster race<br />
|-<br />
|antiranboob || Can't be equipped by Ranboob race<br />
|-<br />
|antijumi || Can't be equipped by Jumi race<br />
|-<br />
|antidancer || Can't be equipped by Dancer class<br />
|-<br />
|antimob || Can't be equipped by mobs<br />
|}<br />
<br />
* NOTE: Old classes are affected by antiwizard, etc, just as new ones are.<br />
<br />
====EXTRA3 FLAGS====<br />
{|<br />
|exalted || Can only be equipped by players who have remorted at least once (if remort $n >= 2)<br />
|-<br />
|heroic || Can only be equipped by players who have remorted at least five times (if remort $n >= 6)<br />
|-<br />
|epic|| Can only be equipped by players who have remorted at least ten times (if remort $n >= 11)<br />
|-<br />
|perishable|| Object will disappear on logout if the character is not in the object's source area.<br />
|-<br />
|owned|| Object cannot be equipped unless it shares all name keywords with the character.<br />
|}<br />
<br />
* NOTE 1: Objects restricted by number of remorts will also not be saved to unqualified player files when logging out, UNLESS they are somehow also flagged as remortable.<br />
* NOTE 2: Mobiles cannot remort, so exalted, heroic, and epic objects are effectively also antimob.<br />
<br />
===AREA EXFLAGS===<br />
{|<br />
|visdeath || Area is not visible on 'areas' display.<br />
|-<br />
|norecall || No recalling anywhere within this area.<br />
|-<br />
|nosummon || No summoning within this area.<br />
|-<br />
|noweather || Weather is always 0 wind, 0 sky, and the 'weather' command fails with no map displayed.<br />
|}<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Flags_Compendium&diff=2219Flags Compendium2019-02-07T03:14:04Z<p>Pascal: /* FORM FLAGS */</p>
<hr />
<div>==FLAGS COMPENDIUM==<br />
===ROOM FLAGS===<br />
{|<br />
|dark || Need a light source <br />
|-<br />
|always_night || Room is always night; sun never rises, 'look sky' always shows stars.<br />
|-<br />
|no_mob || Mobs won't wander in here. Mobs on scripts and charmies are unaffected<br />
|-<br />
|indoors || Won't see [[weather]] or [[time|sunrise/set messages]]<br />
|-<br />
|private || Two people at a time<br />
|-<br />
|arena || Players don't leave corpses or lose XP when they die. Players also don't lose XP for fleeing combat.<br />
|-<br />
|safe || No fighting allowed<br />
|-<br />
|solitary || One person at a time<br />
|-<br />
|pet_shop || Can buy pets here. Pet cost is the 'wealth' of the mob, but purchased pets will be flat broke. Builders should reset the pet mobs into next room vnum.<br />
|-<br />
|no_recall || Can't recall from here<br />
|-<br />
|imp_only || MTS only<br />
|-<br />
|gods_only || Staff only<br />
|-<br />
|heroes_only || Also Staff only<br />
|-<br />
|newbies_only || Level 5 or less only<br />
|-<br />
|law || Prevents use of Charm, Tame, and Hypnotize spells (for some reason). Other stock ROM effects have been commented out.<br />
|-<br />
|nowhere || Can't Scan into this room<br />
|-<br />
|wilderness || Was supposed to involve some sort of overworld map? Doesn't do anything now.<br />
|-<br />
|overgrown_1 || Room has +1 level of overgrowth.<br />
|-<br />
|overgrown_2 || Room has +2 levels of overgrowth. This can stack with overgrown_1.<br />
|-<br />
|always_day || Room is always day; sun never sets, 'look sky' shows the sun.<br />
|-<br />
|lit || Room is always lit, don't require a light.<br />
|}<br />
====SECTOR====<br />
{|<br />
!Sector !! Movement Rate !! Properties !! Geomance Element !! Dance Element<br />
|-<br />
|Inside || 4 || Stays lit at night || Pierce || No effect<br />
|-<br />
|City || 4 || Stays lit at night || Bash || No effect<br />
|-<br />
|Field || 4 || || Slash || Pierce<br />
|-<br />
|Forest || 6 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Hills || 6 || || Slash || Pierce<br />
|-<br />
|Mountain || 8 || || Earth || Earth<br />
|-<br />
|Water (swim) || 4 || || Water || Water<br />
|-<br />
|Water (noswim) || 8 || Can't enter without a boat or the Swim affect || Water || Water<br />
|-<br />
|Unused || 1 || || Wind || No effect<br />
|-<br />
|Air || 4 || Can't enter without the Float affect || Wind || Wind<br />
|-<br />
|Desert || 8 || || Earth || Wind<br />
|-<br />
|Rock || 4 || || Earth || Earth<br />
|-<br />
|Road || 4 || || Wind || No effect<br />
|-<br />
|Enter || 4 || || Wind || No effect<br />
|-<br />
|Snow || 8 || || Cold || Cold<br />
|-<br />
|Swamp || 8 || || Water || Earth<br />
|-<br />
|Jungle || 8 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Ruins || 4 || || Bash || No effect <br />
|-<br />
|Mount2 || 16 || || Earth || No effect<br />
|-<br />
|Coastal || 4 || || Earth || Wind<br />
|-<br />
|Developed || 4 || || Bash || No effect <br />
|-<br />
|Void || 4 || || Wind || No effect<br />
|-<br />
|Lava || 8 || || Fire || Fire<br />
|}<br />
<br />
====[[Exits|EXITS]]====<br />
{|<br />
|door || Exit has a door -- Required for most other exit flags<br />
|-<br />
|closed || Door resets to closed<br />
|-<br />
|locked || Door resets to locked<br />
|-<br />
|pickproof || Door can't be picked<br />
|-<br />
|nopass || Door can't be Pass Door'd<br />
|-<br />
|easy || Pick Lock doesn't take many tries<br />
|-<br />
|hard || Pick Lock takes a few tries<br />
|-<br />
|infuriating || Keep pickin'<br />
|-<br />
|noclose || Door can't be closed<br />
|-<br />
|nolock || Door can't be locked<br />
|-<br />
|hidden || Exit can't be seen by normal means<br />
|-<br />
|swim || Only players who can fly or swim, or are on a flying or seaworthy [[vehicle]] can pass.<br />
|-<br />
|fly || Only players who can fly or are on a flying [[vehicle]] can pass.<br />
|}<br />
<br />
===MOB FLAGS===<br />
*Mobs with the None [[damage type]] will randomly have Slash, Pound, or Pierce.<br />
<br />
====FORM FLAGS====<br />
Most of these don't do anything. The ones that have a coded effect are listed below!<br />
{|<br />
|edible || Mob's parts are edible, and the corpse can be butchered into meat.<br />
|-<br />
|poison || Mob's edible parts are poisonous, and meat butchered from the corpse will be poisoned. Bloodsucking will poison the bloodsucker.<br />
|-<br />
|instant_decay || Mob doesn't leave a corpse at all.<br />
|-<br />
|animal || Mob is affected by the Tame spell<br />
|-<br />
| || Mobs with any of the mammal, bird, reptile, amphibian, fish, or snake form flags can also be Tamed.<br />
|-<br />
|sentient || Mob is affected by the Hypnotize spell and can be haggled with if it's a shopkeeper.<br />
|-<br />
|undead || Mob takes extra non-elemental damage from weapons with disrupting weapon flag.<br />
|-<br />
|cold_blood || Mob has blood that can be bloodsuck'd.<br />
|-<br />
|warm_blood || Mob can be seen in the dark by characters with Infrared and can be bloodsuck'd.<br />
|}<br />
<br />
====PART FLAGS / WEARLOCS====<br />
Mob parts determine what equipment it can wear.<br />
<br />
{| <br />
! Wearloc !! Required Part flag<br />
|-<br />
|take || none<br />
|-<br />
|finger || fingers<br />
|-<br />
|neck || head<br />
|-<br />
|body || guts<br />
|-<br />
|head || head<br />
|-<br />
|legs || legs<br />
|-<br />
|feet || feet<br />
|-<br />
|hands || hands<br />
|-<br />
|arms || hands<br />
|-<br />
|shield || hands<br />
|-<br />
|about || guts<br />
|-<br />
|waist || legs<br />
|-<br />
|wrist || hands<br />
|-<br />
|shoulders || head<br />
|-<br />
|wield || hands<br />
|-<br />
|hold || hands<br />
|-<br />
|nosac || not actually a wearloc<br />
|-<br />
|wearfloat || none<br />
|-<br />
|face || head<br />
|}<br />
<br />
* The Brawling warrior style has special attacks that only execute if the opponent has certain parts; eye, tail, feet, or arms.<br />
* The guts, head, heart, arms, legs, and brains parts can cause dismembered mob organs to be created when the mob dies.<br />
* A mob requires the brains part in order to take any damage from the Brainbuster spell.<br />
* '''A mob without hands cannot hold items, use weapons, or equip shields.'''<br />
* Items which do not have the Take flag can't be sacrificed, so it is redundant to put nosac on these items also.<br />
* Items without a Take flag can't be held by players or mobs at all. Avoid resetting these onto mobs or trying to have mobs oload them.<br />
<br />
====ACT FLAGS====<br />
{|<br />
|sentinel || Mob won't wander between rooms (although it can still move if instructed to by an mprog).<br />
|-<br />
|scavenger || Mob will pick up takeable objects in the room, starting with the most valuable.<br />
|-<br />
|inert || Mob can't be seen in the room (but can still be interacted with).<br />
|-<br />
|omnisight || Mob can see everyone despite invisibility etc but can't necessarily see in the dark.<br />
|-<br />
|aggressive || Doesn't do anything; the code for this function has been commented out.<br />
|-<br />
|stay_area || Mob won't wander outside the area it was reset into.<br />
|-<br />
|wimpy || Mob will try to flee from combat at 20% hp or less.<br />
|-<br />
|pet || Mob is a pet? Probably reserved for pet code. Don't use this.<br />
|-<br />
|train || Players can Train at this mob -- defunct<br />
|-<br />
|practice || Players can Practice at this mob -- defunct<br />
|-<br />
|passive || Mob doesn't fight back with autoattacks, its current health isn't visible when you 'look' at it, nor will Peek work on it.<br />
|-<br />
|hyper || Mob wanders around real fast.<br />
|-<br />
|visdeath || Mob can only be seen by immortals and can't be interacted with by players.<br />
|-<br />
|mage || Mob gets -5 to Saves<br />
|-<br />
|thief || Mob has the Smokescreen skill<br />
|-<br />
|warrior || Mob has the Shield Block skill<br />
|-<br />
|noalign || Mob won't affect player alignment at all when killed.<br />
|-<br />
|nopurge || Mob can't be purged by immortals (the Mob Purge command from a mob can still affect these).<br />
|-<br />
|outdoors || Mob won't wander into Indoor flagged rooms.<br />
|-<br />
|indoors || Mob won't wander outdoors.<br />
|-<br />
|healer || Mob offers hardcoded heal-for-cash services (EG Selan).<br />
|-<br />
|gain || Doesn't do anything -- in stock ROM allows for gaining new skills.<br />
|-<br />
|update_always || Mob does things even when no player in the area.<br />
|-<br />
|changer || Mob is a [[bank]].<br />
|-<br />
|hyper_res || Mob takes 1/4 damage from sources it resists (instead of 2/3) and double damage from sources it's vulnerable to (instead of 3/2).<br />
|}<br />
<br />
Notes on wandering mobs:<br />
* When mobs try to move, they make three attempts. Each attempt, they pick a random exit in the room and then look at it more closely. If they can't move, they try again. If they can move, they do.<br />
* Mobs will not wander through closed doors (even if affected by pass_door) or into no_mob rooms.<br />
* Mobs with the stay_area flag will not wander between areas (which area its' vnum is in doesn't matter).<br />
* Mobs with the Outdoors flag won't wander into Indoors rooms. Mobs with the Indoors flag won't wander into rooms that aren't flagged Indoors.<br />
* Only Flying mobs will move into Air sector rooms. Only mobs with the Swim affect will move into any sort of water room. <br />
** A mob without the Swim affect ''will'' attempt to move into a noswim sector room (and fail to move, unless it has a boat object), but will not even try to get into a swim sector room unless it has the affect (even though it would be allowed to move there if it tried). This doesn't make a lot of sense but that's how it is.<br />
<br />
====ACT2 FLAGS====<br />
{|<br />
|doublexp || Mob gives double XP.<br />
|-<br />
|halfxp || Mob gives half XP.<br />
|-<br />
|noxp || Mob gives no XP.<br />
|-<br />
|noparts || Mob leaves no parts when killed.<br />
|-<br />
|sociable || Mob talks to or slaps people that use socials on it.<br />
|-<br />
|aquatic || Mob won't wander outside water rooms.<br />
|-<br />
|xpandahalf || Mob gives 1.5x XP.<br />
|-<br />
|adept || Mob uses skills at 100% (instead of 75%).<br />
|-<br />
|inept || Mob uses skills at 50% (instead of 75%).<br />
|-<br />
|carryall || Mob has no weight or item# limits.<br />
|-<br />
|priority || Mob will be targetted first by opponents with the AI_1 flag.<br />
|-<br />
|antihyper || Mob wanders especially slowly.<br />
|-<br />
|parsename || Mob will have a unique name as its first name when it resets.<br />
|-<br />
|noattack || Mob can't be attacked by anyone.<br />
|-<br />
|necromancer || Mob offers corpse retrieval for cash services, as Xzar, Caroline, etc.<br />
|-<br />
|raidmob || Mob can be attacked by anyone with no regard to 'kill stealing'.<br />
|-<br />
|carrynone || Mob can't pick up or be given items<br />
|-<br />
|passivelite || Mob won't auto-attack but still has visible health and such<br />
|-<br />
|ally || Is treated as a PC for some attack-safety purposes -- EG Ally mobs won't hit other Ally mobs with area attacks<br />
|-<br />
|shopkeepitems || Shop will not slowly discard items sold to it.<br />
|}<br />
<br />
====OFF FLAGS====<br />
A lot of these are affected by the adept/inept Act flags<br />
{|<br />
|area_attack || Mob hits everything that's fighting it with its normal attacks.<br />
|-<br />
|backstab || Mob is capable of using the Backstab skill, and would if it aggroed, but mobs don't aggro, so it does nothing.<br />
|-<br />
|bash || Mob has a 12.5% chance of using the bash skill, if it's not lagged.<br />
|-<br />
|berserk || Mob has a 12.5% chance of using the berserk skill, if it's not lagged and isn't already berserk.<br />
|-<br />
|disarm || Mob has a 12.5% chance of using the disarm skill, if it's not lagged. The mob needs a [[weapon]].<br />
|-<br />
|dodge || Mob can dodge melee attacks as a player with the dodge skill at 75%.<br />
|-<br />
|fade || Doesn't do anything.<br />
|-<br />
|fast || Mob attacks twice always, doesn't stack with Haste. Mob will ignore Slow if affected. Mob gets +2 DEX when spawned.<br />
|-<br />
|kick || Mob has a 12.5% chance of using the kick skill, if it's not lagged.<br />
|-<br />
|dirt_kick || Mob has a 12.5% chance of using the dirt kick skill, if it's not lagged.<br />
|-<br />
|parry || Mob can parry attacks; works half as often with no [[weapon]].<br />
|-<br />
|rescue || Mob will try to rescue the target of its target, if that target is at 50% hp or less.<br />
|-<br />
|tail || Mob has a 12.5% chance of.. not doing anything (the code for this attack is commented out).<br />
|-<br />
|trip || Mob has a 12.5% chance of using the trip skill, if it's not lagged.<br />
|-<br />
|crush || Mob has a 12.5% chance of using the smash skill, if it's not lagged.<br />
|-<br />
|assist_all || Mob will assist all other '''mobs''' that it sees fighting.<br />
|-<br />
|assist_align || Mob will assist other mobs with a similar alignment, chunked out to good/neutral/evil.<br />
|-<br />
|assist_race || Mob will assist other mobs of the same race.<br />
|-<br />
|assist_players || Mob will assist players as long as the player isn't more than 5 levels above them. This has precedence over the other assist flags.<br />
|-<br />
|assist_leader || If following someone, mob will assist its leader.<br />
|-<br />
|assist_vnum || Mob will assist mobs of the same vnum.<br />
|-<br />
|second_attack || Mob has the 2x-Cut skill.<br />
|-<br />
|third_attack || Mob has the 3x-Cut skill.<br />
|-<br />
|ai_retargeting || Mob will aggro onto players that have recently fled from it, and selectively hit targets with the Priority act flag. If the mob's attacks are ineffective, it will re-target randomly to another member of the same group.<br />
|-<br />
|ai_flees || Mob will flee from sandstorms, flurries, miasmas, wildfires, etc unless it's immune to the appropriate damage type.<br />
|-<br />
|ai_rests || Mob will rest when injured (hp<50%), stand up when it's recovered (hp>75%).<br />
|-<br />
|}<br />
* Only one of the various 12.5% flags can trigger in any given round. A mob will all eight will try to use one (and only one) every single round.<br />
<br />
====BEHAV FLAGS====<br />
{|<br />
|random_innate || Mob randomly has one of the 6 elemental innates. This creates one resistance and one vulnerability.<br />
|-<br />
|rand_phys_resist || Mob randomly resists one of bashing, slashing, or piercing.<br />
|-<br />
|rand_misc_resist || Mob randomly resists one or two non-physical elements.<br />
|}<br />
<br />
====AFFECT FLAGS====<br />
{|<br />
|blind || Character can't see anything! Mobs ignore this flag so their mobprogs work<br />
<br />
|-<br />
|invisible || Character can only be seen and targetted by things with detect_invis.<br />
|-<br />
|detect_evil || Character sees evil objects and characters with a red aura.<br />
|-<br />
|detect_invis || Character can see invisible objects and characters, and knows they're invisible.<br />
|-<br />
|detect_magic || Character sees a blue aura around magical objects.<br />
|-<br />
|detect_hidden || Character can see hidden objects and characters, and knows they're hidden.<br />
|-<br />
|detect_good || Character sees good objects and characters with a gold aura.<br />
|-<br />
|sanctuary || Character is permanently under the effects of Nayru's Love (half damage from everything).<br />
|-<br />
|faerie_fire || Character has a pink aura. Negates invisibility.<br />
|-<br />
|infrared || Character can see warm_blood mobs in the dark.<br />
|-<br />
|curse || Character is flagged as cursed. All skill effectiveness is reduced by 15% while this flag is applied, but the character is immune to the Curse spell.<br />
|-<br />
|solidified || Character is completely frozen!<br />
|-<br />
|poison || Character is flagged as poisoned. This flag has no affect on stats but the character can't be poisoned again. Regeneration is decreased while this flag is applied, however.<br />
|-<br />
|protect_evil || Character takes 2/3 damage from evil foes.<br />
|-<br />
|protect_good || Character takes 2/3 damage from good foes.<br />
|-<br />
|sneak || Character doesn't generate echoes when moving from room to room. Triggers GRALL but not GREET progs.<br />
|-<br />
|hide || Character is hiding. Using any command removes this effect.<br />
|-<br />
|sleep || Character is under the effects of ''permanent'' magical sleep!!<br />
|-<br />
|charm || Character is under the effects of a Charm spell. Don't use.<br />
|-<br />
|flying || Character is flying: reduced MV costs everywhere (by 1 per room), can travel into air sector rooms, and doesn't need a boat to travel into noswim sector rooms. Also immune to Trip and Earthquake.<br />
|-<br />
|pass_door || Character can walk through some closed doors.<br />
|-<br />
|haste || Character is under the effects of Haste: '''always''' gets exactly 1 extra attack in combat, but regenerates at half speed. <br />
|-<br />
|calm || Character is under the effects of the Calm spell. Character can't use berserk.<br />
|-<br />
|plague || Character is flagged as plagued. Regeneration is decreased but the player can't be hit with the Bio 2 spell.<br />
|-<br />
|locusts || Character is a swarm of locusts per the Plague Swarm spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|dark_vision || Character can see anything in any kind of darkness without a light source.<br />
|-<br />
|berserk || Character is under the effects of Berserk! Character can't cast spells, everything the character sees is red, and they get a 50% penalty to all saving throws.<br />
|-<br />
|swim || Character doesn't need a boat to enter noswim sector rooms.<br />
|-<br />
|regeneration || Character regenerates HP twice as fast!<br />
|-<br />
|slow || Character has a chance to simply not attack during combat. 2x-cut and 3x-cut chances are reduced dramatically. Ignored if the mob is flagged off_fast. Character also regenerates at half speed AND spends more MV when traveling.<br />
|-<br />
|scarecrow || Character is affected by the Scarecrow spell -- can't eat, drink, or move, and melee attacks do reduced damage.<br />
|}<br />
<br />
====AFFECT2 FLAGS====<br />
{|<br />
|focus || double mana regeneration<br />
|-<br />
|motivation || slight movement regeneration<br />
|-<br />
|theatrical || takes damage when receiving an affect<br />
|-<br />
|frenzy || grants extra attack<br />
|-<br />
|vampirism || ??<br />
|-<br />
|paralysis|| ??<br />
|-<br />
|fast|| no command lag when moving rooms (like vehicle fast)<br />
|}<br />
<br />
====SHIELD FLAGS====<br />
{|<br />
|charge || Character does 1.5x damage with all applicable spells. DOES NOT DISSIPATE UNLESS IT IS APPLIED BY THE CHARGE SPELL.<br />
|-<br />
|sabotaged || Character takes damage when using skills or spells.<br />
|-<br />
|hallucinating || Character is under the effects of the Mushroomize spell; all MUD output turns wacky.<br />
|-<br />
|terrified || Character may cower helplessly in combat, with a greater chance is the foe's level is higher than the character's. Also makes the character try to flee.<br />
|-<br />
|haunted || Character is tormented by minighosts.<br />
|-<br />
|confused || Character hits itself sometimes in combat.<br />
|-<br />
|stat enhancement || Character is under the effects of one of Sage Aura, Brilliance, Limber, Valor, or Vigor/Warcry and can't be affected by another one.<br />
|-<br />
|ice shield || Returns 20 to 30% of melee damage as bash-type damage<br />
|-<br />
|thorn shield || Returns 20 to 30% of melee damage as pierce-type damage<br />
|-<br />
|crystal shield || Returns 20 to 30% of melee damage as slash-type damage<br />
|-<br />
|osmosis || Character loses MP steadily. Also decreases MP regeneration.<br />
|-<br />
|volta || Character does not auto-attack but has double normal dodge chances.<br />
|-<br />
|manashield || Character has Mana Shield permanently up. It will give the 'your shield broke' message with every attack if they're at 0MP but they'll still take full damage.<br />
|-<br />
|kamikaze || Character is going to Detonate. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|zeal || Character fails all saving throws but receives a bonus to damage for each bad affect<br />
|-<br />
|bleeding || Character loses HP steadily. Some types of bleeding make you bleed worse than others!<br />
|-<br />
|undead || Character is a zombie with a relentless hunger for delicious brains. All text is dark gray, healing spells do damage instead of healing, and the poor bastard doesn't necessarily die when they drop below 0hp! This is distinct from the undead form flag.<br />
|-<br />
|oozaru form || Character is an oozaru and can't cast spells.<br />
|-<br />
|double image || Character has a double image. It will take one attack and then vanish.<br />
|-<br />
|ink || Character has been inked. Display is all goofed up with large black splotches.<br />
|-<br />
|seraph form || Character has seraph form and can't cast spells.<br />
|-<br />
|reflect || Spells targetted at the character bounce back the wrong way<br />
|-<br />
|surefire casting || Character has surecasting on.<br />
|-<br />
|jinx || Character has a 33% chance of dropping any [[weapon]] they're wielding in any combat round.<br />
|-<br />
|leechseed || Character is under the effects of the Leech Seed spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bees || Character is covered in bees which deal periodic damage.<br />
|-<br />
|choke || Character is affected by Choke and casts spells at 3/4 the normal strength.<br />
|-<br />
|endure || Character cannot be reduced below 1hp.<br />
|-<br />
|sheltered || Character is being sheltered by a friendly Templar. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bide || Character is using the skill Bide. *Cannot be set on a mob's template or applied by an item.<br />
|}<br />
<br />
Some of these affects can't be applied to a mob's template, only by spells; homing attack, stat enhancement, extension, kamikaze, short term combat effect, oozaru form, double image, seraph form, Jumi empathy, surefire casting, and leechseed.<br />
<br />
===OBJ FLAGS===<br />
For more details on object types see [[Flags Compendium/Obj Types]]<br />
<br />
{|<br />
|[[light]] || Light sources, go in a special 'light' slot when equipped no matter what wear flags you use<br />
|-<br />
|[[scroll]] || Can be recited or read to cast 1-4 spells on a target. Works from base inventory, consumed when used, uses [[Artifice]] skill.<br />
|-<br />
|[[wand]] || Can be zapped or used to cast 1 spell a set number of times on a target. Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[staff]] || Can be brandished or used to cast 1 spell a set number of times on all targets in a room! Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[weapon]] || Changes wearer's melee autoattack damage to the type and amount specified in the object. Must be in the Wield slot to work.<br />
|-<br />
|[[treasure]] || No inherent properties, reserved for salable loot.<br />
|-<br />
|armor || Modifies wearer's armor values. Can be equipped anywhere.<br />
|-<br />
|[[potion]] || Can be quaffed or drunk to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|-<br />
|[[furniture]] || Various flags allow characters to sit, rest, stand, or sleep on, in, or at these objects. Recovery rates can be modified as well.<br />
|-<br />
|[[trash]] || No inherent properties, reserved for nonsalable loot.<br />
|-<br />
|[[container]] || Object that holds other objects. Can be closable/lockable like a door.<br />
|-<br />
|[[drinkcontainer]] || Holds a set quantity of a certain [[liquid]]. Liquids can be replaced with different liquids. Disappears when empty unless NOEXPLODE is set.<br />
|-<br />
|[[key]] || Object vanishes on logout. Has no other properties.<br />
|- <br />
|[[food]] || Can be eaten for food/full value and cast 1 spell on the eater.<br />
|- <br />
|[[money]] || Is abstracted into current wealth when picked up by a player. Dropped wealth turns into a money object. The Priest class can sacrifice money to recover mana for 1 MP per 50 silver.<br />
|- <br />
|boat || Can be equipped or in base inventory for players to move in water rooms. Defunct.<br />
|- <br />
|npccorpse || NPC [[Corpse]]. Reserved.<br />
|- <br />
|[[fountain]] || Like a drinkcontainer but the [[liquid]] inside can't be poisoned. Drinkcontainers can also be 'fill'ed from it.<br />
|- <br />
|[[pill]] || Can be eaten to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|- <br />
|protect || Uncoded junk. Don't use.<br />
|- <br />
|map || Uncoded junk. Don't use.<br />
|- <br />
|[[portal]] || Objects that can be 'entered' to take the character to a set room. Can be closable/lockable like a door.<br />
|- <br />
|warpstone || Used to be necessary for the Nexus spell.<br />
|- <br />
|roomkey || Uncoded junk. Don't use.<br />
|- <br />
|gem || Uncoded junk. Don't use.<br />
|- <br />
|[[jewelry]] || No inherent properties. Used for equippables that aren't armor.<br />
|- <br />
|[[Event Item|event]] || An object with both charges and cooldown capability, which executes an mprog when 'zap'ped or 'use'd. Uses [[Artifice]] skill.<br />
|- <br />
|slotmachine || <s>Type "Game slots" at a slot machine to spin the wheel. Slot machines can have their cost and jackpot size specified in the object template.</s> Just kidding! Disabled.<br />
|- <br />
|gun || Uncoded junk. Don't use.<br />
|- <br />
|ammo || Uncoded junk. Don't use.<br />
|- <br />
|[[vehicle]] || Vehicles allow players to consume less movement points as they travel, move faster, and/or travel to rooms they can't enter on foot.<br />
|- <br />
|exit || Uncoded junk. Don't use. Not the same as a real [[exit]].<br />
|- <br />
|[[rod]] || Can be zapped or used to cast 1 spell on a target with a set delay between uses. Must be equipped, any slot is OK. Uses [[Artifice]] skill.<br />
|}<br />
====EXTRA FLAGS====<br />
{|<br />
|glow || Item can be seen in the dark, shows (glowing) before its short desc<br />
|-<br />
|hum || Item shows (Humming) before its short desc<br />
|-<br />
|norecharge || Wand, staff, rod, or event can't be recharged with the Recharge spell.<br />
|-<br />
|autoconsume || Item is automatically used as soon as it's picked up off the ground. Works with [[potions]], [[pills]], and [[artifice]] items.<br />
|-<br />
|evil || Item has a red aura if you can detect evil, can be removed with Bless.<br />
|-<br />
|invis || Item can only be seen if you have detect invis, and shows (Invis) if you can<br />
|-<br />
|magic || Item shows as magic if you can detect magic<br />
|-<br />
|nodrop || Item can't be dropped, can be removed with Bless<br />
|-<br />
|bless || Item has a blue aura if you can detect good, can't be poisoned, and is a little easier to enchant. Is removed by Curse.<br />
|-<br />
|noremove || Item can't be removed. This flag is removed by uncursing<br />
|-<br />
|inventory || Item is part of a shopkeeper's inventory and will be sold with infinite quantity left. Also evaporates when the holder dies, like rotdeath.<br />
|-<br />
|nopurge || Item can't be purged. Use sparingly!<br />
|-<br />
|rotdeath || Item poofs when whoever is holding it dies. If a mob dies with one of these, it will vanish.<br />
|-<br />
|visdeath || Item can only be seen by immortals<br />
|-<br />
|uncounted || Item doesn't count against the holder's carry number or weight capacities.<br />
|-<br />
|nonmetal || Item is unaffected by Heat Metal<br />
|-<br />
|meltdrop || Item poofs when dropped or stolen. If a mob dies with one of these, it will appear in the room. <br />
|-<br />
|decaying || Item loses 1 condition per minute, then disintegrates.<br />
|-<br />
|sellextract || Item poofs when sold to shopkeeper -- doesn't show up in their inventory<br />
|-<br />
|nodestroy || (AKA burn_proof in the code for some reason) Item can't be poisoned, and can't be destroyed by various item-destroying affects (which I think are disabled)<br />
|-<br />
|nouncurse || Item can't be uncursed. (nodrop, noremove flags)<br />
|-<br />
|runic || Unused<br />
|-<br />
|adhesive || Item stays with a player, not on their corpse<br />
|-<br />
|nochk || [[Wand]], [[Scroll]], [[Staff]], [[Rod]], and [[Event Item|Event]] items with this flag won't check a character's [[artifice]] skill when used, but just always work<br />
|-<br />
|noremort || Item can't be carried through a remort<br />
|-<br />
|inert || Item doesn't appear in rooms its in<br />
|-<br />
|noexplode || Wand and staff type item won't disintegrate when their charges are used up. Drinkcontainers won't poof when empty.<br />
|}<br />
<br />
====EXTRA2 FLAGS====<br />
{|<br />
|antihuman || Can't be equipped by Human race<br />
|-<br />
|antimoogle || Can't be equipped by Moogle race<br />
|-<br />
|antisaiyan || Can't be equipped by Saiyan race<br />
|-<br />
|antiesper || Can't be equipped by Esper race<br />
|-<br />
|antihylian || Can't be equipped by Hylian race<br />
|-<br />
|antikokiri || Can't be equipped by Kokiri race<br />
|-<br />
|antigiganto || Can't be equipped by Giganto race<br />
|-<br />
|antimatango || Can't be equipped by Matango race<br />
|-<br />
|antireploid || Can't be equipped by Reploid race<br />
|-<br />
|antikoopa || Can't be equipped by Koopa race<br />
|-<br />
|antipmpkn || Can't be equipped by Pumpkinhead race<br />
|-<br />
|antiknight || Can't be equipped by Knight class<br />
|-<br />
|antiwarrior || Can't be equipped by Warrior class<br />
|-<br />
|antithief || Can't be equipped by Thief class<br />
|-<br />
|antiwizard || Can't be equipped by Wizard class<br />
|-<br />
|antipriest || Can't be equipped by Priest class<br />
|-<br />
|antigeomancer || Can't be equipped by Geomancer class<br />
|-<br />
|antisummoner || Can't be equipped by Summoner class<br />
|-<br />
|antifemale || Can't be equipped by female characters<br />
|-<br />
|antimale || Can't be equipped by male characters<br />
|-<br />
|antineuter || Can't be equipped by sexless characters<br />
|-<br />
|cursed || Item becomes noremove when equipped<br />
|-<br />
|unique || Characters can't pick up one of these if they already have one.<br />
|-<br />
|remortable || Item was carried through a remort and won't vanish on logout if it's out of the player's level range.<br />
|-<br />
|antinu || Can't be equipped by Nu race<br />
|-<br />
|antikirby || Can't be equipped by Kirby race<br />
|-<br />
|antilobsterman || Can't be equipped by Lobster race<br />
|-<br />
|antiranboob || Can't be equipped by Ranboob race<br />
|-<br />
|antijumi || Can't be equipped by Jumi race<br />
|-<br />
|antidancer || Can't be equipped by Dancer class<br />
|-<br />
|antimob || Can't be equipped by mobs<br />
|}<br />
<br />
* NOTE: Old classes are affected by antiwizard, etc, just as new ones are.<br />
<br />
====EXTRA3 FLAGS====<br />
{|<br />
|exalted || Can only be equipped by players who have remorted at least once (if remort $n >= 2)<br />
|-<br />
|heroic || Can only be equipped by players who have remorted at least five times (if remort $n >= 6)<br />
|-<br />
|epic|| Can only be equipped by players who have remorted at least ten times (if remort $n >= 11)<br />
|-<br />
|perishable|| Object will disappear on logout if the character is not in the object's source area.<br />
|-<br />
|owned|| Object cannot be equipped unless it shares all name keywords with the character.<br />
|}<br />
<br />
* NOTE 1: Objects restricted by number of remorts will also not be saved to unqualified player files when logging out, UNLESS they are somehow also flagged as remortable.<br />
* NOTE 2: Mobiles cannot remort, so exalted, heroic, and epic objects are effectively also antimob.<br />
<br />
===AREA EXFLAGS===<br />
{|<br />
|visdeath || Area is not visible on 'areas' display.<br />
|-<br />
|norecall || No recalling anywhere within this area.<br />
|-<br />
|nosummon || No summoning within this area.<br />
|-<br />
|noweather || Weather is always 0 wind, 0 sky, and the 'weather' command fails with no map displayed.<br />
|}<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2216Mprog Compendium2019-02-04T15:49:12Z<p>Pascal: /* MOB COMMANDS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: can only use EITHER 'or' or 'and' per ifchk.<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum/name><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Mob remove can also take a name argument, but be incredibly diligent when using this as it could potentially remove a different object that shares a name keyword. (For example, do not 'mob remove $n sword' because it will almost certainly not remove the item you intend!) Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it. Do not 'mob remove' things from players' inventories without good reason.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> <victim><br />
This command makes the victim the pet of the target. It works almost exactly like the staff command of the same name. Target and victim are arguments, and they can be any character in the world. However, mob petify will not work if victim is a player or if target already has a pet. It's probably not a great idea to petify a victim that's not in the same room as the target, even though you can within the extent of the command.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), align(#), damtype(a), hitroll(#), magroll(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Player_Housing&diff=2211Player Housing2019-01-28T15:05:50Z<p>Pascal: </p>
<hr />
<div>[[File:Customhomes.png|200px|thumb|right|Home is where the grass is.]]<br />
== Housing Admin ==<br />
Lilly is the current housing admin. All questions or clarifications will be deferred to her.<br />
<br />
<br />
==HOUSING==<br />
What you need to purchase a home:<br />
<br />
1. One immortal token or three restring tokens.<br />
<br />
2. Your character must be at least level 50.<br />
<br />
3. One of your characters needs to have at least 100 hours of play time.<br />
<br />
<br />
<br />
==ACCEPTABLE IMMORTAL TOKENS==<br />
<br />
1. Heart-tipped arrow (Versalia)<br />
<br />
2. Ripe, yellow Benana (Benamas)<br />
<br />
3. A Clay cup of Ageatea (Ageatii)<br />
<br />
4. Tuna Token (Carsanquay)<br />
<br />
5. A Bag of Grass Seed (Lilly)<br />
<br />
6. An Abysblossom (Abysmal)<br />
<br />
7. A Silk Top Hat with a Red Band (Ozlynn)<br />
<br />
8. A Tangible Piece of Void (Sham)<br />
<br />
9. A Totally REAL Gold Coin (Cooper)<br />
<br />
==RESIDENTIAL AREAS FOR PURCHASE==<br />
<br />
When purchasing a home, you must fulfill the above requirements, and then contact Lilly to arrange to pay the following sums to begin building your first room. All initial rooms come with a town-specific interactable object that will reset the house as your recall point, as well as allow other people inside your home to visit. Price is based on level 5000+MinLvlx50 (except Gold City).<br />
<br />
You must provide descriptions for the rooms you are purchasing.<br />
<br />
{| border="1"<br />
|+HOME PRICES<br />
|-<br />
!Town<br />
!Price (in Gold)<br />
!Starter Object<br />
!Pet (vending)<br />
|-<br />
|Truce<br />
|5000<br />
|Wall-Mounted Shield<br />
|Alley Cat<br />
|-<br />
|Viorar<br />
|5000<br />
|Firefly Lamp<br />
|Dudbear<br />
|-<br />
|Crysta<br />
|5250<br />
|Woven Quilt<br />
|Goose<br />
|-<br />
|Mongrelia<br />
|5250<br />
|Dog Collar<br />
|Growlithe<br />
|-<br />
|Monstro Town<br />
|5250<br />
|Dancing Star<br />
|Goomba Martial Artist<br />
|-<br />
|Rocket Town<br />
|5500<br />
|Model Rocket<br />
|Capsule J2<br />
|-<br />
|Wutai<br />
|5500<br />
|Wall Scroll<br />
|Ninji<br />
|-<br />
|Cosmo Canyon<br />
|6000<br />
|Crimson Candle<br />
|Litwick<br />
|-<br />
|Mabe Village<br />
|6000<br />
|Cucco Clock<br />
|Cucco Warrior<br />
|-<br />
|Arlia<br />
|6250<br />
|Silver Star<br />
|Drillbur<br />
|-<br />
|Tonoe<br />
|6250<br />
|Mini Haystack<br />
|Miltank<br />
|-<br />
|Medina<br />
|6500<br />
|Magus Statuette<br />
|Kappa<br />
|-<br />
|Shrike<br />
|6750<br />
|TiVo Set<br />
|Sniper Joe<br />
|-<br />
|Mandala<br />
|7000<br />
|a Veedio<br />
|Nemesis Owl<br />
|-<br />
|Brei<br />
|7000<br />
|Anvil<br />
|Timburr<br />
|-<br />
|Final Weapon<br />
|7000<br />
|Repliforce Insignia<br />
|Porygon Maverick<br />
|-<br />
|Lasacul<br />
|7500<br />
|Miniature Gondola<br />
|Surskit<br />
|-<br />
|Todo<br />
|7500<br />
|Mounted Salmon<br />
|Frostifur<br />
|-<br />
|Dry Dry Outpost<br />
|7500<br />
|Li'l Cactus<br />
|Mad Mallard<br />
|-<br />
|Brigantes<br />
|8000<br />
|Jack'O'Lantern<br />
|Crobat<br />
|-<br />
|Caspia<br />
|8000<br />
|Antique Hourglass<br />
|Dainslaif<br />
|-<br />
|Gold City<br />
|10000<br />
|Large Pile of Gold<br />
|Golden Golduck<br />
|}<br />
<br />
Players may choose a starting item that belongs to another town, instead of their town's<br />
default one, for an additional fee of '''500 gold'''.<br />
<br />
Starting pets, as listed above, will become available once a player purchases a Pet Vendor<br />
for their home (see Housing Shop below).<br />
<br />
==ADDING ON ROOMS==<br />
You may add on extra rooms to your home by paying increasing amounts of restring tokens and gold. Immortal tokens count as '''three''' restring tokens here.<br />
<br />
{| border="1"<br />
|+ROOM EXPANSIONS<br />
|-<br />
!Total Rooms<br />
!Restring Tokens Required<br />
!Gold<br />
|-<br />
|1<br />
|N/A<br />
|N/A<br />
|-<br />
|2<br />
|1<br />
|500<br />
|-<br />
|3<br />
|2<br />
|500<br />
|-<br />
|4<br />
|4<br />
|500<br />
|-<br />
|5<br />
|8<br />
|500<br />
|-<br />
|6<br />
|10<br />
|500<br />
|-<br />
|7+<br />
|10<br />
|500 x (RoomCnt - 5)<br />
|}<br />
<br />
<br />
==HOUSE ACCESS==<br />
<br />
ALL homes exit onto the town room of your choice, but entry is all located at the same spot. A signpost will be in each town listing addresses. Knock on that address to be allowed in if you are the owner, or the owner is in and has "left the door open" (by activating their specific starter item).<br />
<br />
<br />
==PORTALS==<br />
<br />
Portals come in the form of purchasable objects for your home. Prices of these portals are based on proximity in distance and level, among other things. There are two kinds of portals, Rank 1 and Rank 2: Rank 1 portals include the basic mainstay towns and large cities (and are also the 'default' portals available for purchase), while Rank 2 portals include most all of the rest of the "civilized" regions, including the villages, smaller towns, and locations that hold a uniformity or governing authority of some kind.<br />
<br />
For Rank 1 Portals, add 1 and the level disparity in 10's to the coordinate disparity (though allow for wrapping from the westernmost and easternmost portions on the map). Multiply that total by 300 for the price in gold. Rank 1 portals are seen as the CAPITAL LETTER locations on the grid below.<br />
<br />
<br />
'''(L + D + 1) x 300 = Gold Price'''<br />
<br />
<br />
'''Example 1:''' Calculate price of (V)iorar to (T)ruce. They are 6 spaces away (diagonals are used). Because they are the same level there is no disparity. The cost of a portal would be 2100 gold ( [0 + 6 + 1] x 300).<br />
<br />
'''Example 2:''' Calculate price of (V)iorar to (G)old City. By going off the west edge of the map and rejoining on the right, we see we are 12 spaces away (as opposed to 18). The level disparity is 6. [6 + 12 + 1] x 300 = 5700 Gold for a Viorar to Gold City Portal.<br />
<br />
<br />
<br />
For Rank 2 Portals, add 3 and the level disparity in 10's to the coordinate disparity. Multiply that total by 400 for the price in gold. Rank 2 portals are seen as the LOWERCASE LETTER locations on the grid below.<br />
<br />
<br />
'''(L + D + 3) x 400 = Gold Price'''<br />
<br />
<br />
'''Example 1:''' Calculate the price of (T)ruce to (b)rei. They are 7 spaces away (diagonals are used) and have a level disparity of 4. [4 + 7 + 3] x 400 = 5600 gold for a Truce to Bree portal.<br />
<br />
'''Example 2:''' Calculate the price of (M)onstro Town to (c)aspia. By wrapping around the west edge of the map, they are 12 spaces away (instead of 18) and have a level disparity of 5. [5 + 12 + 3] x 500 = 10000 gold for a Monstro to Caspia portal.<br />
<br />
Please note, Rank 2 portals are priced according to transport from a Rank 1 location to a<br />
Rank 2 location. In the event that a player owns a house in a Rank 2 location already,<br />
purchase of a portal to a Rank 1 location uses the price and formula for a Rank 1 portal.<br />
The price from a Rank 2 location to another Rank 2 location remains the same as the normal Rank<br />
2 portal pricing.<br />
<br />
<br />
<br />
____________________________________________________________<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .|<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .|<br />
| . . . . . . . . . . m . . t B . . . . . . . . . . . . . . .|<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| <br />
| . . . . . . k . . . . . c . . . . S . . . . . . . . . . . .| <br />
| . . . . . . . . . . . . . . w . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . r . T . . . . . m . . . . . G . . . . .| <br />
| . . . . . . . . . . . . c . . . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . L . m . . . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| <br />
| . . . . . . V . . a . . . . . m . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . t . . . . . . . . . . . . . . . . . . .| <br />
| . . . . M . . . . . . . . b . . . . . . . . . . . . . . . .|<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| (m) Center = Mongrelia<br />
| . . . . . . . . . . . . . . . . . . . . . . c . . . . . . .| (m) North = Mandala<br />
| . . . . . . . . . . . . . . . . . . . . . . d . . . . . . .| (m) Southeast = Mabe Village<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| (m) East = Medina<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| (c) Center = Crysta<br />
-------------------------------------------------------------- (c) North = Cosmo Canyon<br />
(c) Southeast = Caspia<br />
<br />
<br />
(NOTE: Final Weapon [Rank 1 Portal] and Pioneer 2 [Rank 2 portal] are available as well, but not listed; both locations are traversible via rocket town, and are actually in planetary orbit. Their location in terms of coordinate disparity will be considered the same location as (r)ocket Town, plus 5 [as opposed to the previous 19, which is kind of silly])<br />
<br />
<br />
<br />
==SHOPS==<br />
<br />
You may convert a home into a shop, but with restrictions. Shop profits will not fall onto the owner. Shops that are in a public house and always open to players cannot have accessible portals or other beneficial objects/mobs. You must purchase a shopkeeper. All '''regular''' items added to the shopkeeper's list cost Gold = ItemLvlx10, while exotic (hard-to-get/find) items will cost ItemLvlx30 Gold to stock. Items chosen must exist ingame already and be fairly reasonable choices; exceptions include crafting items, quest rewards, and other items that are likely not meant to be readily available in a shop setting. Max shop list is 10. Some specific exclusions may apply on a case-by-case scenario for MUD integrity; if you're not sure, the best way to find out is to ask Lilly.<br />
<br />
To add a Custom Item to the shop, please see [[Custom_Item_Creation|this separate page]] detailing how custom item creation is applied. Any questions on this process should be directed to Lilly via note or tell (if she is online at the time).<br />
<br />
<br />
==HOUSING SHOP==<br />
<br />
You may purchase a whole slew of neat things for your house! New things are added from time to time, too! Please note that only one of '''each type''' of "Shop" mobs (banker, healer, shopkeeper, etc.) can exist in a room at a time, as it is physically impossible to interact with two healers, two shopkeepers, etc. in the same room.<br />
<br />
{| border="1"<br />
|+'''HOUSING SHOP'''<br />
|-<br />
!Item/NPC<br />
!Gold<br />
!Description<br />
|-<br />
|a Painting of [enter town here]<br />
|See Portal section<br />
|Portal that leads to a town or city<br />
|-<br />
|Mr. Moit<br />
|5000<br />
|Turban Matango shopkeeper<br />
|-<br />
|a Moogle Maid<br />
|500<br />
|"Cleans" your house, recovers your HP and MP.<br />
|-<br />
|a Servbot Helper<br />
|5000<br />
|Casts "Recharge" on items given to it<br />Can also be set to cast "Phlogiston" on lights given to it<br />Can be set to do both for 8000g<br />
|-<br />
|a training dummy<br />
|1000<br />
|Beat it up, has about 1000 HP, resist weapon and magic.<br />
|-<br />
|a house pet<br />
|500<br />restring token<br />
|A custom, interactable mob that remains at your house. Provides no tangible benefit.<br />
|-<br />
|secret exits<br />
|500<br />restring token<br />
|Custom ways to open/reveal exits (ex: turn statue head to slide open bookshelf)<br />Includes Mobprogs and applying 'hidden' flags.<br />
|-<br />
|a pokeball vending machine<br />
|5000<br />
|Sells pokeballs with pets inside, only for owner use^<br />
|-<br />
|Fountain~<br />
|1000<br />
|Infinite source of specific liquid.<br />May purchase copy of one that exists already, or add a Restring Token for a custom one.<br />
|-<br />
|Furniture~<br />
|500<br />
|Immobile, untakeable objects of any kind.<br />May purchase copy of one that exists already, or pay 500g+Restring for Customized.<br />
|-<br />
|Banker<br />
|4000<br />Req. House Size of 4+ Rooms<br />
|Your own personal banker!<br />
|-<br />
|Mage<br />
|4000<br />Req. House Size of 4+ Rooms<br />
|Your own personal mage! (Fees still apply)<br />
|-<br />
|Necromancer<br />
|6000<br />Restring Token<br />Req. House Size of 5+ Rooms<br />
|Your own personal... wait. People actually WANT one of these in their HOUSE..!?<br /><br />
|Requires own room.<br />
|-<br />
|Mana Orchard Treant<br />
|5000<br />2 Restring Tokens<br />Req. House Size of 3+ Rooms<br />
|Sentient tree infused with Mana that will consume seeds and bear fruit/vegetables from them.<br />Requires 'outside'-type room.<br />
|-<br />
|Cooking Station<br />
|3500<br />2 Restring Tokens<br />
|Includes an array of kitchenware needed to prepare lots of yummy recipes! (Note: Food not included)<br />Requires 'inside'-type room.<br />
|-<br />
|Krak Pot<br />
|5000<br />3 Restring Tokens<br />
|A decorative, sentient iron pot with knack for alchemical knowledge.<br />
|-<br />
|Cookbooks<br />
|1000, 2000, 3000<br />
|You can't cook without knowing how!<br />Books include 'Beginner', 'Intermediate', and 'Advanced' recipes at incremental pricing.<br />
|-<br />
|Alchenomicon: Basic Tomes<br />
|1500, 3000, 4000<br />
|Learn the secrets of the alchemist!<br />Books include 'Beginner', 'Intermediate', and 'Advanced' recipes at incremental pricing.<br />
|-<br />
|Alchenomicon: Special Tomes<br />
|10000 each<br />
|Additional Alchemy books for the fanatics. Currently available: "A Composition of Compositions".<br />
|-<br />
|Polychromatic Crystal<br />
|2000<br />1 Imm Token<br />
|A splendorous, multi-hued crystal that bestows a heavy and long-duration buff based on the current day.<br />
|-<br />
|Custom Portal + Location<br />
|8000<br />1 Imm Token<br />
|A customized portal that can take you anywhere in the Cleft, with some exceptions.<br />No locations beyond quest/level/item-required mobs (i.e Goa, Cave of Trials' entrance, etc.)<br />Portal will have a level requirement of (MinAreaLv - 10).<br />
|-<br />
|A Cow<br />
|2500<br />Req. House Size of 3+ Rooms<br />
|A domesticated farm animal that will occasionally produce milk when properly fed.<br />Requires 'outside'-type room.<br />
|-<br />
|A Cucco<br />
|2500<br />Req. House Size of 3+ Rooms<br />
|A feathered farm animal that will occasionally produce eggs when properly fed.<br />Requires 'outside'-type room.<br />
|-<br />
|A Produce Cart<br />
|1500<br />Req. 'Mana Treant' Purchase<br />
|A large cart that will follow you around, carrying your produce.<br />Only useable in the player's house.<br />
|-<br />
|A Locker<br />
|3000<br />
|A place for no-loss storage of items.<br />See 'locker' helpfile in-game for details.<br />
|-<br />
|A Combat Simulation Room<br />
|12000<br />1 Imm Token<br />
|A holographic projector in this room will allow you to re-fight mobs of the Cleft of Dimensions at your leisure. Some mobs may be unavailable if their programming becomes unstable due to being fought outside of their specific room, and all mobs will be given immunity to charm. Mobs defeated in this simulation will not yield any gold or item rewards, and reward only 50% normal experience.<br />
|Cost is per-mob: '''Regular Mobs''' = 10g*Lvl ... '''Boss Mobs''' = 50g*Lvl<br />
|This purchase requires a new room '''entirely''' devoted to this purchase and nothing else, and the cost of the room's customization is included in the purchase price.<br />
|-<br />
|Inventory-to-Furniture Conversion<br />
|(Varying Gold)<br />1 Restring Token<br />
|Players may 'convert' an item in their inventory (which will be removed from inventory during the conversion process) to a piece of furniture in their house that will remain there permanently. Most items will be an immobile, ineffective object that simply serves as a visual furniture, but items with infinite charges or usage (Rods, event items, etc.) may retain their usability under the same delay they had as a held item. Exceptions apply and gold cost is on a per-item basis, so ask Lilly for specific item qualifications and costs.<br />
|-<br />
|Equipment Mannequins<br />
|10000<br />3 Restring Tokens<br />Max 8<br />
|A mannequin that can be used to store equipment sets. One piece of equipment per slot may be placed upon it, and storage/retrieval is processed via Qflags (hence the maximum of 8 per player). For details, please send Lilly a tell or a note.<br />
|-<br />
|Equipment Capsules<br />
|20000<br />1 Restring Token<br />Req. House Size of 6+ Rooms<br />Req. Shopkeeper Mob<br />
|While not precisely a house-specific item, this purchase will allow you to create an item that can "hold" multiple pieces of equipment in one collapsible item, much like a mannequin, except carried with you. This is a heavily-customized item and all details should be discussed with Lilly.<br />
|-<br />
|a Clanlink Transporter<br />
|4000<br />
|Transfers a player from their Player House to their Clan Hall (if they have one).<br />
|-<br />
|a Faithful Companion<br />
|60000<br />1 Immortal Token<br />Req. Pet Vending Machine<br />
|A custom pet variant that will level alongside you and gain statistical bonuses every ten levels! This custom pet is extremely mobprog intensive, hence the high cost, and all questions and details should be asked of and confirmed with Lilly. Cost for purchase FROM vending machine, once created, is a flat 2500g. See [[Faithful_Companion|this page]] for details and information.<br />
|-<br />
|a Keyring<br />
|1000<br />1 Restring Token<br />
|A stationary item in your home that will allow you to store and recall keys that you have acquired during your travels. While the initial keyring item is inexpensive, adding keys to the ring requires a fee of 20g per level up to the minimum level of the zone that the key is found in. Some keys may be given a higher applied level depending on where they lead. Maximum of 50 unique keys per character.<br />
|}<br />
<br />
^One Town-specific mob comes with machine (may not necessarily be a pokemon), can add more types to machine by paying '''2500''' gold - Max of 8. Cost to purchase pet from vending machine, once available, is Lvlx3 gold for the first 50 levels, and then Lvlx5 gold for any of the last 50 levels.<br />
<br />
@Coming Soon!<br />
<br />
~Excludes unique customized objects that exist in other players' homes.<br />
<br />
<br />
==Custom Purchases==<br />
<br />
All shop purchases can be customized.<br />
<br />
For item/npc restring (different only by appearance) add a restring token.<br />
<br />
For NPC/Pet customization (includes custom appearance AND customized mobprog [NOT INCLUDING 'Faithful Companion' variant, seen above]) add triple the gold cost and a restring token. Does not include Mana Treant, Cooking Station, or Krak-Pot; cost to fully customize any of these three purchases is 30000g and 6 restring tokens, due to their programming complexity and difficult (but doable) transition to a custom mob.<br />
<br />
<br />
== ALTERNATE HOUSING (PLAN B) ==<br />
<br />
As opposed to a home with purchased benefits, you may choose to have your home open up for all players to see and interact with. Note that it doesn't have to be an actual residence. Those types of houses are available OUTSIDE of the normal 'Signpost Entrance' that the other form of Player Housing stands by.<br />
<br />
Under this plan, you cannot have portals or free items or any other features specified above. Expansion costs however, will be the same. Instead, additional expansion will add NPCs and miniquests. Please get ahold of Lilly to discuss your ideas for potential NPCs and miniquests that may relate to the NPC/Player House, and she can quote you a price range and feasibility factor.<br />
<br />
This requires approval from the Admin, and the home and location has to "make sense" for wherever it is located. No Black Omens hovering above Wutai, as that requires extensive rebuilding of existing content on part of the staff.<br />
<br />
If you already own a home and want to convert it to "Plan B," the rate of conversion of features will be equal to what the home already has. You may have to relocate or edit the home to fit it better in its area.<br />
<br />
Plan B player houses may also be built in areas outside of towns/cities, with the aforementioned notion that it needs to make sense in regard to the area in which it resides, and with additional fees. The rate at which Plan B houses may be built in non-town locations is (5000 + [MinLvl x 100]) gold. Some restrictions also apply in terms of allowed areas, but this will go on a case-by-case basis, and discussion with Lilly about your plans or ideas is recommended.<br />
<br />
Additionally, expansion costs are slightly higher (it's dangerous work building things in the wilderness) in out-of-town locations. Here is a breakdown of what you can expect to pay, versus the normal expansion costs:<br />
<br />
{| border="1"<br />
|+WILDERNESS ROOM EXPANSIONS<br />
|-<br />
!Total Rooms<br />
!Restring Tokens Required<br />
!Gold<br />
|-<br />
|1<br />
|N/A<br />
|N/A<br />
|-<br />
|2<br />
|1<br />
|750<br />
|-<br />
|3<br />
|2<br />
|750<br />
|-<br />
|4<br />
|4<br />
|750<br />
|-<br />
|5<br />
|8<br />
|750<br />
|-<br />
|6<br />
|12<br />
|750<br />
|-<br />
|7+<br />
|12<br />
|750 x (RoomCnt - 5)<br />
|}<br />
<br />
While the ammenities available to private player houses are, as mentioned, not allowed for Plan B locations, certain exemptions may apply if it fits the house's feel decently enough. A player should talk to Lilly if they really want something that they feel would greatly add to the Plan B house's atmosphere, and perhaps a deal can be worked out.<br />
<br />
<br />
<br />
==Applying For Housing==<br />
<br />
In a note written to Lilly, please provide the '''MINIMUM''' following information:<br />
<br />
A.) Rooms: '''Room title''' (name of the room); '''Room desc''' (main description of the room); '''Extra Descs''' (any "extra" descriptions you want in the room, by way of specific keyword lookup). If you want color, add it in your note, otherwise I'm going to just go with the Cleft's basic color scheme (which is normal grey room descs and dark cyan room titles).<br />
<br />
<br />
B.) Room Linkage: If this is your first room, please include the '''exit room''' (the room in town that the exit to your house leads to). For additional rooms, include the '''direction''' they are linked from room to room. If you are creating secret exits or entrances by way of a mobprog action, include the above information while describing your hidden exit request (see below).<br />
<br />
<br />
C.) Furniture/Objects/Fountains: '''Short description''' (the name of the object) and '''long description''' (what it says when the item is in the room). You may also request '''extra descriptions''' in the same way as a Room's extra descriptions, but if you do not include any, I will assume them to be unwanted. Please also include the '''room''' that you want it placed in.<br />
<br />
<br />
D.) House Pets: '''Short description''' and '''long description''', as well as a '''physical description''' (what the mob looks like). If you want your pets to do anything via a mobprog, please be as detailed as possible with what you want them to do, how to react, and etc. There's very little I can't do, but the clearer you are in your request, the easier of a time I'll have programming them accurately. Please also include the '''room''' that you want it placed in.<br />
<br />
<br />
E.) Hidden/Special Exits/Entrances: If an activateable object is involved, please include the '''short description''' and '''long description''' (unless it is meant to be hidden). Extra descriptions are not required, but recommended if the device is meant to work as a hidden or secret exit (perhaps, for example, to give clues on its useage). Please also include the '''room''' that you want it placed in, as well as the '''linked room''' that it is meant to lead into.<br />
<br />
<br />
F.) Extras: Anything from the Housing Shop should be considered witht he above guidelines, as they apply toward anything not covered in acknowledgements A through E. If you're not sure if your point is getting across in a note you post to me, think of it this way: the more information you include, the better off we'll BOTH be.<br />
<br />
<br />
These instructions do '''not''' have to be followed to the letter; if your note skips a step or two, but is highly descriptive, I will likely be able to catch your drift and build accordingly without any interruption or irritation on my part at missing information. On the other hand, telling me 'a breadbox in the kitchen' is not explaining to me what you want. Do you want it called 'a breadbox in the kitchen'? What about the long desc? Have some consideration for what information I need to put into the item as I am creating it; all descriptions are required by the PLAYER, not for the admin to guess or have a free-for-all with. If glaring information is left out and I'm already not feeling helpful, I may leave you with a half-assed item and state that "this is what your note requested". So get your pen out and be descriptive!<br />
<br />
<br />
<br />
<br />
<br />
==Multi-Character Housing==<br />
<br />
In the interest of saving effort, time, and (perhaps most importantly) Vnums, I have decided to allow multi-character player housing. What this means is that a Player House can legally have more than one character is its "owner," but only under the following pretenses and stipulations:<br />
<br />
<br />
1.) The normal rules of a player house still apply for any moving-in character: level 50, 100 hours on any character the player owns, etc.<br />
<br />
2.) The "moving-in" character does not have to be an alt of the house-owner's player (meaning multiple players can live in one player's character's house), but '''all''' purchases that were made by the initial house-owner must also be made by the character that is moving in. This includes initial plot price (including Imm token/3 Restrings), price for every room added on since the first, and all current objects/ammenities that reside in the house.<br />
<br />
3.) Aside from this "repurchasing" cost mentioned above, a flat additional fee of 2000 gold will be charged to each character wanting to move into an already-owner player house.<br />
<br />
4.) These fees '''must''' be paid by the character intended to move in. No transfer of gold (token transferral between alts is okay, as always) between alts is allowed; if the character can't afford it, they can't move in. Plain and simple. In addition (and while I condone the compassionate notion of players helping each other out), moving-in characters will be required to pay for at least '''HALF''' of the expense of moving in out of their own pocket, including restrings. This is to prevent one super-wealthy character from amassing tons of gold and paving the way for everybody and their cousins to move into their house at little or no cost to the moving-in characters themselves. Sorry guys, but we can't have the top 1% carrying everyone on their backs; that's not really fair for the rest who do it themselves and have actually worked for what they have attained.<br />
<br />
5.) Once a player home is owned by multiple characters, additional add-ons and purchases must be made for EACH MEMBER OF THE HOUSE; the catch to multiple people living in one house is that each character is still paying for everything they get to use. Essentially, every character is still paying for their own house and living accommodations, they are simply sharing the vnums. For example, if a house had 3 rooms and someone wanted a fourth, and there were two people living in the house, each member of the house would have to pay 4 tokens and 500 gold, for a total of 8 tokens and 1000 gold. If any members of the house cannot pay, no upgrades will be made.<br />
<br />
<br />
If there is a character that would like to begin the process of moving into an already-owned player house, they should contact Lilly so that the procedure can be discussed. Obviously, the decision for a second character to move into an owned player house must be mutually-agreed-upon.<br />
<br />
<br />
<br />
<br />
<br />
==Character Housing Fund Accounts==<br />
<br />
<br />
As a personal favor to players, I am willing to keep a database for characters who wish to deposit money and restring/immortal tokens into a "Housing Account" toward the use of purchasing Player Housing items for that character. This frees up time otherwise spent idling while at level 100, trying to decide on what to purchase before one can remort, or having to wait for an Immortal to make the transaction, etc. With this, a player can simply drop off excess money and tokens to me (Lilly), and I will make a note for the character in my database with the added funding. Thus, they are free to continue playing without having to worry about where the money does or doesn't go.<br />
<br />
<br />
Two small notes:<br />
<br />
1.) Monetary balances will be kept track of in amounts of GOLD only, for the sake of ease for myself. If you have heaps of silver to lay on me, this is fine, but know that I will round whatever you give me down to the nearest whole gold piece.<br />
<br />
2.) Once you have added gold and/or tokens to this House Funding Account, it is there PERMANENTLY until used for player housing purchases. There will be no returning of these coins/tokens to the character at any time, for any reason, once I have received your deposit. '''The <u>ONLY EXCEPTION</u> to this rule is in the instance of players purchasing their own [[Custom_Item_Creation|custom-made]] items from their own shop; I will reimburse players for the amount from their account toward the cost of a [[Custom Item Creation|custom-made]] item, as long as they were the character that made the item.'''<br />
<br />
<br />
If you wish to know your current monetary/token balance, simply ask, either while I'm online or in a note, and I'll be happy to look it up for you.<br />
<br />
<br />
<br />
<br />
<br />
==Final Note==<br />
<br />
Please have patience with me after you have submitted a Player Housing request. There's a few things I would like people to consider, on my behalf, after you've made your request:<br />
<br />
1.) I'm one person, and we have a lot of players. Normally I'm not swamped, but there may be a queue, and I may not be able to get to your request on the day it is given.<br />
<br />
2.) I'm not just the Player Housing admin. I'm also the head of RP, I'm a builder, I like to play the game as a mortal from time to time, and above all this, I have an involving home life outside the Cleft. Again, there may be things that prevent me from getting to your request in a timely manner, but rest assured, as long as you have posted your note to me, I do know about it, and I will get to it.<br />
<br />
3.) Constantly reminding me of your request is not going to get it done any faster. I'm well aware that you have paid. I'm well aware that you haven't gotten your description in yet. If I'm around and I'm not working on your Housing Request, there's an extremely-likely chance that I'm working on something else at the time that, for whatever reason, is taking a higher priority at the minute.<br />
<br />
4.) I took this position willingly. If two or three days seems like too long to wait for something, know that I could abandon this project at any time and players could go back to simply waiting "until one of the Imms can get around to it" again.<br />
<br />
<br />
In short, please be patient once you've sent your note. I haven't forgotten about you, and it WILL get done. Pressuring me about it will put your place in the queue at risk, and I may delay it intentionally just to be a hag about it. ^_^<br />
<br />
For more information on Player Housing, checking out the guide [[Player_Housing_Walkthrough|here]].</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2201Mprog Compendium2019-01-12T19:47:47Z<p>Pascal: /* IFCHECKS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void 22 - lava<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
- (doesn't check to see if wearing, ONLY if in inventory)<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: can only use EITHER 'or' or 'and' per ifchk.<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> <victim><br />
This command makes the victim the pet of the target. It works almost exactly like the staff command of the same name. Target and victim are arguments, and they can be any character in the world. However, mob petify will not work if victim is a player or if target already has a pet. It's probably not a great idea to petify a victim that's not in the same room as the target, even though you can within the extent of the command.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), align(#), damtype(a), hitroll(#), magroll(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=File:Black_and_white_new_atlasjpg.jpg&diff=2190File:Black and white new atlasjpg.jpg2018-12-23T14:07:14Z<p>Pascal: </p>
<hr />
<div></div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Player_Housing&diff=2185Player Housing2018-12-15T15:41:17Z<p>Pascal: </p>
<hr />
<div>[[File:Customhomes.png|200px|thumb|right|Home is where the grass is.]]<br />
== Housing Admin ==<br />
Lilly is the current housing admin. All questions or clarifications will be deferred to her.<br />
<br />
<br />
==HOUSING==<br />
What you need to purchase a home:<br />
<br />
1. One immortal token or three restring tokens.<br />
<br />
2. Your character must be at least level 50.<br />
<br />
3. One of your characters needs to have at least 100 hours of play time.<br />
<br />
<br />
<br />
==ACCEPTABLE IMMORTAL TOKENS==<br />
<br />
1. Heart-tipped arrow (Versalia)<br />
<br />
2. Ripe, yellow Benana (Benamas)<br />
<br />
3. A Clay cup of Ageatea (Ageatii)<br />
<br />
4. Tuna Token (Carsanquay)<br />
<br />
5. A Bag of Grass Seed (Lilly)<br />
<br />
6. An Abysblossom (Abysmal)<br />
<br />
7. A Silk Top Hat with a Red Band (Ozlynn)<br />
<br />
8. A Tangible Piece of Void (Sham)<br />
<br />
9. A Totally REAL Gold Coin (Cooper)<br />
<br />
==RESIDENTIAL AREAS FOR PURCHASE==<br />
<br />
When purchasing a home, you must fulfill the above requirements, and then contact Lilly to arrange to pay the following sums to begin building your first room. All initial rooms come with a town-specific interactable object that will reset the house as your recall point, as well as allow other people inside your home to visit. Price is based on level 5000+MinLvlx50 (except Gold City).<br />
<br />
You must provide descriptions for the rooms you are purchasing.<br />
<br />
{| border="1"<br />
|+HOME PRICES<br />
|-<br />
!Town<br />
!Price (in Gold)<br />
!Starter Object<br />
!Pet (vending)<br />
|-<br />
|Truce<br />
|5000<br />
|Wall-Mounted Shield<br />
|Alley Cat<br />
|-<br />
|Viorar<br />
|5000<br />
|Firefly Lamp<br />
|Dudbear<br />
|-<br />
|Crysta<br />
|5250<br />
|Woven Quilt<br />
|Goose<br />
|-<br />
|Mongrelia<br />
|5250<br />
|Dog Collar<br />
|Growlithe<br />
|-<br />
|Monstro Town<br />
|5250<br />
|Dancing Star<br />
|Goomba Martial Artist<br />
|-<br />
|Rocket Town<br />
|5500<br />
|Model Rocket<br />
|Capsule J2<br />
|-<br />
|Wutai<br />
|5500<br />
|Wall Scroll<br />
|Ninji<br />
|-<br />
|Cosmo Canyon<br />
|6000<br />
|Crimson Candle<br />
|Litwick<br />
|-<br />
|Mabe Village<br />
|6000<br />
|Cucco Clock<br />
|Cucco Warrior<br />
|-<br />
|Arlia<br />
|6250<br />
|Silver Star<br />
|Drillbur<br />
|-<br />
|Tonoe<br />
|6250<br />
|Mini Haystack<br />
|Miltank<br />
|-<br />
|Medina<br />
|6500<br />
|Magus Statuette<br />
|Kappa<br />
|-<br />
|Shrike<br />
|6750<br />
|TiVo Set<br />
|Sniper Joe<br />
|-<br />
|Mandala<br />
|7000<br />
|a Veedio<br />
|Nemesis Owl<br />
|-<br />
|Brei<br />
|7000<br />
|Anvil<br />
|Timburr<br />
|-<br />
|Final Weapon<br />
|7000<br />
|Repliforce Insignia<br />
|Porygon Maverick<br />
|-<br />
|Lasacul<br />
|7500<br />
|Miniature Gondola<br />
|Surskit<br />
|-<br />
|Todo<br />
|7500<br />
|Mounted Salmon<br />
|Frostifur<br />
|-<br />
|Dry Dry Outpost<br />
|7500<br />
|Li'l Cactus<br />
|Mad Mallard<br />
|-<br />
|Brigantes<br />
|8000<br />
|Jack'O'Lantern<br />
|Crobat<br />
|-<br />
|Caspia<br />
|8000<br />
|Antique Hourglass<br />
|Dainslaif<br />
|-<br />
|Gold City<br />
|10000<br />
|Large Pile of Gold<br />
|Golden Golduck<br />
|}<br />
<br />
Players may choose a starting item that belongs to another town, instead of their town's<br />
default one, for an additional fee of '''500 gold'''.<br />
<br />
Starting pets, as listed above, will become available once a player purchases a Pet Vendor<br />
for their home (see Housing Shop below).<br />
<br />
==ADDING ON ROOMS==<br />
You may add on extra rooms to your home by paying increasing amounts of restring tokens and gold. Immortal tokens count as '''three''' restring tokens here.<br />
<br />
{| border="1"<br />
|+ROOM EXPANSIONS<br />
|-<br />
!Total Rooms<br />
!Restring Tokens Required<br />
!Gold<br />
|-<br />
|1<br />
|N/A<br />
|N/A<br />
|-<br />
|2<br />
|1<br />
|500<br />
|-<br />
|3<br />
|2<br />
|500<br />
|-<br />
|4<br />
|4<br />
|500<br />
|-<br />
|5<br />
|8<br />
|500<br />
|-<br />
|6<br />
|10<br />
|500<br />
|-<br />
|7+<br />
|10<br />
|500 x (RoomCnt - 5)<br />
|}<br />
<br />
<br />
==HOUSE ACCESS==<br />
<br />
ALL homes exit onto the town room of your choice, but entry is all located at the same spot. A signpost will be in each town listing addresses. Knock on that address to be allowed in if you are the owner, or the owner is in and has "left the door open" (by activating their specific starter item).<br />
<br />
<br />
==PORTALS==<br />
<br />
Portals come in the form of purchasable objects for your home. Prices of these portals are based on proximity in distance and level, among other things. There are two kinds of portals, Rank 1 and Rank 2: Rank 1 portals include the basic mainstay towns and large cities (and are also the 'default' portals available for purchase), while Rank 2 portals include most all of the rest of the "civilized" regions, including the villages, smaller towns, and locations that hold a uniformity or governing authority of some kind.<br />
<br />
For Rank 1 Portals, add 1 and the level disparity in 10's to the coordinate disparity (though allow for wrapping from the westernmost and easternmost portions on the map). Multiply that total by 300 for the price in gold. Rank 1 portals are seen as the CAPITAL LETTER locations on the grid below.<br />
<br />
<br />
'''(L + D + 1) x 300 = Gold Price'''<br />
<br />
<br />
'''Example 1:''' Calculate price of (V)iorar to (T)ruce. They are 6 spaces away (diagonals are used). Because they are the same level there is no disparity. The cost of a portal would be 2100 gold ( [0 + 6 + 1] x 300).<br />
<br />
'''Example 2:''' Calculate price of (V)iorar to (G)old City. By going off the west edge of the map and rejoining on the right, we see we are 12 spaces away (as opposed to 18). The level disparity is 6. [6 + 12 + 1] x 300 = 5700 Gold for a Viorar to Gold City Portal.<br />
<br />
<br />
<br />
For Rank 2 Portals, add 3 and the level disparity in 10's to the coordinate disparity. Multiply that total by 400 for the price in gold. Rank 2 portals are seen as the LOWERCASE LETTER locations on the grid below.<br />
<br />
<br />
'''(L + D + 3) x 400 = Gold Price'''<br />
<br />
<br />
'''Example 1:''' Calculate the price of (T)ruce to (b)rei. They are 7 spaces away (diagonals are used) and have a level disparity of 4. [4 + 7 + 3] x 400 = 5600 gold for a Truce to Bree portal.<br />
<br />
'''Example 2:''' Calculate the price of (M)onstro Town to (c)aspia. By wrapping around the west edge of the map, they are 12 spaces away (instead of 18) and have a level disparity of 5. [5 + 12 + 3] x 500 = 10000 gold for a Monstro to Caspia portal.<br />
<br />
Please note, Rank 2 portals are priced according to transport from a Rank 1 location to a<br />
Rank 2 location. In the event that a player owns a house in a Rank 2 location already,<br />
purchase of a portal to a Rank 1 location uses the price and formula for a Rank 1 portal.<br />
The price from a Rank 2 location to another Rank 2 location remains the same as the normal Rank<br />
2 portal pricing.<br />
<br />
<br />
<br />
____________________________________________________________<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .|<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .|<br />
| . . . . . . . . . . m . . t B . . . . . . . . . . . . . . .|<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| <br />
| . . . . . . k . . . . . c . . . . S . . . . . . . . . . . .| <br />
| . . . . . . . . . . . . . . w . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . r . T . . . . . m . . . . . G . . . . .| <br />
| . . . . . . . . . . . . c . . . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . L . m . . . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| <br />
| . . . . . . V . . a . . . . . m . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| <br />
| . . . . . . . . . . t . . . . . . . . . . . . . . . . . . .| <br />
| . . . . M . . . . . . . . b . . . . . . . . . . . . . . . .|<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| (m) Center = Mongrelia<br />
| . . . . . . . . . . . . . . . . . . . . . . c . . . . . . .| (m) North = Mandala<br />
| . . . . . . . . . . . . . . . . . . . . . . d . . . . . . .| (m) Southeast = Mabe Village<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| (m) East = Medina<br />
| . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .| (c) Center = Crysta<br />
-------------------------------------------------------------- (c) North = Cosmo Canyon<br />
(c) Southeast = Caspia<br />
<br />
<br />
(NOTE: Final Weapon [Rank 1 Portal] and Pioneer 2 [Rank 2 portal] are available as well, but not listed; both locations are traversible via rocket town, and are actually in planetary orbit. Their location in terms of coordinate disparity will be considered the same location as (r)ocket Town, plus 5 [as opposed to the previous 19, which is kind of silly])<br />
<br />
<br />
<br />
==SHOPS==<br />
<br />
You may convert a home into a shop, but with restrictions. Shop profits will not fall onto the owner. Shops that are in a public house and always open to players cannot have accessible portals or other beneficial objects/mobs. You must purchase a shopkeeper. All '''regular''' items added to the shopkeeper's list cost Gold = ItemLvlx10, while exotic (hard-to-get/find) items will cost ItemLvlx30 Gold to stock. Items chosen must exist ingame already and be fairly reasonable choices; exceptions include crafting items, quest rewards, and other items that are likely not meant to be readily available in a shop setting. Max shop list is 10. Some specific exclusions may apply on a case-by-case scenario for MUD integrity; if you're not sure, the best way to find out is to ask Lilly.<br />
<br />
To add a Custom Item to the shop, please see [[Custom_Item_Creation|this separate page]] detailing how custom item creation is applied. Any questions on this process should be directed to Lilly via note or tell (if she is online at the time).<br />
<br />
<br />
==HOUSING SHOP==<br />
<br />
You may purchase a whole slew of neat things for your house! New things are added from time to time, too! Please note that only one of '''each type''' of "Shop" mobs (banker, healer, shopkeeper, etc.) can exist in a room at a time, as it is physically impossible to interact with two healers, two shopkeepers, etc. in the same room.<br />
<br />
{| border="1"<br />
|+'''HOUSING SHOP'''<br />
|-<br />
!Item/NPC<br />
!Gold<br />
!Description<br />
|-<br />
|a Painting of [enter town here]<br />
|See Portal section<br />
|Portal that leads to a town or city<br />
|-<br />
|Mr. Moit<br />
|5000<br />
|Turban Matango shopkeeper<br />
|-<br />
|a Moogle Maid<br />
|500<br />
|"Cleans" your house, recovers your HP and MP.<br />
|-<br />
|a Servbot Helper<br />
|5000<br />
|Casts "Recharge" on items given to it<br />Can also be set to cast "Phlogiston" on lights given to it<br />Can be set to do both for 8000g<br />
|-<br />
|a training dummy<br />
|1000<br />
|Beat it up, has about 1000 HP, resist weapon and magic.<br />
|-<br />
|a house pet<br />
|500<br />restring token<br />
|A custom, interactable mob that remains at your house. Provides no tangible benefit.<br />
|-<br />
|secret exits<br />
|500<br />restring token<br />
|Custom ways to open/reveal exits (ex: turn statue head to slide open bookshelf)<br />Includes Mobprogs and applying 'hidden' flags.<br />
|-<br />
|a pokeball vending machine<br />
|5000<br />
|Sells pokeballs with pets inside, only for owner use^<br />
|-<br />
|Fountain~<br />
|1000<br />
|Infinite source of specific liquid.<br />May purchase copy of one that exists already, or add a Restring Token for a custom one.<br />
|-<br />
|Furniture~<br />
|500<br />
|Immobile, untakeable objects of any kind.<br />May purchase copy of one that exists already, or pay 500g+Restring for Customized.<br />
|-<br />
|Banker<br />
|4000<br />Req. House Size of 4+ Rooms<br />
|Your own personal banker!<br />
|-<br />
|Mage<br />
|4000<br />Req. House Size of 4+ Rooms<br />
|Your own personal mage! (Fees still apply)<br />
|-<br />
|Necromancer<br />
|6000<br />Restring Token<br />Req. House Size of 5+ Rooms<br />
|Your own personal... wait. People actually WANT one of these in their HOUSE..!?<br /><br />
|Requires own room.<br />
|-<br />
|Mana Orchard Treant<br />
|5000<br />2 Restring Tokens<br />Req. House Size of 3+ Rooms<br />
|Sentient tree infused with Mana that will consume seeds and bear fruit/vegetables from them.<br />Requires 'outside'-type room.<br />
|-<br />
|Cooking Station<br />
|3500<br />2 Restring Tokens<br />
|Includes an array of kitchenware needed to prepare lots of yummy recipes! (Note: Food not included)<br />Requires 'inside'-type room.<br />
|-<br />
|Krak Pot<br />
|5000<br />3 Restring Tokens<br />
|A decorative, sentient iron pot with knack for alchemical knowledge.<br />
|-<br />
|Cookbooks<br />
|1000, 2000, 3000<br />
|You can't cook without knowing how!<br />Books include 'Beginner', 'Intermediate', and 'Advanced' recipes at incremental pricing.<br />
|-<br />
|Alchenomicon: Basic Tomes<br />
|1500, 3000, 4000<br />
|Learn the secrets of the alchemist!<br />Books include 'Beginner', 'Intermediate', and 'Advanced' recipes at incremental pricing.<br />
|-<br />
|Alchenomicon: Special Tomes<br />
|10000 each<br />
|Additional Alchemy books for the fanatics. Currently available: "A Composition of Compositions".<br />
|-<br />
|Polychromatic Crystal<br />
|2000<br />1 Imm Token<br />
|A splendorous, multi-hued crystal that bestows a heavy and long-duration buff based on the current day.<br />
|-<br />
|Custom Portal + Location<br />
|8000<br />1 Imm Token<br />
|A customized portal that can take you anywhere in the Cleft, with some exceptions.<br />No locations beyond quest/level/item-required mobs (i.e Goa, Cave of Trials' entrance, etc.)<br />Portal will have a level requirement of (MinAreaLv - 10).<br />
|-<br />
|A Cow<br />
|2500<br />Req. House Size of 3+ Rooms<br />
|A domesticated farm animal that will occasionally produce milk when properly fed.<br />Requires 'outside'-type room.<br />
|-<br />
|A Cucco<br />
|2500<br />Req. House Size of 3+ Rooms<br />
|A feathered farm animal that will occasionally produce eggs when properly fed.<br />Requires 'outside'-type room.<br />
|-<br />
|A Produce Cart<br />
|1500<br />Req. 'Mana Treant' Purchase<br />
|A large cart that will follow you around, carrying your produce.<br />Only useable in the player's house.<br />
|-<br />
|A Locker<br />
|3000<br />
|A place for no-loss storage of items.<br />See 'locker' helpfile in-game for details.<br />
|-<br />
|A Combat Simulation Room<br />
|12000<br />1 Imm Token<br />
|A holographic projector in this room will allow you to re-fight mobs of the Cleft of Dimensions at your leisure. Some mobs may be unavailable if their programming becomes unstable due to being fought outside of their specific room, and all mobs will be given immunity to charm. Mobs defeated in this simulation will not yield any gold or item rewards, and reward only 50% normal experience.<br />
|Cost is per-mob: '''Regular Mobs''' = 10g*Lvl ... '''Boss Mobs''' = 50g*Lvl<br />
|This purchase requires a new room '''entirely''' devoted to this purchase and nothing else, and the cost of the room's customization is included in the purchase price.<br />
|-<br />
|Inventory-to-Furniture Conversion<br />
|(Varying Gold)<br />1 Restring Token<br />
|Players may 'convert' an item in their inventory (which will be removed from inventory during the conversion process) to a piece of furniture in their house that will remain there permanently. Most items will be an immobile, ineffective object that simply serves as a visual furniture, but items with infinite charges or usage (Rods, event items, etc.) may retain their usability under the same delay they had as a held item. Exceptions apply and gold cost is on a per-item basis, so ask Lilly for specific item qualifications and costs.<br />
|-<br />
|Equipment Mannequins<br />
|10000<br />3 Restring Tokens<br />Max 8<br />
|A mannequin that can be used to store equipment sets. One piece of equipment per slot may be placed upon it, and storage/retrieval is processed via Qflags (hence the maximum of 8 per player). For details, please send Lilly a tell or a note.<br />
|-<br />
|Equipment Capsules<br />
|20000<br />1 Restring Token<br />Req. House Size of 6+ Rooms<br />Req. Shopkeeper Mob<br />
|While not precisely a house-specific item, this purchase will allow you to create an item that can "hold" multiple pieces of equipment in one collapsible item, much like a mannequin, except carried with you. This is a heavily-customized item and all details should be discussed with Lilly.<br />
|-<br />
|a Clanlink Transporter<br />
|4000<br />
|Transfers a player from their Player House to their Clan Hall (if they have one).<br />
|-<br />
|a Faithful Companion<br />
|60000<br />1 Immortal Token<br />Req. Pet Vending Machine<br />
|A custom pet variant that will level alongside you and gain statistical bonuses every ten levels! This custom pet is extremely mobprog intensive, hence the high cost, and all questions and details should be asked of and confirmed with Lilly. Cost for purchase FROM vending machine, once created, is a flat 2500g. See [[Faithful_Companion|this page]] for details and information.<br />
|-<br />
|a Keyring<br />
|1000<br />1 Restring Token<br />
|A stationary item in your home that will allow you to store and recall keys that you have acquired during your travels. While the initial keyring item is inexpensive, adding keys to the ring requires a fee of 20g per level up to the minimum level of the zone that the key is found in. Some keys may be given a higher applied level depending on where they lead. Maximum of 50 unique keys per character.<br />
|}<br />
<br />
^One Town-specific mob comes with machine (may not necessarily be a pokemon), can add more types to machine by paying '''2500''' gold - Max of 8. Cost to purchase pet from vending machine, once available, is Lvlx3 gold for the first 50 levels, and then Lvlx5 gold for any of the last 50 levels.<br />
<br />
@Coming Soon!<br />
<br />
~Excludes unique customized objects that exist in other players' homes.<br />
<br />
<br />
==Custom Purchases==<br />
<br />
All shop purchases can be customized.<br />
<br />
For item/npc restring (different only by appearance) add a restring token.<br />
<br />
For NPC/Pet customization (includes custom appearance AND customized mobprog [NOT INCLUDING 'Faithful Companion' variant, seen above]) add triple the gold cost and a restring token. Does not include Mana Treant, Cooking Station, or Krak-Pot; cost to fully customize any of these three purchases is 30000g and 6 restring tokens, due to their programming complexity and difficult (but doable) transition to a custom mob.<br />
<br />
<br />
== ALTERNATE HOUSING (PLAN B) ==<br />
<br />
As opposed to a home with purchased benefits, you may choose to have your home open up for all players to see and interact with. Note that it doesn't have to be an actual residence. Those types of houses are available OUTSIDE of the normal 'Signpost Entrance' that the other form of Player Housing stands by.<br />
<br />
Under this plan, you cannot have portals or free items or any other features specified above. Expansion costs however, will be the same. Instead, additional expansion will add NPCs and miniquests. Please get ahold of Lilly to discuss your ideas for potential NPCs and miniquests that may relate to the NPC/Player House, and she can quote you a price range and feasibility factor.<br />
<br />
This requires approval from the Admin, and the home and location has to "make sense" for wherever it is located. No Black Omens hovering above Wutai, as that requires extensive rebuilding of existing content on part of the staff.<br />
<br />
If you already own a home and want to convert it to "Plan B," the rate of conversion of features will be equal to what the home already has. You may have to relocate or edit the home to fit it better in its area.<br />
<br />
Plan B player houses may also be built in areas outside of towns/cities, with the aforementioned notion that it needs to make sense in regard to the area in which it resides, and with additional fees. The rate at which Plan B houses may be built in non-town locations is (5000 + [MinLvl x 100]) gold. Some restrictions also apply in terms of allowed areas, but this will go on a case-by-case basis, and discussion with Lilly about your plans or ideas is recommended.<br />
<br />
Additionally, expansion costs are slightly higher (it's dangerous work building things in the wilderness) in out-of-town locations. Here is a breakdown of what you can expect to pay, versus the normal expansion costs:<br />
<br />
{| border="1"<br />
|+WILDERNESS ROOM EXPANSIONS<br />
|-<br />
!Total Rooms<br />
!Restring Tokens Required<br />
!Gold<br />
|-<br />
|1<br />
|N/A<br />
|N/A<br />
|-<br />
|2<br />
|1<br />
|750<br />
|-<br />
|3<br />
|2<br />
|750<br />
|-<br />
|4<br />
|4<br />
|750<br />
|-<br />
|5<br />
|8<br />
|750<br />
|-<br />
|6<br />
|12<br />
|750<br />
|-<br />
|7+<br />
|12<br />
|750 x (RoomCnt - 5)<br />
|}<br />
<br />
While the ammenities available to private player houses are, as mentioned, not allowed for Plan B locations, certain exemptions may apply if it fits the house's feel decently enough. A player should talk to Lilly if they really want something that they feel would greatly add to the Plan B house's atmosphere, and perhaps a deal can be worked out.<br />
<br />
<br />
<br />
==Applying For Housing==<br />
<br />
In a note written to Lilly, please provide the '''MINIMUM''' following information:<br />
<br />
A.) Rooms: '''Room title''' (name of the room); '''Room desc''' (main description of the room); '''Extra Descs''' (any "extra" descriptions you want in the room, by way of specific keyword lookup). If you want color, add it in your note, otherwise I'm going to just go with the Cleft's basic color scheme (which is normal grey room descs and dark cyan room titles).<br />
<br />
<br />
B.) Room Linkage: If this is your first room, please include the '''exit room''' (the room in town that the exit to your house leads to). For additional rooms, include the '''direction''' they are linked from room to room. If you are creating secret exits or entrances by way of a mobprog action, include the above information while describing your hidden exit request (see below).<br />
<br />
<br />
C.) Furniture/Objects/Fountains: '''Short description''' (the name of the object) and '''long description''' (what it says when the item is in the room). You may also request '''extra descriptions''' in the same way as a Room's extra descriptions, but if you do not include any, I will assume them to be unwanted. Please also include the '''room''' that you want it placed in.<br />
<br />
<br />
D.) House Pets: '''Short description''' and '''long description''', as well as a '''physical description''' (what the mob looks like). If you want your pets to do anything via a mobprog, please be as detailed as possible with what you want them to do, how to react, and etc. There's very little I can't do, but the clearer you are in your request, the easier of a time I'll have programming them accurately. Please also include the '''room''' that you want it placed in.<br />
<br />
<br />
E.) Hidden/Special Exits/Entrances: If an activateable object is involved, please include the '''short description''' and '''long description''' (unless it is meant to be hidden). Extra descriptions are not required, but recommended if the device is meant to work as a hidden or secret exit (perhaps, for example, to give clues on its useage). Please also include the '''room''' that you want it placed in, as well as the '''linked room''' that it is meant to lead into.<br />
<br />
<br />
F.) Extras: Anything from the Housing Shop should be considered witht he above guidelines, as they apply toward anything not covered in acknowledgements A through E. If you're not sure if your point is getting across in a note you post to me, think of it this way: the more information you include, the better off we'll BOTH be.<br />
<br />
<br />
These instructions do '''not''' have to be followed to the letter; if your note skips a step or two, but is highly descriptive, I will likely be able to catch your drift and build accordingly without any interruption or irritation on my part at missing information. On the other hand, telling me 'a breadbox in the kitchen' is not explaining to me what you want. Do you want it called 'a breadbox in the kitchen'? What about the long desc? Have some consideration for what information I need to put into the item as I am creating it; all descriptions are required by the PLAYER, not for the admin to guess or have a free-for-all with. If glaring information is left out and I'm already not feeling helpful, I may leave you with a half-assed item and state that "this is what your note requested". So get your pen out and be descriptive!<br />
<br />
<br />
<br />
<br />
<br />
==Multi-Character Housing==<br />
<br />
In the interest of saving effort, time, and (perhaps most importantly) Vnums, I have decided to allow multi-character player housing. What this means is that a Player House can legally have more than one character is its "owner," but only under the following pretenses and stipulations:<br />
<br />
<br />
1.) The normal rules of a player house still apply for any moving-in character: level 50, 100 hours on any character the player owns, etc.<br />
<br />
2.) The "moving-in" character does not have to be an alt of the house-owner's player (meaning multiple players can live in one player's character's house), but '''all''' purchases that were made by the initial house-owner must also be made by the character that is moving in. This includes initial plot price (including Imm token/3 Restrings), price for every room added on since the first, and all current objects/ammenities that reside in the house.<br />
<br />
3.) Aside from this "repurchasing" cost mentioned above, a flat additional fee of 2000 gold will be charged to each character wanting to move into an already-owner player house.<br />
<br />
4.) These fees '''must''' be paid by the character intended to move in. No transfer of gold (token transferral between alts is okay, as always) between alts is allowed; if the character can't afford it, they can't move in. Plain and simple. In addition (and while I condone the compassionate notion of players helping each other out), moving-in characters will be required to pay for at least '''HALF''' of the expense of moving in out of their own pocket, including restrings. This is to prevent one super-wealthy character from amassing tons of gold and paving the way for everybody and their cousins to move into their house at little or no cost to the moving-in characters themselves. Sorry guys, but we can't have the top 1% carrying everyone on their backs; that's not really fair for the rest who do it themselves and have actually worked for what they have attained.<br />
<br />
5.) Once a player home is owned by multiple characters, additional add-ons and purchases must be made for EACH MEMBER OF THE HOUSE; the catch to multiple people living in one house is that each character is still paying for everything they get to use. Essentially, every character is still paying for their own house and living accommodations, they are simply sharing the vnums. For example, if a house had 3 rooms and someone wanted a fourth, and there were two people living in the house, each member of the house would have to pay 4 tokens and 500 gold, for a total of 8 tokens and 1000 gold. If any members of the house cannot pay, no upgrades will be made.<br />
<br />
<br />
If there is a character that would like to begin the process of moving into an already-owned player house, they should contact Lilly so that the procedure can be discussed. Obviously, the decision for a second character to move into an owned player house must be mutually-agreed-upon.<br />
<br />
<br />
<br />
<br />
<br />
==Character Housing Fund Accounts==<br />
<br />
<br />
As a personal favor to players, I am willing to keep a database for characters who wish to deposit money and restring/immortal tokens into a "Housing Account" toward the use of purchasing Player Housing items for that character. This frees up time otherwise spent idling while at level 100, trying to decide on what to purchase before one can remort, or having to wait for an Immortal to make the transaction, etc. With this, a player can simply drop off excess money and tokens to me (Lilly), and I will make a note for the character in my database with the added funding. Thus, they are free to continue playing without having to worry about where the money does or doesn't go.<br />
<br />
<br />
Two small notes:<br />
<br />
1.) Monetary balances will be kept track of in amounts of GOLD only, for the sake of ease for myself. If you have heaps of silver to lay on me, this is fine, but know that I will round whatever you give me down to the nearest whole gold piece.<br />
<br />
2.) Once you have added gold and/or tokens to this House Funding Account, it is there PERMANENTLY until used for player housing purchases. There will be no returning of these coins/tokens to the character at any time, for any reason, once I have received your deposit. '''The <u>ONLY EXCEPTION</u> to this rule is in the instance of players purchasing their own [[Custom_Item_Creation|custom-made]] items from their own shop; I will reimburse players for the amount from their account toward the cost of a [[Custom Item Creation|custom-made]] item, as long as they were the character that made the item.'''<br />
<br />
<br />
If you wish to know your current monetary/token balance, simply ask, either while I'm online or in a note, and I'll be happy to look it up for you.<br />
<br />
<br />
<br />
<br />
<br />
==Final Note==<br />
<br />
Please have patience with me after you have submitted a Player Housing request. There's a few things I would like people to consider, on my behalf, after you've made your request:<br />
<br />
1.) I'm one person, and we have a lot of players. Normally I'm not swamped, but there may be a queue, and I may not be able to get to your request on the day it is given.<br />
<br />
2.) I'm not just the Player Housing admin. I'm also the head of RP, I'm a builder, I like to play the game as a mortal from time to time, and above all this, I have an involving home life outside the Cleft. Again, there may be things that prevent me from getting to your request in a timely manner, but rest assured, as long as you have posted your note to me, I do know about it, and I will get to it.<br />
<br />
3.) Constantly reminding me of your request is not going to get it done any faster. I'm well aware that you have paid. I'm well aware that you haven't gotten your description in yet. If I'm around and I'm not working on your Housing Request, there's an extremely-likely chance that I'm working on something else at the time that, for whatever reason, is taking a higher priority at the minute.<br />
<br />
4.) I took this position willingly. If two or three days seems like too long to wait for something, know that I could abandon this project at any time and players could go back to simply waiting "until one of the Imms can get around to it" again.<br />
<br />
<br />
In short, please be patient once you've sent your note. I haven't forgotten about you, and it WILL get done. Pressuring me about it will put your place in the queue at risk, and I may delay it intentionally just to be a hag about it. ^_^</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Apr_2018:Booster_Tower&diff=2184Apr 2018:Booster Tower2018-12-14T13:40:53Z<p>Pascal: </p>
<hr />
<div>Area of the Month for April 2018 is [[Booster_Tower|Booster Tower]]!<br />
<br />
A template format for your review is below; click 'edit' at the top of the page, copy-pasta from the <nowiki>----</nowiki> to the next <nowiki>----</nowiki>, and fill in the gaps!<br />
<br />
('''''Yes,''''' a wiki account is required to edit the page and therefore post your review, but take heart: The wiki is hosted by the Cleft itself, not a third party!<br />
<br />
**Post-reviews, Booster Tower was altered too significantly to note every change here, thanks. 9/27/2018<br />
<br />
<br />
----<br />
<br />
'''Player: You!(Class/Level)'''<br />
<br />
'''Review Date(s): '''<br />
<br />
<br />
'''Descriptions: X/10'''<br />
<br />
How does the area's room descriptions(descs) work for you? Do they give you a good idea of the area? Do things that stand out in the desc and NEED explanation GET that, either from flavor text(extra-descs) or NPCs in the room or anything?<br />
<br />
What about mobiles(mobs) and their descriptions? Can you get a decent mental image of who or what this NPC/monster is? Do they respond when you talk or interact with them?<br />
<br />
Some areas have interact-able objects like fountains. Do they stack up well also?<br />
<br />
<br />
'''Balance: X/10 (OR N/A)'''<br />
<br />
(NOTE: combat will be most accurately gauged when your character is in the area's suggested level range.)<br />
<br />
If this area has combat, how does it feel? Does anything jump as horribly overpowered and impossible to deal with? What about the flipside, anything far too easy to beat? <br />
<br />
Are purchased or rewarded items at the appropriate strength levels? Is the effort required to obtain rewarded items reflected in their usefulness (or uniqueness and fancifulness)<br />
<br />
<br />
'''Attractions: X/10'''<br />
<br />
Why would you suggest someone come to this area?<br />
Is it just a good place to grind experience(lots of mobs)?<br />
Does the area provide a chunk of good gold and loot?<br />
<br />
What about the quests? Does this area's quests feel properly done, or is there some part of it that you feel needs work?<br />
<br />
For towns, are the shops good? Any other non-combative attraction for the area?<br />
<br />
<br />
'''Connections: X/10 '''<br />
<br />
How easily and well does this area connect to its nearby areas?<br />
Does it make sense thematically to be connected to the areas it is?<br />
<br />
<br />
'''Personal'''<br />
<br />
Any comments you'd like to make that you don't feel apply to the other sections can go here!<br />
<br />
<br />
<br />
----<br />
<br />
'''Player: Scribble(Knight/16)''' - TOKEN'D<br />
<br />
'''Review Date(s): 4/1/2018'''<br />
<br />
<br />
'''Descriptions: 4/10'''<br />
<br />
The descriptions of the mobs are short and sweet, which is fine. They describe them rather well, but just somewhat unimaginatively. The Snifits all share a description except for one, describing them as Booster's "three main toadies" even though there is a fourth. This fourth one is also a shopkeeper, but looking at him still reveals his condition as if he were killable.<br />
<br />
The room descriptions are easy to ignore and very short. A few are even one sentence. The room you are sent to after taking the trip there refers to the event that sent you there, even though it's possible to leave from this room and then go back through it normally, obviously not having arrived there the same way as you did initially. There are very few things in the room descriptions to look at and nothing in them is ever important, every important interactable object and mob being plainly visible in the room.<br />
<br />
While reading the descriptions does help mildly paint a picture of the area, the tower is more or less a free for all killing spree zone without much to look at. The only location within this area that is actually interesting to read is the Marrymore Province, but it lacks extra descriptions. On that note, extra descriptions are highly lacking and the ones that *do* exist do not add much more to the area.<br />
<br />
This is somewhat an important note as, being a very popular, easily accessible area that nearly every newbie will visit, it does not help adjust them to the fact that reading room descriptions is typically very important in the Cleft. Though, arguably, completing the quests would still be very hard to do without reading the descriptions of the mobs involved.<br />
<br />
<br />
'''Balance: 8/10'''<br />
<br />
The balance here is good, in regards to mobs. There are large numbers of killable mobs all around the tower, ranging from 15 to 19. All of the named mobs, with sparse few exceptions, are killable and much higher level, however they are only so much more difficult than the regular mobs, except for a few (the Apprentice for example is rather tough). My character is perhaps slightly more well geared than your typical newbie, though these mobs will be harder for some classes than for others, as well. At level 17 (I leveled while writing this) I'm able to kill the level 25 mobs here, as long as I'm paying attention. For a lower level area, perhaps this is okay. The trash mobs are of varying difficulty and introduce some new status effects to new players, which is important, though annoying. <br />
<br />
For instance, I've just been not killing Orb Users because I can't re-equip my shield after using shield slam due to being blinded. This is just annoying and not really a huge issue. Bob-Ombs are probably the weakest enemies, but will explode for no experience if not killed quickly, which is a neat mechanic, teaching new players that not all fights will be so cut and dry.<br />
<br />
The items available here are decently balanced, though the level requirement for certain quest rewards is worth some discussion, mentioned below. The actual strength of these items is probably fine.<br />
<br />
<br />
'''Attractions: 7/10'''<br />
<br />
Booster Tower is obviously a hotspot for leveling and it's suggested quite frequently already. Its location is incredibly convenient, much closer to Truce than other similar leveled areas, and a useful spot for much longer than others. It's a good leveling spot for first life characters and newbies from its starting level (depending on the skill and class of the player, possibly earlier), though it tends to lose its steam quite a few levels before its suggested ending level range.<br />
<br />
There are useful pieces of gear, here, from quests or otherwise, that are typical standard fare for your general player. Some of the quest rewards are not useable until the very last level of the range of the tower. Even for a first life character, the quests are not difficult to complete before level 25, even *far* before 25, potentially teaching newbies the hard way that items will poof from your inventory if they are 10 levels out of reach. By the time you can actually use them, you probably won't even be in Booster Tower anymore.<br />
<br />
The "main" quest (the one with the most steps) is not too hard to follow and figure out, although considering its main mechanic is giving items to NPCs, it's unfortunate that some of the NPCs may keep these quest items when they are the incorrect recipient. There is inconsistency here, as some NPCs WILL give back wrong items and others will not. It's not clear if this is intentional, but if so, it's not really a great sort of 'difficulty modifier' in my opinion, and moreso just annoying.<br />
<br />
It's also worth questioning if it's worth preserving the situation within this quest where the final turn in item is a potentially useful item for certain classes to keep, while the final reward would be bad for those classes. It's possible to do the quest over again, but that would insist that if the final reward is not good for your class, you basically just do it again, while other people would not have to. I'm not sure this is a great mechanic, personally.<br />
<br />
One of the quests can be cheesed (I won't explain how publicly!) really easily, while another requires an item that requires level 20 to wear, but the reward requires level 25 to use. The item also doesn't *necessarily* require combat to acquire, so the jump in level requirements is potentially super annoying. Basically if you complete it as soon as you are able, you'll still have an unusable item in your inventory for five levels before you even know if it's worth the space to keep it.<br />
<br />
These level requirements for the quest rewards is the only thing I would really think to take a second look at, if only for the fact that Booster Tower - despite being level 16-25 - becomes less useful and will typically be finished significantly before its final level of 25, even by newbies, as has been demonstrated recently.<br />
<br />
<br />
'''Connections: 5/10 '''<br />
<br />
This is one of the most easily accessible, mob-dense areas for low level leveling in the game for a Truce start. Thematically, Booster Tower is questionable in its location. It's just a short walk from Truce, between there and Rocket Town. The entrance to the tower itself implies the tower is somewhat unpleasant looking, saying that the door has been broken down. For an area openly displayed between two neat and orderly towns, this seems like something that may be of interest to be addressed by the authorities. Maybe it's mentioned and I just haven't seen it.<br />
<br />
<br />
<br />
----<br />
'''Player:''' Aludra(Wizard/8) -- Token'd<br />
<br />
'''Review Date(s)''': 04/06/2018<br />
<br />
<br />
'''Descriptions''': 5/10<br />
<br />
The area itself is fairly decent. Some rooms have much shorter descriptions than others, but the environment is rather same-y all in all. Especially in the source material. There are only so many ways to say 'big ugly marble chessboard room.' I wouldn't mind seeing some colour pops though, just to highlight some of the more interesting things. There aren't really any extra descriptions of note other than the TV near the top. Cute, but not inspiring.<br />
<br />
Most of the mobs have strange formatting and linebreaks. Snifit 1 for example:<br />
<br />
He wears a grey coat over his whole body, a black belt, and a black gas <br />
mask covering his face. He is one of Booster's three main toadies and loves<br />
to catch beetles and eat cake. <br />
<br />
And, of course, a Spookum: <br />
<br />
Spookums are the same height and wear the same mask as Snifits, but their<br />
rank is lower and their robes are blue rather than grey. They came to<br />
become Snifits under Booster's training, but he only wants four. <br />
<br />
They all seem to be written under a very short linewrap. I'm not going to paste every single mob description, but there are a lot of them with this issue.<br />
<br />
Other than that, they're all nice and concise and give a good idea of what you're dealing with.<br />
<br />
As for area objects, such as the toy chest and therein, these objects suffer the same linewrap issue. One of the trains are barely described at all. Player-ownable objects (such as the balloons) have equally lackluster notes. Some colour pops would be great there too.<br />
<br />
All in all, the writing is decent, but it's lacking in content. Jazz it up!<br />
<br />
'''Balance''': 7/10 (OR N/A)<br />
<br />
The chain chomps are probably the most difficult thing here to fight. Disproportionately so, given their relative level.<br />
<br />
Fireballs are definitely the weakest, and their level/xp are true to that. Would be neat if they were more in line with the rest of the area.<br />
<br />
Second to fireballs, bombs are definitely probably the weakest. I just wish they didn't cease to give you XP if they delete themselves via explosion. If they survived that with 1hp, I'd be a lot happier. <br />
<br />
<br />
I wish the rewards were more consistently leveled though. Equipment and items you can get here range from 15 to 45. By level 25, there are definitely way better places to be and much better items to use. At least the level 45 item isn't terrible. It's very easy to lose track of though, especially at a lower level where it will disappear and you'll forget about it entirely.<br />
<br />
<br />
'''Attractions''': 7/10<br />
<br />
There's basically no reason not to come to this area if you're starting out on the Truce side. It's easily located, it's packed to the gills with things to kills. The money drops aren't too bad for the level. There are plenty of little hidden treasures you can acquire if you know what to do. And, most importantly, you can do the beetle hunting minigame and rack up all kinds of dosh if you're bored.<br />
<br />
The main questline here is pretty slick. It takes a little bit of trial and error, but once you get rolling, it's hard to stop!<br />
<br />
There are three shops. None of which have any weapons or armor, but you can get some useful goodies here, if you know where to use them!<br />
<br />
<br />
'''Connections''': 10/10<br />
<br />
It connects Truce, Rocket Town and Rabite forest. Or, I'm assuming. I've never found the key to the locked back door. But I'm assuming! If the door does go where I think it was, it's a quick trip through Booster's Tower to get to Neko's Cabin, which backdoors into Guardia Castle. Pretty handy shortcut, if true. But where's the key? This might be a Thief Only scenario.<br />
<br />
<br />
'''Personal'''<br />
<br />
All in all, this area is a great springboard into the teen-levels, and further adventure. At least one of the rewards is good for all levels. I just wish it were more visual.<br />
----<br />
<br />
<br />
'''Player: Kaze(Warrior/10ish, Theif 10-15)'''<br />
<br />
'''Review Date(s): April 1st for the Warrior, April 15th for the Thief'''<br />
<br />
<br />
'''Descriptions: 7/10'''<br />
<br />
I like the descriptions as a rule. It's good. Many of the rooms are pretty bland. One common issue is that the names are the primary way to get a feel for relative height short of mapping, not the descriptions.<br />
<br />
The rooms that are noteworthy locations are pretty well described. That includes the entryway, Thomp's room, Booster's room, and Marymore... Dodo, etc. The knifey dude is pretty much the only interesting feature of his room.<br />
<br />
Most of the puzzles are in the descriptions, fair dinkum. This is good. Some level of hand holding is appropriate such an early stage, even, so the clarity is welcome.<br />
<br />
Mobs are pretty descriptive and have a jovial feel. None stood out as particularly bad, but a few were especially good. Valentina's rich trailer-trash vibe was readily apparent. The train's animation played in my head.<br />
<br />
'''Balance: 9/10 (OR N/A)'''<br />
<br />
Fire vulnerability is NASTY in the tower. <br />
<br />
The Bob-ombs seem overpowered for their level. You need DPS to drop them. The boom is devastating or deadly at the low end of the level. (If you have the HP to survive, I suspect they are much easier. Warrior handled them much lower than thief, say) Still, if you ''have'' enough, they are otherwise a bit easy. They are pretty binary that way. Going into the tower at level, I'd recommend most steer clear. On your way out, waste them for the exp.<br />
<br />
Orb users can also be deadly, especially to the fire vulnerable, but their tricks mostly seem challenging to me, not unfair. They blind and hit hard, yet are a bit fragile. I think they're well balanced for level.<br />
<br />
Spookums are pretty fair, given they act as a pretty solid entry requirement. Must be this big to enter. They are pretty much average, Maybe a touch weak, but given their company, that's far from a bad thing.<br />
<br />
Chomps are tough little cookies at level. Got to use dirty tricks or resources to fight them until about mid level. They are fairly easy to avoid and, frankly, used quite well. <br />
<br />
The bosses are a bit of a ramp, as expected and desired. The only one that really seems out of range is Val. Especially if you have the wrong vulnerabilities, she's realy good at smacking a low level character around. It generally wise to come back to finish her off.<br />
<br />
Item rewards range from about what you'd purchase to nice for the level. Clown Gloves are really nice for their level. Otherwise things tend to be a bit light.<br />
<br />
All in all, this is pretty much my standard for combat balance. It's one of the best zones, that way.<br />
<br />
<br />
'''Attractions: 9/10'''<br />
<br />
It's got fun and amusing little secrets. It's got challenging MOBs. It's got some decent EQ. If you like MUDs, it's for you. <br />
<br />
Loot isn't much of a draw, though the shops are. Gold is decent.<br />
<br />
Quests are average. They mostly aren't hard. The Chain Chomp thing is pretty obscure. The Sniffits are humerous but the rewards are pretty pointless. Marymore is cool looking but one of its quest elements is tricky to even spot, much less solve. <br />
<br />
A few more scattered hints are in order. Given the nature of the area, that's probably best solved in other zones, predominantly, but some on site would be good, too.<br />
<br />
<br />
'''Connections: 7/10 '''<br />
<br />
''Why'' it's where it is isn't clear, but it does link to its surroundings in a rational way. Really ought to have a bit more description on the road, though. A tower that big would be visible from quite a ways off.<br />
<br />
<br />
'''Personal'''<br />
<br />
It's my favorite low-level area. <br />
<br />
A clever way across the fireball floor without an encounter would be welcome, as would some more flavor in the interstitial floors.<br />
<br />
<br />
<br />
----<br />
<br />
'''Kolem (Playing as Belle, L. 8-13 Moogle Geomancer, with various others; also Paisley, L~10 thief)'''<br />
<br />
'''Review Date(s): 4/26/2918'''<br />
<br />
As is standard with my reviews, all sections begin with five points. Consistent positives or excellent examples gain points; consistent negatives lose points or half points. Here we go!<br />
<br />
<br />
'''Descriptions: 5/10'''<br />
<br />
Oh, Booster tower. You hold a special place in my heart, but you show your age in a lotta places. One of them is the near-dearth of extra look descriptions--the only ones there are for interactables, as well as a single T.V. On the bright side, all monsters in the tower respond to talking, and spookums and snifits aside, seem to be desced decently. I was gonna ding this area half a point for lack of extra descriptions, but it doesn't really IMPEDE the player--it just feels like a missed opportunity, especially given the bonkers nature of the source material. I'll give it functional marks, but this is an area for improvement.<br />
<br />
<br />
'''Balance: 5/10'''<br />
<br />
This is a hard one, and I feel like it's one of Booster Tower's high points--and low points. The real problem I have with the zone is that, outside of the boss enemies and quest items, there aren't any real 'drops' to speak of in the tower. Spookums, Bob-ombs, Orb Users, Chain Chomps, and Remo Cons don't appear to have any drops whatsoever, and the boss rewards are either high-end of the range or storebought at the very lowest end of the scale (as is the case with Valentia's drops). <br />
<br />
On the other hand, I have nothing but praises to sing ABOUT those mobs. Booster Tower's mobs--the ones above, before we get to the bosses--all have interesting, engaging combat tricks. Analyze reveals that chain chomps have a random major weapon resistance, making melee classes have to think and plan, while Bob-Ombs will severely punish, say, a caster who bungles a few spells (this happened to me more than once). Orb users introduce low level blind and fire attacks into the mix, while Remo Cons inflict the Curse ailment, which can lead to real problems. Coupled with the levels you might attempt the tower being the introduction to the necro mechanics, these monsters are incredible teaching moments. Which leads us to...<br />
<br />
The bosses. They can and WILL thrash players who are much too low level to challenge them, with powerful attacks. One sore point is the Apprentice miniboss, who can come off as a nasty surprise the first time you encounter them, and is probably single handedly responsible for most of the new player deaths in the tower. Fireballs are also fairly obnoxious, but much less challenging than just about everybody else in the zone. Some sort of trick mechanic to switch them 'off' for a bit might be cool, similar to the trick for the chain chomps and spookum at the doorway. Maybe a minor in-room puzzle? Booster can call for help, and Valentia has powerful spells for the level. <br />
<br />
Another sore spot is the items--not just the lack thereof from the main common monsters, but the boss drops, as well, and those items gleaned through quests and mini-quests. They're all over the scale, swinging wildly from cheap but usable to high level and very useful, with levels that don't really quite suit their placement. The Balloons item, wands, and rod in particular in this zone are all handy to have, but have caveats--whether they be rot-death, high level, or simply hidden in a multi-level quest with a slightly obscure (but fun!) beginning. I kinda wish it was possible to expand the entry point to the quest, just because I enjoy it personally.<br />
<br />
All in all: Plus one full point for dynamic, interesting monsters that have multiple approaches to fights, minus one half for a lack of drops, and minus another half for the swinginess of item level and placement--it's items that hold this zone back, and that's a pity, because the combats here are genuinely a blast. (Hah!)<br />
<br />
<br />
'''Attractions: 7/10'''<br />
<br />
Hmm. While Booster Tower has solid experience payouts, the treasures--once you know what is here--are pretty useful, even though their levels are skewed. Additionally, there's at least one major item for a tie in quest later. I wish there were more to recommend here, especially in Marrymore--it's just big enough and themed enough with enough facilities to suggest expanding it to a mini-town, like Monstro Town or Medina. It'd really add some zing to the tower! There are also some mini-quests available in other areas that tie here, and a little lateral thinking can net you an nice piece of equipment. I can award one point for that--the distinctive items that are here are pretty fun, but I wish there was more reward for the lower end challenges here. See the Suggestions section for more. <br />
<br />
Additionally, the Beetle-catching minigame--and the hidden quest given by it--is really fun, but as others have pointed out, the mobs in the tower don't return items. I'll award another half point to the beetle game, and I wish there was more to do with it. There's also a minigame miniboss, which is always nice to see! I'll award it another point for that.<br />
<br />
<br />
'''Connections: 5/10 '''<br />
<br />
Booster tower itself has been worked on, off and on, by different builders for several years. This sorta patchwork addition is fine, but the surrounding environments--truce and Rocket town--refer to it only sparsely. It might be nice if it being obnoxious and visible played into more areas.<br />
<br />
Ultimately, it only has two exits, and one of them is locked by default. Which is... ehhhn. I wish there was more to Marrymore, and I wish there were more connections to external zones--it feels like the sort of place a Cannon Travel guy would totally make an installation on a balcony, or something. <br />
<br />
Five points for a functional, easy connection to one of the starting towns, but it could always stand to be improved.<br />
<br />
'''Personal'''<br />
<br />
Woof. What do I even say here? Booster's tower is practically a fixture of my time in the cleft, and it really sold me on the kind of lateral-thinking fighting on your feet that comes more into play as you fight later monsters. I love the flavor of the enemies here, but the tower itself could use a lot of touch ups. <br />
<br />
FINAL AVERAGE: Out of four categories, average score is '''5.5'''.<br />
<br />
SUGGESTIONS FOR IMPROVEMENT:<br />
<br />
*Rebalance item levels and flags and grant minor loot drops to the lower end monsters. One suggestion that sticks out in my mind is a hunk of Cosmo Brimstone as an uncommon drop from bob-ombs, regardless of if they explode or not--one gold treasures are decent enough for the level, and it would reward players with crafting components that they could feasibly use to start poking the crafting shops. It would also be thematically consistent with the bob-omb recipe sold in cosmo canyon.<br />
<br />
*Touch up room, mob, and extra descriptions. For being such a gaudy place, Booster Tower uses criminally little color--the portraits are begging for ascii art or at least extra descriptions, along with loads of other spots it'd be easy to add more un-style.<br />
<br />
*Expand the beetle minigame! Yes this is silly and dumb and unnecessary but I love it, and I wish more beetle-based enemies yielded special rewards / there were more variants of beetle / a beetle box event item. Shush don't judge me.<br />
<br />
*Add additional resources to Marrymore. It has a fountain and even benches--expanding it into a minitown would reward adventurous players, and would be a great spot for 'toys' and the like to be sold in the future.<br />
<br />
*Give more external clues about the way to bypass the guard / get various prizes / bypass the chomps with the use of a logically fitting item.<br />
<br />
<br />
----<br />
<br />
<br />
[[Category:Area of the Month]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=September_2018:_Safari_Zone&diff=2183September 2018: Safari Zone2018-12-14T13:38:55Z<p>Pascal: </p>
<hr />
<div>Area of the Month for September 2018 is the [[Safari_Zone|Safari Zone]]!<br />
<br />
A template format for your review is below; click 'edit' at the top of the page, copy-pasta from the <nowiki>----</nowiki> to the next <nowiki>----</nowiki>, and fill in the gaps!<br />
<br />
('''''Yes,''''' a wiki account is required to edit the page and therefore post your review, but take heart: The wiki is hosted by the Cleft itself, not a third party!<br />
<br />
<br />
----<br />
<br />
'''Player: You!(Class/Level)'''<br />
<br />
'''Review Date(s): '''<br />
<br />
<br />
'''Descriptions: X/10'''<br />
<br />
How does the area's room descriptions(descs) work for you? Do they give you a good idea of the area? Do things that stand out in the desc and NEED explanation GET that, either from flavor text(extra-descs) or NPCs in the room or anything?<br />
<br />
What about mobiles(mobs) and their descriptions? Can you get a decent mental image of who or what this NPC/monster is? Do they respond when you talk or interact with them?<br />
<br />
Some areas have interact-able objects like fountains. Do they stack up well also?<br />
<br />
<br />
'''Balance: X/10 (OR N/A)'''<br />
<br />
(NOTE: combat will be most accurately gauged when your character is in the area's suggested level range.)<br />
<br />
If this area has combat, how does it feel? Does anything jump as horribly overpowered and impossible to deal with? What about the flipside, anything far too easy to beat? <br />
<br />
Are purchased or rewarded items at the appropriate strength levels? Is the effort required to obtain rewarded items reflected in their usefulness (or uniqueness and fancifulness)<br />
<br />
<br />
'''Attractions: X/10'''<br />
<br />
Why would you suggest someone come to this area?<br />
Is it just a good place to grind experience(lots of mobs)?<br />
Does the area provide a chunk of good gold and loot?<br />
<br />
What about the quests? Does this area's quests feel properly done, or is there some part of it that you feel needs work?<br />
<br />
For towns, are the shops good? Any other non-combative attraction for the area?<br />
<br />
<br />
'''Connections: X/10 '''<br />
<br />
How easily and well does this area connect to its nearby areas?<br />
Does it make sense thematically to be connected to the areas it is?<br />
<br />
<br />
'''Personal'''<br />
<br />
Any comments you'd like to make that you don't feel apply to the other sections can go here!<br />
<br />
<br />
<br />
----<br />
<br />
'''Player:''' Emouse (Dollmage, L100, ~5 remorts) --TOKEN'D<br />
<br />
'''Review Dates:''' 9/7/2018-9/8/2018<br />
<br />
'''Descriptions: 5/10'''<br />
<br />
The mobs in the Safari Zone are good, but not great: The lookdescs and combat progs are effective descriptions and show some personality, but outside of that the mobs are kinda lifeless. None of the pokemon have talkprogs to demonstrate non-violent interaction, there's no text while idle or interaction between pokemon in the wild, and Todd's involvement for his quest is... minimal. And easily sequence broken - you can walk straight to the Fearow and skip the rest of his requests. Of which I remember more than the one he currently makes, so I'm not sure if it's even operating as intended. You'd also think his enthusiasm would lead him to babble a lot about the pokemon in the region if prompted when following, but that's pure radio silence as well...<br />
<br />
Gotta say, the graffiti adds a lot of personality to the room descriptions. The river/pond region has a lot of little bonus descriptions that add life to the area... but the rest of the zone doesn't. The room descriptions in the caves and forest area are good, but there's little further details on items of interest from trying to 'look' at them, aside from one or two quest-related tidbits. Complete lack of detail on the Dustox colony in the forest and the various stalactites and water pools in the cave is saddening. It feels like the one N W W from the entrance of the caves would even be a fountain...?<br />
<br />
'''Balance: 7/10?'''; approximated by having level 30 pet solo battles<br />
<br />
The mostly-questing-prices Level 30 Knight-like pet that I brought here to fight could usually win solo battles before the Anger Rating maxxed out, but took nontrivial amounts of damage in the process, even with the modestly-interesting combat progs most of them had. Except against Gyrados, which is appropriate given the level jump. RIP.<br />
<br />
In terms of drops and loot, there are some finds here that... aren't very good, but have niche uses, and the pokemon in the area drop enough cash that the 100 silver entry fee isn't a huge deterrant. However, the drops have... pretty bad sell value, and feel rare for the narrow range where it's useful. For example, I managed to clear out the forest twice without getting the Scyther equipment drop.<br />
<br />
I'm not sure how to feel about the frequency of the pokemon food dropping from everything in the area: It's such a poor food item that it can't be used to stave off hunger, but I don't know how common it should be to have it as an option to offset the anger meter mechanic for classes that aren't damage-focused, or if it should offer much side use for players that don't. Would 1 satiation/1 fullness to make it at least count as a snack for the shameless be too much?<br />
<br />
'''Attractions: 3/10'''<br />
<br />
The Safari Zone is in a weird place in terms of attractiveness. If you know enough about it already and have an aggressive enough skillset, it can be a servicable levelling spot with some niche drops available, but if you haven't figured the area out already, there's no real indication that sticking around is worth it - especially since the main attraction to the area is fighting the pokemon without being caught by the warden, when both the warden and Todd appear to discourage you from fighting them. Some more guidance that "yeah, beat 'em up but be careful" is the real point would probably make the area clearer. Perhaps Todd could drop a hint that you'll need to at least provoke pokemon to get the photos he needs and let the rest happen as it will?<br />
<br />
There are some hidden things hinted at or with requirements from other zones that are definitely worthwhile, but I don't know whether to count those as attractions for the Safari Zone, or attractions for those other zones that require you to look around further. They don't really add incentives to stay at the safari zone - just to visit briefly to get something else in an area you're already overlevelled for and might as well leave immediately afterwards. The items available are... usable, but not especially impressive outside of some distinct niches.<br />
<br />
Outside of the purely pokemon-flavored sightseeing there's not a lot here that you can't do better at elsewhere. Tonoe and Arlia aren't much further from Viorar with significantly wider options and more relevant quests...<br />
<br />
'''Connections: 2/10'''<br />
<br />
Another rough spot. The Safari Zone is entirely pokemon-based aside from references in the graffiti and a few external quest things that are hard to count as the Safari Zone specifically. But... it is specifically an animal reserve for pokemon and that's exactly what the Warden would do, so it's hard to justify further connection to the rest of the Cleft.<br />
<br />
At most, other visitors of different races/whatever as NPCs with hints or advice could be added, or adding references to external resources that the Warden would be willing to employ to try and keep the pokemon safe; hidden Monotoli-brand security cameras, for example. Still, whether the warden would have/use the resources to do this is difficult to say.<br />
<br />
The connections for Safari Zone are poor, but adding more is also difficult to justify. Hard to say what to do with this one: Probably best left as a low priority outside of a serious zone overhaul.<br />
<br />
'''Bugs/Exploits:'''<br />
<br />
Something I'm not sure is a bug - you can attack and kill Todd, the starter NPC for the only real quest in the zone. No special response or acknowledgement is given for this, and he's level 0. Should he be classified as either noattack or a player ally?<br />
<br />
'''Overall: C-'''<br />
<br />
The Safari Zone is not one of the Cleft's stronger zones. Between the mediocre attractions there and its dead-end location it's very easy to skip over or forget about entirely, though there are some neat points hidden away if you make a point of looking. Is it worth doing more than once? Well... not really. Todd doesn't even offer a mini medal for his miniquest, which is so small and simple that's even understandable. There's not much to do here aside from get into fights to level, but the zone flavor even discourages that. It looks so promising when you start out with the river and pond areas and all the graffiti descriptions, but falls apart pretty quickly once you go further and start really interacting with the area. If anyone particularly feels like revamping things, this is probably a good candidate for it.<br />
<br />
<br />
----<br />
<br />
Player: Patapon(Warrior/25) - TOKEN'D<br />
<br />
Review Date(s): 9/19/18<br />
<br />
'''Descriptions: 5/10'''<br />
<br />
Marginal typographical errors throughout the area, not bad enough to really distract too terribly. The mobs are described well, however the descs are all short and formatted inconsistently. There are almost no extra descs except for some graffiti and one random lantern that is formatted kind of crazily and seems almost cryptic and meaningful, but isn't, like most things in this area.<br />
<br />
It's not the worst I've ever seen but it's right about bare minimum for acceptable.<br />
<br />
<br />
'''Balance: 4/10'''<br />
<br />
The fights are very easy, but I am also a warrior so that might be a side effect. There are a lot of mobs to fight so it's a pretty mindless grind. The anger mechanic exists. I'm sure it's helpful but it's mostly a non-issue, it's never difficult to toss a food at a pokemon, especially since they drop all over.<br />
<br />
The random rarer pokemon are marginally harder, which makes sense.<br />
<br />
The gear attained here is entirely ignorable. There is nothing significant that better can't be found before or at the same level, some of it from vendors. Even random drops from mobs should be better than vendor gear.<br />
<br />
<br />
'''Attractions: 1/10'''<br />
<br />
I immediately lost Todd in a tree before finding the pokemon he requested. Looking around the entire place, I'm not sure it even exists. The quest ends abruptly with screen spam. It could be tidied up with some delays. The quest could also be made better by not being so terrible.<br />
<br />
There is nothing here of value or interest, except for two different unrelated things from completely different areas that you wouldn't know about just from going here.<br />
<br />
I'm giving it 1 point because pokemon themselves are an attraction. It was fun finding the different pokemon, like gyarados. However, defeating them always let me down.<br />
<br />
<br />
'''Connections: 1/10'''<br />
<br />
From a straight-forward approach, the connections here are close enough to non-existent to be statistically insignificant. However, it could easily be speculated that the Safari Zone as a wildlife preserve is controlled by the nearby Fort Walla Walla, one of the only 'law and order' type establishments in this region of Fa'diel and possibly the only ones interested in preserving wildlife. Otherwise, the "don't fight the pokemon" command doesn't make any sense. As is, there is no connection, but potential exists to tie it in much better.<br />
<br />
<br />
'''Personal'''<br />
<br />
The way to get in is not straightforward. It says you have to pay, but what he means is you have to buy a ticket. I am not the only person who did not figure out that you had to actually buy a physical ticket from the guard via typical shop mechanics. The first time I came here I couldn't figure it out literally at all and got in by sneaking through. When I came back without sneak, it took me 10 minutes to figure out. He also says you need to put away your weapons, but you actually don't, which is lame.<br />
<br />
This area has great potential. Even with the mediocre descriptions, the aesthetic is nice. Just by merit of having pokemon and being the safari zone, this area is okay. If it was anything else, I would probably say it was terrible.<br />
<br />
----<br />
<br />
[[Category:Area of the Month]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=File:KirbyPR7.jpg&diff=2146File:KirbyPR7.jpg2018-10-17T01:01:15Z<p>Pascal: Kirby hal</p>
<hr />
<div>Kirby hal</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Builder_Applications&diff=2145Builder Applications2018-10-13T17:13:51Z<p>Pascal: </p>
<hr />
<div>Builders are responsible for creating the areas that players explore in the Cleft. Before submitting an application, you should have a solid idea about the kind of area you intend to create if accepted.<br />
<br />
Due to a reduced need for builders currently, application rules have become more stringent until futher notice. Only above average applicants will be accepted.<br />
<br />
'''Please read all of the following rules before submitting an application.'''<br />
<br />
# Must have reached 100 at least once before submitting your application.<br />
# Application must be a note to ALL immortals, titled: Builder Application<br />
#* You may also email us your application. Post a titled note if you do so.<br />
# Applicant must submit a minimum of 5 room descriptions.<br />
## Descriptions must be at least 255 characters long.<br />
## Descriptions may include extra descriptions (keywords within the room description that can yield further descriptions.) Extra descriptions are encouraged and have no minimum or maximum size.<br />
# Applicant must submit a minimum of 3 object descriptions.<br />
## Must include the short description. ex. (an apple)<br />
## Must include the long description. ex. (A small red apple is seen here.)<br />
## Must include the extra/full description. (What you see when you look at it)<br />
# Applicant must submit a minimum of 3 mobile descriptions.<br />
## Full descriptions must be a minimum of 255 characters long.<br />
## Must include the short description.<br />
## Must include the long description.<br />
## Must include a response for when you TALK to the mob.<br />
#* It is up to the applicant's discretion what kinds of rooms, objects, and mobs they submit for analysis and the extent to which they fulfill these requirements. <br />
# Descriptions should be well formatted and include minimal spelling and grammatical errors.<br />
# Must include two detailed descriptions of sample quests/events that, to the best of their knowledge, will work reasonably within the code of this MUD.<br />
#* The samples do not need actual code with them.<br />
# Application must be easy to read and properly organized.<br />
<br />
*Feel free to ask questions. Asking questions will not hurt your chances at being accepted. We expect many, many questions from potential, trial, and established builders.<br />
<br />
<br />
An applicant may not necessarily be accepted even if they follow all of the guidelines. Respect the Staff's decision. We don't care if you build/code/own another MUD, you still must follow the guidelines.<br />
The level requirement is to prove your interest and dedication to the Cleft as well as ensure that you have seen a good amount of our content to understand what kind of areas and aesthetics we strive for. <br />
Applicant may also be subject to an interview with the Staff. <br />
<br />
<br />
* '''Concerning those who become Builders.'''<br />
<br />
# Your first area shall contain a maximum of 25 vnums.<br />
## 25 room vnums, 25 object vnums, 25 mobile vnums, 25 mprogs. This rule is absolute.<br />
##* This rule is in place to help ensure that areas are finished and released in a timely manner. Being able to create a good quality area with 25 vnums is a proof of concept for your ability to create larger areas.<br />
##Your first area's theme and aesthetic are your choice unless it too heavily conflicts with the Cleft's theme (which is unlikely).<br />
##Where the area is linked to the rest of the Cleft is up to the discretion of the head builder.<br />
# Your first area cannot be a city or any other specifically residential area. <br />
#* No first area can contain any shop unless authorized by a staff member.<br />
# Only higher immortals have access to mprogs (for security reasons).<br />
#* If you need an mprog in your area, ask an immortal of status ADV or higher.<br />
# Repeating room descriptions are mostly unacceptable.<br />
# Your area must be constructed, room-wise, each room fully described, within a month of start date or you shall be fired.<br />
# Fail to log on within this time period and you shall be fired.<br />
# Should a Builder quit or be fired while an area is in progress, the Staff may still use it and edit it as they see fit.<br />
# All areas are subject to revision by Staff if they do not meet our quality standards or if there is questionable or innappropriate content. If unsure, do not hesitate to ask about something before including it.<br />
# Abuse of privileges (see help rules), will not be tolerated.<br />
<br />
<br />
<br />
'''What you can expect as a builder after successfully completing your first area'''<br />
<br />
*A builder's first area is essentially their trial period.<br />
**Once you have completed your first area to acceptable standard within the time restraints and in compliance with the rules listed, you will be promoted once.<br />
**If you and your area do not comply with the rules and restraints, you will either be fired or given a second chance at the staff's discretion.<br />
*Once established as a builder there is no strict period of time within which you must complete your second and subsequent areas, but your actions, behaviors, life situations, and time active within the mud will be taken into account on whether you are demoted or not.<br />
**You can be fired at any time for grievous abuse of power.<br />
**If you disappear for a long time, it is up to the staff's discretion whether your builder character is demoted/deleted or not.<br />
*While it is entirely up to the builder what areas to create, the head builder and staff will guide and encourage building that helps fill in gaps in the Cleft. <br />
**This is obviously an unpaid position and we don't expect a hobbyist builder to dedicate their time and energy into something they are uninterested in doing, but we as the Staff have a vision for the Cleft that we hope everyone is interested in working together to achieve. <br />
**It is unlikely for an area idea to be denied unless it is an excessively bad fit for the Cleft. <br />
**All contributions are appreciated, and any area built can be worked somewhere into the Cleft, so creative freedom is quite broad. <br />
<br />
<br />
- Cooper, Head Builder</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Builder_Applications&diff=2144Builder Applications2018-10-13T16:00:19Z<p>Pascal: more strict rules and guidelines + additional information</p>
<hr />
<div>Builders are responsible for creating the areas that players explore in the Cleft. Before submitting an application, you should have a solid idea about the kind of area you intend to create if accepted.<br />
<br />
Due to a reduced need for builders currently, application rules have become more stringent until futher notice. Only above average applicants will be accepted.<br />
<br />
'''Please read all of the following rules before submitting an application.'''<br />
<br />
# Must have reached 100 at least once before submitting your application.<br />
# Application must be a note to ALL immortals, titled: Builder Application<br />
#* You may also email us your application. Post a titled note if you do so.<br />
# Applicant must submit a minimum of 5 room descriptions.<br />
## Descriptions must be at least 255 characters long.<br />
## Descriptions may include extra descriptions (keywords within the room description that can yield further descriptions.) Extra descriptions are encouraged and have no minimum or maximum size.<br />
# Applicant must submit a minimum of 3 object descriptions.<br />
## Must include the short description. ex. (an apple)<br />
## Must include the long description. ex. (A small red apple is seen here.)<br />
## Must include the extra/full description. (What you see when you look at it)<br />
# Applicant must submit a minimum of 3 mobile descriptions.<br />
## Full descriptions must be a minimum of 255 characters long.<br />
## Must include the short description.<br />
## Must include the long description.<br />
## Must include a response for when you TALK to the mob.<br />
#* It is up to the applicant's discretion what kinds of rooms, objects, and mobs they submit for analysis and the extent to which they fulfill these requirements. <br />
# Descriptions should be well formatted and include minimal spelling and grammatical errors.<br />
# Must include two detailed descriptions of sample quests/events that, to the best of their knowledge, will work reasonably within the code of this MUD.<br />
#* The samples do not need actual code with them.<br />
# Application must be easy to read and properly organized.<br />
<br />
*Feel free to ask questions. Asking questions will not hurt your chances at being accepted. We expect many, many questions from potential, trial, and established builders.<br />
<br />
<br />
An applicant may not necessarily be accepted even if they follow all of the guidelines. Respect the Staff's decision. We don't care if you build/code/own another MUD, you still must follow the guidelines.<br />
The level requirement is to prove your interest and dedication to the Cleft as well as ensure that you have seen a good amount of our content to understand what kind of areas and aesthetics we strive for. <br />
Applicant may also be subject to an interview with the Staff. <br />
<br />
<br />
* '''Concerning those who become Builders.'''<br />
<br />
# Your first area shall contain a maximum of 25 vnums.<br />
## 25 room vnums, 25 object vnums, 25 mobile vnums, 25 mprogs. This rule is absolute.<br />
##* This rule is in place to help ensure that areas are finished and released in a timely manner. Being able to create a good quality area with 25 vnums is a proof of concept for your ability to create larger areas.<br />
##Your first area's theme and aesthetic are your choice unless it too heavily conflicts with the Cleft's theme (which is unlikely).<br />
##Where the area is linked to the rest of the Cleft is up to the discretion of the head builder.<br />
# Your first area cannot be a city or any other specifically residential area. <br />
#* No first area can contain any shop unless authorized by a staff member.<br />
# Only higher immortals have access to mprogs (for security reasons).<br />
#* If you need an mprog in your area, ask an immortal of status ADV or higher.<br />
# Repeating room descriptions are mostly unacceptable.<br />
# Your area must be constructed, room-wise, each room fully described, within a month of start date or you shall be fired.<br />
# Fail to log on within this time period and you shall be fired.<br />
# Should a Builder quit or be fired while an area is in progress, the Staff may still use it and edit it as they see fit.<br />
# All areas are subject to revision by Staff if they do not meet our quality standards or if there is questionable or innappropriate content. If unsure, do not hesitate to ask about something before including it.<br />
# Abuse of privileges (see help rules), will not be tolerated.<br />
<br />
<br />
<br />
'''What you can expect as a builder after successfully completing your first area'''<br />
<br />
*A builder's first area is essentially their trial period.<br />
**Once you have completed your first area to acceptable standard within the time restraints and in compliance with the rules listed, you will be promoted once.<br />
**If you and your area do not comply with the rules and restraints, you will either be fired or given a second chance at the staff's discretion.<br />
*Once established as a builder there is no strict period of time within which you must complete your second and subsequent areas, but your actions, behaviors, life situations, and time active within the mud will be taken into account on whether you are demoted or not.<br />
**You can be fired at any time for grevious abuse of power.<br />
**If you disappear for a long time, it is up to the staff's discretion whether your builder character is demoted/deleted or not.<br />
*While it is entirely up to the builder what areas to create, the head builder and staff will guide and encourage building that helps fill in gaps in the Cleft. <br />
**This is obviously an unpaid position and we don't expect a hobbyist builder to dedicate their time and energy into something they are uninterested in doing, but we as the Staff have a vision for the Cleft that we hope everyone is interested in working together to achieve. <br />
**It is unlikely for an area idea to be denied unless it is an excessively bad fit for the Cleft. <br />
**All contributions are appreciated, and any area built can be worked somewhere into the Cleft, so creative freedom is quite broad. <br />
<br />
<br />
- Cooper, Head Builder</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2143Mprog Compendium2018-10-13T14:01:00Z<p>Pascal: /* IFCHECKS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: can only use EITHER 'or' or 'and' per ifchk.<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> <victim><br />
This command makes the victim the pet of the target. It works almost exactly like the staff command of the same name. Target and victim are arguments, and they can be any character in the world. However, mob petify will not work if victim is a player or if target already has a pet. It's probably not a great idea to petify a victim that's not in the same room as the target, even though you can within the extent of the command.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), align(#), damtype(a), hitroll(#), magroll(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2142Mprog Compendium2018-10-13T14:00:41Z<p>Pascal: /* IFCHECKS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or', 'and', and 'else'. Ex:<br />
-NOTE: can only use EITHER 'or' or 'and' per ifchk.<br />
-NOTE: 'else' can be combined with 'or' and 'and' ifchks.<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
if uses $n weapon - does $n have an object type of 'weapon' equipped?<br />
mob exitpermit yes: they may pass through.<br />
else<br />
say You need a weapon first! no: mob says You need a weapon first!<br />
endif<br />
<br />
Every if needs an endif. 'Or', 'and', and 'else' do not require additional endifs.<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> <victim><br />
This command makes the victim the pet of the target. It works almost exactly like the staff command of the same name. Target and victim are arguments, and they can be any character in the world. However, mob petify will not work if victim is a player or if target already has a pet. It's probably not a great idea to petify a victim that's not in the same room as the target, even though you can within the extent of the command.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), align(#), damtype(a), hitroll(#), magroll(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Mprog_Compendium&diff=2138Mprog Compendium2018-10-02T15:15:19Z<p>Pascal: /* IFCHECKS */</p>
<hr />
<div>[[Image:2Mprog3.jpg|right|thumb|212px|No clear results from Google images on what an Mprog looks like.]]<br />
<br />
For every entry in this database, I will attempt to explain to the fullest degree possible the various ways every mobprog command, trigger, and ifchk works in the Cleft of Dimensions. If you're just a tourist, check out some [[Mprog Compendium/Examples|examples]]<br />
<br />
===IFCHECKS===<br />
<br />
rand if rand 30 - if random number between 1 and 100 is < 30<br />
exists if exists $n - does $n exist somewhere<br />
ishere if ishere $q - is $q in this room?<br />
mobexists if mobexists fido - is there a fido mob somewhere<br />
if mobexists 1233 - is there mob vnum 1233 somewhere<br />
objexists if objexists sword - is there a sword obj somewhere<br />
if objexists 1233 - is there obj vnum 1233 somewhere<br />
mobhere if mobhere fido - is there a 'fido' mob in this room?<br />
if mobhere 1233 - is there mob vnum 1233 in this room?<br />
objhere if objhere bottle - is there a 'bottle' obj in this room?<br />
-can't see in if objhere 1233 - is there obj vnum 1233 in this room?<br />
containers<br />
isself if isself $n - evaluate equivalence between a character and the acting mob<br />
people if people > 4 - does room contain > 4 people<br />
players if players > 1 - does room contain > 1 pcs *in event obj progs the player doesn't count in if players checks<br />
mobs if mobs > 2 - does room contain > 2 mobiles<br />
clones if clones > 3 - are there > 3 mobs of $i's vnum here<br />
duplicates if duplicates $n > 3 - are there > 3 mobs of $n's vnum here<br />
order if order == 0 - is mob the first in room<br />
<br />
hour if hour > 11 - is the time > 11 o'clock<br />
Sunrise occurs at 6am (hour 6)<br />
Sunset occurs at 6pm (hour 18)<br />
day if day > 0 - is today not the first day of the week<br />
0 - Mana Holy Day<br />
1 - Luna Day <br />
2 - Salamando Day<br />
3 - Undine Day<br />
4 - Dryad Day<br />
5 - Jinn Day<br />
6 - Gnome Day<br />
sky if sky > 2 - is the sky rating > cloudy<br />
0 - dry<br />
1 - cloudless<br />
2 - cloudy<br />
3 - raining<br />
4 - lightning<br />
wind if wind > 2 - is the wind rating > breeze<br />
0 - stale<br />
1 - none<br />
2 - breeze<br />
3 - windy<br />
4 - gale<br />
sector if sector $i == 5 - sector check<br />
0 - inside 1 - city 2 - field 3 - forest <br />
4 - hills 5 - mountain 6 - swim 7 - noswim<br />
8 - unused 9 - air 10 - desert 11 - rock<br />
12 - road 13 - enter 14 - snow 15 - swamp<br />
16 - jungle 17 - ruins 18 - mount2 19 - coastal<br />
20 - developed 21 - void<br />
<br />
ispc if ispc $n - is $n a pc<br />
isnpc if isnpc $n - is $n a mobile<br />
isgood if isgood $n - is $n good<br />
isevil if isevil $n - is $n evil<br />
isneutral if isneutral $n - is $n neutral<br />
isimmort if isimmort $n - is $n immortal<br />
ischarm if ischarm $n - is $n charmed */<br />
isfollow if isfollow $n - is $n following someone<br />
isactive if isactive $n - is $n's position > SLEEPING<br />
isdelay if isdelay $i - does $i currently have a delay counter<br />
isvisible if isvisible $n - can mob see $n<br />
isfighting if isfighting $n - fighting check<br />
hastarget if hastarget $i - does $i have a valid remembered target<br />
istarget if istarget $n - is $n mob's remember target<br />
<br />
affected if affected $n blind - is $n affected by blind<br />
affected2 if affected2 $n frenzy - '''(second set of affects, see mob template for list)'''<br />
shielded if shielded $n charge - is $n shielded by charge<br />
act if act $i sentinel - is $i flagged sentinel<br />
act2 if act2 $i noattack - is $i flagged noattack<br />
off if off $i berserk - is $i flagged berserk<br />
imm if imm $i fire - is $i immune to fire <br />
vuln if vuln $i electricity - is $i vulnerable to electricity<br />
res if res $i cold - is $i resistant to cold<br />
carries if carries $n sword - does $n have a 'sword'<br />
if carries $n 1233 - does $n have obj vnum 1233<br />
wears if wears $n lantern - is $n wearing a 'lantern'<br />
if wears $n 1233 - is $n wearing obj vnum 1233<br />
upon if upon $n motorcycle - is $n riding/using as furniture a 'motorcycle<br />
if upon $n 1233 - is $n riding/using as furniture obj vnum 1233<br />
has if has $n weapon - does $n have obj of type weapon<br />
uses if uses $n armor - is $n wearing obj of type armor<br />
pos if pos $n standing - is $n standing<br />
name if name $n puff - is $n's name 'puff'<br />
clan if clan $n 'tuna' - does $n belong to clan 'tuna'<br />
race if race $n dragon - is $n of 'dragon' race<br />
class if class $n wizard - is $n's class 'wizard'<br />
subclass if subclass $n > 0 - subclass check<br />
skill if skill $n 'big boo' - does $n have the big boo skill<br />
skillchk if skillchk $n 'fire' > 90 - character's skill percentage check<br />
objtype if objtype $o scroll - is $o a scroll type obj<br />
quest if quest $n nerb1 - is quest flag nerb1 toggled for $n<br />
remort if remort $n > 1 - has $n remorted at least once?<br />
(New characters start at "if remort == 1";<br />
first remort is at "if remort == 2")<br />
brief if isbrief $n - does $n have 'brief' toggled? *only works for players<br />
<br />
vnum if vnum $i == 1233 - virtual number check<br />
room if room $i == 1233 - room virtual number<br />
roomaff if roomaff sandstorm - room affect check ('? roomaff' in editor to see valid flags)<br />
roomflag if roomflag dark - room flag check ('? room' in editor to see valid flags)<br />
align if align $n < -1000 - alignment check<br />
level if level $n < 5 - level check<br />
if level $o == 0 - works on objects too<br />
sex if sex $i == 0 - sex check<br />
0 - none<br />
1 - male<br />
2 - female<br />
innate if innate $n == 1 - innate check<br />
0 - None<br />
1 - Water<br />
2 - Moon<br />
3 - Wood<br />
4 - None (Don't use)<br />
5 - Wind<br />
6 - Earth<br />
7 - Fire<br />
size if size $n < 2 - size check<br />
0 - tiny<br />
1 - small<br />
2 - medium<br />
3 - large<br />
4 - huge<br />
5 - giant<br />
<br />
counter if counter $i >= 6 - mob counter check<br />
money if money $n > 500 - money check (in silver)<br />
objval0 if objval0 $o > 1000 - object value[] checks 0-4 (check object type in oedit for relevant variables)<br />
objval1 -for money in bribe triggers use objval0 for silver and objval1 for gold<br />
objval2<br />
objval3<br />
objval4<br />
objcost if objcost $o >= 50 - cost of the obj in silver<br />
objweight if objweight $o < 100 - weight of the obj in 1/10lbs<br />
objextra if objextra $o glow - does $o have glow<br />
objextra2 if objextra2 $o unique - is $o unique<br />
objextra3 if objextra3 $o owned - is $o owned<br />
objcond if objcond $o > 50 - object condition value check<br />
if objcond pie > 50 <br />
wenchant if wenchant $o == 10 - has $o been enchanted 10 times (weapon only)<br />
aenchant if aenchant $o == 10 - has $o been enchanted 10 times (armor only)<br />
<br />
grpsize if grpsize $n > 6 - group size check<br />
-a solo player is a group size of 0<br />
-all pets and charmies count toward group size<br />
-they don't count if they aren't in the room with the target<br />
str if str $n > 13 - strength check<br />
int if int $i < 18 - intelligence check<br />
wis if wis $q == 25 - wisdom check<br />
dex if dex $f >= 8 - dexterity check<br />
con if con $g <= 20 - constitution check<br />
hpchk if hpchk $n < 15 - hit point check<br />
hpcnt if hpcnt $i > 30 - hit point percent check<br />
mpchk if mpchk $i > 8 - mana point check<br />
mpcnt if mpcnt $i > 50 - mana percentage check<br />
mvchk if mvchk $i > 25 - movement point check<br />
drunk if drunk $n >= 5 - drunkenness check<br />
khexists if khexists $n 1234 - does mob of this vnum exist in kill history (bodycount)<br />
khcount if khcount $n 1234 > 5 - is number of mob of this vnum in kill history higher than 5<br />
<br />
IFCHKS can be used with 'or' and 'and'. Ex:<br />
-can only use one at a time per ifchk<br />
if room $i >= 500 - is the room vnum both greater than or equal to 500 and less than or equal to 1000?<br />
and room $i <= 1000 i.e. between 500 and 1000, including both 500 and 1000.<br />
<br />
if dex $n > 12 - are $n's dex AND str both greater than 12?<br />
and str $n > 12<br />
<br />
if hour >= 18 - is the hour later than 6pm or earlier than 6am?<br />
or hour <= 6 i.e. is it between 6pm and 6am, including both 6pm and 6am.<br />
*'or' must be used for this type of 'evening' check because<br />
the numbers don't circle like a real clock - it can't be both<br />
greater than 18 and less than 6.<br />
if class $n thief - is $n a thief OR a warrior?<br />
or class $n warrior<br />
<br />
===VARIABLES===<br />
<br />
There are two types of variables that are used in mobprogs. There is a limited set of variables than can be used with ifchecks, and there is a far more diverse set of variables than can be used with everything else. Additionally, there are variables outside of mobprogs that deal with items such as gender, but those are covered by the general variables listed below and are outside the scope of this document anyway. The variables listed below are in alphabetical order.<br />
<br />
====Ifcheck Variables:====<br />
$f the pet of the mob remember target<br />
$g the master of the mob remember target<br />
$i the acting mob himself<br />
$n the target of the mob<br />
$o the target object of the mob<br />
$p the secondary target object of the mob (act trigger only)*<br />
$q the mob remember target<br />
$r random character in room<br />
$t the secondary target of the mob (act trigger only)*<br />
$z the counter of the acting mob<br />
<br />
For use in event mprogs:<br />
<br />
$n is the targetted mob or player<br />
$o is the targetted object<br />
$i is the acting player<br />
$p is the actual event item being activated<br />
$y will always refer to the person using the event item<br />
(useful when the event forces other mobs)<br />
$n and $o cannot exist at the same time in an event mprog<br />
players are considered to be vnum 0 when using a 'vnum $i' check.<br />
<br />
====General Variables:====<br />
$a the numerical damage amount of the last successful Mob Damage (only works with Mob Echo)<br />
$b the race (for PCs) or shortdesc (for mobs) of the mob's remember target<br />
$B the level of the mob's remember target<br />
$e the subject pronoun of the mob's target<br />
$E the subject pronoun of the mob's secondary target*<br />
$f the name of the pet of the mob's remember target<br />
$F the short desc of the pet of the mob's remember target<br />
$g the name of the master of the mob's remember target<br />
$G the short desc of the master of the mob's remember target<br />
$i the name of the acting mob<br />
$I the short desc of the acting mob<br />
$j the subject pronoun of the acting mob (he/she/it)<br />
$J the subject pronoun of a random character<br />
$k the object pronoun of the acting mob (him/her/it)<br />
$K the object pronoun of a random character<br />
$l the possessive adjective of the acting mob (his/her/its)<br />
$L the possessive adjective of a random character<br />
$m the object pronoun of the mob's target<br />
$M the object pronoun of the mob's secondary target*<br />
$n the name of the mob's target<br />
$N the short desc of the mob's target<br />
$o the name of the mob's object target<br />
$O the short desc of the mob's object target<br />
$p the name of the mob's secondary object target*<br />
$P the short desc of the mob's secondary object target*<br />
$q the name of the mob's remember target<br />
$Q the short desc of the mob's remember target<br />
$r the name of a random character<br />
$R the short desc of a random character<br />
$s the possessive adjective of the mob's target<br />
$S the possessive adjective of the mob's secondary target*<br />
$t the name of the mob's secondary target*<br />
$T the short desc of the mob's secondary target*<br />
$X the subject pronoun of the mob remember target<br />
$Y the object pronoun of the mob remember target<br />
$z the counter of the acting mob<br />
$Z the possessive adjective of the mob remember target<br />
<br />
OR:<br />
<br />
{|<br />
! !! Name !! Short Desc !! Subject Pronoun !! Object Pronoun !! Possessive Adjective<br />
|-<br />
| || For Targetting || For Echoing || He/She/It || Him/Her/It || His/Her/Its<br />
|-<br />
|Acting Mob || $i || $I || $j || $k || $l<br />
|-<br />
|Mob's Target || $n || $N || $e || $m || $s<br />
|-<br />
|Secondary Target* || $t || $T || $E || $M || $S<br />
|-<br />
|Object Target || $o || $O<br />
|-<br />
|Secondary Object* || $p || $P<br />
|-<br />
|Random Character || $r || $R || $J || $K || $L<br />
|-<br />
|Mob Remember Target || $q || $Q || $X || $Y || $Z<br />
|-<br />
|Remember Target's Pet || $f || $F<br />
|-<br />
|Remember Target's Master|| $g || $G<br />
|}<br />
<br />
*The secondary target variables are a bit odd. Basically, they only work when a target or mob is related indirectly to the mob. For example, if Griswald opened a box and the mob had an act prog execute on that, the box would be $p. Or if Griswald parried Ami's attack and the mob had an act prog execute on that, Ami would be $t. $p and $t cannot exist at the same time.<br />
<br />
===MOB COMMANDS===<br />
<br />
The commands are grouped logically, not alphabetically. Commands that serve a similar purpose are grouped together, since I thought it would be more helpful that way. Every command has the appropriate syntax listed under it. Stuff in <brackets> denotes necessary parameters, stuff in [brackets] denotes unnecessary parameters. A synopsis of every command is listed as well. At the bottom of every entry I list examples of every command's usage. <br />
<br />
A list of examples is given for each command. Every command has up to five basic examples and a further list of advanced usages for the command. In general, I try to draw no more than one example from each area, unless a given area has two or more distinctly different advanced usages of a command. The examples can be accessed via mpdump.<br />
<br />
;ECHO:mob echo <string><br />
This command sends a text message to every player in the room. It is the basic command to output whatever you want via mobprogs. There are many more specialized versions of this command, all of which are listed below. Oftentimes echo is a better choice than having a mob say or emote something.<br />
<br />
Examples: 1362, 2206, 2553, 1161, 4715<br />
<br />
;ECHOAT:mob echoat <target> <string><br />
This command will echo a message to the specific player targetted in the room and no one else. In combination with the echoaround command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoat is useful in events such as someone being telepathed to, or if you just want to hide a certain message from other players in the room.<br />
<br />
Examples: 1072, 33, 152, 1502, 3007<br />
<br />
;ECHOAROUND:mob echoaround <target> <string><br />
This command will echo a message to every player in the room with the exception of the target. In combination with the echoat command, this can allow for messages that simulate real commands. Usually the echo command is preferable, but echoaround combined with echoat can allow for the distinction between "you" and "$n" in messages. Echoaround is generally useful when you want to hide certain messages from the target player.<br />
<br />
Examples: 1462, 4001, 4807, 3129, 4072<br />
<br />
;ASOUND:mob asound <string><br />
This command is similiar to echo. Unlike echo, however, asound will echo a message to every room that the mob's current room has an exit to - i.e., the surrounding rooms. What's interesting about asound is that it doesn't echo to the room the mob is in, only adjacent ones. It will echo through doors, but will not echo through portals or one-way exits leading INTO the mob's room.<br />
<br />
Examples: 4017, 5683, 2217, 5494, 2714<br />
<br />
;ZECHO:mob zecho <string><br />
This command is a more powerful version of echo, echoing a message to every player in the mob's current area. Staff will get a "mob echo>" in front of every zecho message, but players won't. The applications of this command are pretty straightforward, and they can easily add some flavor to your area.<br />
<br />
Examples: 1035, 1003, 182<br />
<br />
;GECHO:mob gecho <string><br />
This command is a more powerful version of zecho, echoing a message to every player in the MUD. There probably aren't that many times anybody would want to use this, but it's a powerful command and it's there. Staff will get a "mob echo>" in front of every gecho message, but players won't.<br />
<br />
Examples: 419<br />
<br />
;GOTO:mob goto <location><br />
This command transfers the mobile from the current room to another. The location parameter takes many different arguments. When given a number, goto will transfer the mob to the given room number. When given any single word, goto will transfer the mob to the first relevant mob or object in the world. An interesting fact about goto is that it stops the mob's combat during the transfer, so it acts like a localized mob peace. Also, use of the goto command can disguise a mob's death cry - shown in the examples below. Mob goto can transfer through safe or no_mob room flags and can move sentinel mobs.<br />
<br />
Examples: 4004, 2712, 3116, 1021, 5555<br><br />
Adv. Examples: 2115, 4069, 1212, 1549, 2262, 71, 4851, 1053, 187, 733<br />
<br />
;TRANSFER:mob transfer <target> [location]<br />
This command transfers the target to the given location. The location can be a room vnum or a single keyword for a given mob or object. If location is omitted, the command will transfer the target to the room the mob is in. The target can be any mob or player in the world. Mob transfer can also transfer "all," which will move all characters in the mob's room. Mob transfer can transfer through safe or no_mob room flags and move sentinel mobs.<br />
<br />
Examples: 1452, 4014, 2708, 4854, 1714<br />
<br />
;GTRANSFER:mob transfer <target> [location]<br />
This command works just like transfer, except it transfers everyone in the target's group as well as the target. However, you cannot gtransfer all. Besides that, it is entirely identical to transfer.<br />
<br />
Examples: None.<br />
<br />
;MLOAD:mob mload <vnum><br />
This command loads a mob with the chosen vnum into the same room as the acting mob. It can load mobs from any area and into any room with no restrictions. It only takes vnums as a parameter - you cannot mload specific words. While the command appears straightforward, it can be used creatively.<br />
<br />
Examples: 1206, 1453, 39, 3119, 154<br><br />
Adv. Examples: 2729, 2262, 4076, 1404, 4849, 1563, 1003<br />
<br />
;OLOAD:mob oload <vnum> [level] [R] [W]<br />
This command loads an object with the chosen vnum into the inventory of the mobile. If the item cannot be taken into inventory, it is generated on the floor. "R" will send the object to the room, and "W" will make the mob wear the object, if possible, instead of placing it in inventory. The [level] and [R] or [W] parameters are not necessary to use mob oload, but in order to load something into the room or equipped onto the mob using R or W, the level parameter has to be defined, as well. However, the function of altering the level of the loaded object is defunct, so it's typical to simply use '0 R' or '0 W' to load objects in these ways. What's great about loading objects is that they can be used as "counters" in mobprogs, illustrated in some examples below.<br />
<br />
Examples: 1475, 1360, 3126, 2381, 2127<br><br />
Adv. Examples: 2232, 178, 5670, 4818<br />
<br />
;OTRANSFER:mob otransfer <target> <location><br />
This command transfers an object to a given location. The target object can be in the room, in the mob's inventory, or part of the mob's equipment. The location parameter can be a room vnum or an argument for a mobile or object anywhere in the world. Unlike the regular transfer command, the location is mandatory. Unfortunately, no matter what the location is, the target object will always transfer to the room the location is in, never the actual character specified. NOTE: items inside containers cannot be otransfered, but ifchks can see them.<br />
<br />
Examples: 4868<br />
<br />
;PURGE:mob purge [target]<br />
This command can delete items or mobiles from the room the mob is in. It has powerful and versatile purposes. Mob purge without a parameter will purge all mobs and items in the room that lack the nopurge flag. Mob purge with a target can purge any mobile in the room or any object in the room or in the mob's inventory or equipment. Mob purge will never purge player characters. A mob can "mob purge self," but do so sparingly - it appears to be able to crash the MUD at times. When you do use "mob purge self," try to place it as close to the end of mobprogs as possible. For extra security, always place 'break' right after a mob purge self command.<br />
<br />
Examples: 53, 3149, 4829, 1581, 710<br><br />
Adv. Examples: 1005, 3123<br />
<br />
;JUNK:mob junk <item><br />
This command can destroy any item the mob has in inventory or is wearing as equipment. The <item> parameter is very versatile. You can junk all, or junk 'all something', or just junk a specific item. It works just like the get command in this regard. It also takes variables such as $o. Mob junk cannot junk items on the ground or items in a player's inventory. NOTE: items inside containers cannot be junked, but ifchks can see them.<br />
<br />
Examples: 1476, 2109, 1360, 2710, 4886<br><br />
Adv. Examples: 3146, 2216, 4015, 2387, 727, 1009, 1212, 5491, 3113<br />
<br />
;REMOVE:mob remove <target> <vnum><br />
This command removes the given object from the target's inventory or equipment. The target must be in the same room as the mob. The vnum parameter specifies the vnum of the object to be removed from the target. Mob remove will only remove one object each time it is used, even if the player is carrying multiple of that object vnum. Alternately, all can be used instead of a vnum - this will remove every object the target has. (Don't do this to players!) Removed objects are completely destroyed, not dropped to the floor or given to the mob. This means be careful when using it.<br />
<br />
Examples: 1027, 4829, 1314, 1162, 5556<br />
<br />
;FLEE:mob flee<br />
This command causes the mob to instantly run to an adjoining room. It only works if the mob is not currently fighting (simply use 'flee' for this). The mob will not flee through closed doors or into no_mob rooms, and it will not flee into the same room as it started in (via looped exits). It will cause a normal 'leaves east' type echo. The way it works is that the mob tries, six times, to run in a random direction. If at the end of those six attempts it hasn't found a valid exit, the mob does nothing. Because of this, mob flee is more likely to work in rooms with more exits than rooms with fewer exits.<br />
<br />
Examples: 1006<br />
<br />
;KILL:mob kill <target><br />
This command will force the mob to attack the target. The target parameter can be either a variable like $n or an actual name like goomba. It ignores almost all of the restrictions the regular kill command has - for example, a mob can attack a person who is already fighting someone else, or it can attack through a safe room. Here are the only restrictions: the target must be in the same room as the mob, the mob can't attack itself, and charmed mobs can't attack their masters. When your mobile absolutely must attack someone, you want to use this instead of the regular kill command.<br />
<br />
Examples: 4700, 1456, 2712, 3123<br><br />
Adv. Examples: 1514, 2352, 3014, 1060, 161, 172<br />
<br />
;ASSIST:mob assist <target><br />
This command works similarly to kill. It functions somewhat differently than the regular assist command. Mob assist will force the mob to attack whoever the target is fighting with. The target parameter can be either a variable like $n or an actual name like goomba. It does not relieve the target of fighting, it merely draws the mob into the fray. Mob assist will attack under any circumstances unless: the target isn't in the same room as the mob, the mob is trying to assist itself, the target is not fighting, or the mob is already fighting.<br />
<br />
Examples: None. This command is not mentioned in the standard mprog documentation.<br />
<br />
;HIT:mob hit <target><br />
Similar to Kill and Assist, this command causes the mob to attack the target. However, it doesn't care if the actor is already fighting -- this makes it useful for simulating special attacks.<br />
<br />
Examples: 1456<br />
<br />
;PEACE:mob peace<br />
This command stops all fighting in the same room as the mob. It works exactly like the staff command of the same name. Besides furthering the cause of pacifism, it's ideal for creating a gap in the fighting to execute commands that can't be done while fighting, then resuming the brawl. Additionally, it's a helpful command to use with inert or passive mobs.<br />
<br />
Examples: 5669, 4001, 3014, 172, 3139<br />
<br />
;SKILL:mob skill <command><br />
This command allows the mob to execute almost any skill. The given command is parsed like a regular command, except that, when this command is executed, the mob is treated as having 75% adequacy in all skills in the game. Therefore, skills that are normally forbidden to mobs can be used with the mob skill command. By using the adept and inept act2 flags, the proficiency of the mob at skills can be increased or decreased by 25%.<br />
<br />
Examples: 2511<br />
<br />
;DAMAGE:mob damage <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command directly damages the target. This will work when the mob is not in combat and will not initiate combat. The target can be any character in the same room as the mob, or it can be '''all''', which targets all characters in the room. Mob damage does a random number of hitpoints damage between min and max. Min and max are not dice, they are a flat range. Mob damage can do negative damage, which will heal the target - however, mob damage will not send the target's hp above maximum. Note that healing this way ignores zombie status, distribute, etc.<br><br />
Damtype specifies what [[damage type]] to use in respect to resistances and vulnerabilities. It can be any damage type you see with "? imm" in medit. A given mob damage can only have one given damtype.<br><br />
If you type "lethal" at the end of the command, the mob damage can kill the target. Otherwise, the target's hp will not drop below 0. [damtype] and [lethal]'s positions in the command are interchangeable. If you type "safe" at the end of the command, the mob damage will not hurt characters in the same group as the mob; however, this is only relevant to "all" mob damages.<br><br />
The "percent" keyword changes the min and max from a damage quantity into a percentage of the target's maximum HP. It will not do more damage than the target's current HP, however.<br />
<br />
Examples: 4061, 4831, 1704, 1532<br />
<br />
;DAMECHO:mob damecho "message to target" "message to room" <target> <min> <max> [damtype] [lethal] [safe] [percent]<br />
This command is extremely similar to 'mob damage' but allows echoes to the target and the room the target is in, with a number on the end for damage. This command will initiate combat, unlike mob damage. <br />
<br />
Examples: 701<br />
<br />
;CAST:mob cast <spell> [target]<br />
This command allows a mob to cast any of the spells normally available to players. The spell parameter takes an argument, and you'd type in given spell there just like you would with the regular cast command. The target can be any mob or object in the room or mob's inventory, or, depending on the spell, no target at all. Mob cast costs no mana. You'll usually want to pair this command with a mob echo for more flavor.<br />
<br />
Examples: 4001, 2203, 4838, 301, 4716<br />
<br />
;MANA:mob mana <target> <min> <max><br />
This command drains mana from the target. It works in a similar fashion to mob damage, but it is less complex. The target can be any character in the same room as the mob, or it can be "all," which targets all characters in the room. Mob mana does a random number of mana damage between min and max. Min and max are not dice, they are a range. Mob mana can drain negative mana to cause restoration, but it will not give more mana than a character has max. Likewise, it will never send mana below 0. Mob mana $i commands are an excellent way to make realistic spellcasting for mobs, especially when combined with mob cast and mob damage commands, in addition to the mpchk ifchk.<br />
<br />
Examples: 3139, 2748, 169, 701. This command is unique to CoD.<br />
<br />
;AWARD:mob award <target> <type> <value> [noscale]<br />
This command can award various points to the target. It works almost exactly like the staff command of the same name. The target argument can be any character in the world, but cannot be a mob or a staffer. Below is a chart of type arguments and their relevant range of values:<br />
<br />
gold -10000 10000 prac 10 -10 exp -10000 10000<br />
silver -10000 10000 train 5 -5 align -100 100<br />
<br />
Use this command sparingly and only as a reward for doing important stuff. It is best used in conjunction with the mob quest command, especially when dealing with experience, practices, or trains.<br />
<br />
The 'noscale' argument is optional, and causes awarded experience to be a flat award regardless of the level of the player being awarded. Please keep in mind to level lock large experience rewards to keep quests relevant to the actual level of their area, when using noscale. Without 'noscale', 'mob award exp' modifies awarded XP by 0-200% based on the level difference between target and mob, like XP gained from kills.<br />
<br />
Examples: 2260, 4022, 1027, 1116, 32. This command is unique to CoD.<br />
<br />
;QUEST:mob quest <target> <+/-/=> <questflag><br />
This command modifies the value of a quest flag on the target character. Quest flags are unique, hardcoded flags that save whether a mob has completed a certain event or not. Target is an argument and can refer to any player in the world. Mob quest does not work with mob targets. <+/-/=> indicates whether to set or unset the relevant quest flag; + and = are exactly the same. Each area automatically comes with 8 quest flags, regardless of the total vnums of the area, that will use the syntax of [area name]1-8 (without .are) ex. 'truce1'. <br />
<br />
Examples: 54, 3113, 2390, 4874, 1596. This command is unique to CoD.<br />
<br />
;PETIFY:mob petify <target> <victim><br />
This command makes the victim the pet of the target. It works almost exactly like the staff command of the same name. Target and victim are arguments, and they can be any character in the world. However, mob petify will not work if victim is a player or if target already has a pet. It's probably not a great idea to petify a victim that's not in the same room as the target, even though you can within the extent of the command.<br />
<br />
Examples: 2106, 3196, 700, 707, 715. This command is unique to CoD.<br />
<br />
;FORCE:mob force <target> <command><br />
This command forces the given target to perform the given command. The target can be anyone in the same room as the mobile, excluding the mobile itself. The target can also be "all," which will affect every character in the room that the mob can see and who is not staff. The command can be any regular command - or if the target is a mob, a mob command - but it cannot be an ifcheck. This can be a very powerful command.<br />
<br />
Examples: 5660, 3130, 2710, 3014, 2387<br />
<br />
;GFORCE:mob gforce <target> <command><br />
This command works just like force, except it forces everyone in the target's group as well as the target. The target must be in the same room as and not be the mob. Besides that, it is entirely identical to force.<br />
<br />
Examples: 5276<br />
<br />
;VFORCE:mob vforce <vnum> <command><br />
This command works just like force, except it forces every character in the world of the specified vnum to do the given command. Vnum must be a number. Vforce will not force the mob that executed the command, or players, or characters that are currently fighting. Besides that, it is entirely identical to force.<br />
<br />
Examples: None.<br />
<br />
;MFORCE: mob mforce <target> <command><br />
This command is similar to force, but it allows a mob to force a player to perform commands that players cannot normally perform, i.e. mob commands. It can only target a single player and not the player's group. It is very useful for a variety of things, as mob commands behave differently than player commands and can allow for interesting mechanics. For example, use mforce to have a player use 'mob oload' for a quest reward, as this bypasses item and weight carry limits, so there won't be any issues having them receive the item. <br />
<br />
Examples: None (for now).<br />
<br />
;AT:mob at <location> <command><br />
This command allows a mob to perform any single action at any location on the MUD. It's like using a mob goto, a command, and another mob goto to return all in one command. The location can be a vnum or any one word mob or object. The command parameter works just like a regular line of code in a mobprog. The <command> can be any regular or mob command, but it cannot be an ifcheck. If you want to perform multiple commands and ifchecks in a remote room, use multiple mob goto statements instead.<br />
<br />
Examples: 4073, 1003, 5664, 735, 2387<br />
<br />
;DELAY:mob delay <pulses><br />
This command sets the delay timer for the mob. The delay timer is measured in pulses - to see how quickly pulses count down, cast a buff spell and see how its timer works (one pulse is about 4 seconds). When the delay timer hits zero, the mob's delay trigger prog will execute, if it has one. Unless a mob has update_always, its delay counter won't tick down unless there are players in the area - staff do not count. So when debugging progs, you may note in mpstat that the delay counter can stagnate. Mob delay is an intensely useful function and requires some thought to figure out. Due to the nature of mob delay, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 182, 1005, 1502, 1061, 1806<br />
<br />
;CANCEL:mob cancel<br />
This command cancels the mob's delay timer. It sets it to zero and stops the mob's delay triggers from activating. While waiting enough pulses will also let the delay timer reach zero, that will make the mob's delay triggers activate. This will not.<br />
<br />
Examples: 4011, 1009<br />
<br />
;REMEMBER:mob remember <target><br />
This command stores the name of a target in the mob's memory. Target is one argument and can be either a name or a variable. The target can be anywhere in the world. Once remembered, the target's name is stored as $q for the mob and will remain until a mob forget command, a new mob remember, or the mob's death. Mobs will remember players through player deaths, but will forget a player when that player logs out. A mob's memory can be seen with mpstat. If a mob has no target, it will remember the first person who walks into the room with it - note this, as it can cause problems for some mobprogs. Due to the nature of mob remember, many potential example mobprogs are split up over several progs and are difficult to show here.<br />
<br />
Examples: 4065, 1211, 1053, 1015, 160<br />
<br />
;FORGET:mob forget<br />
This command empties the mob's memory. It is the opposite of mob remember and almost always appears accompanying it. Besides mob forget, the only way to clear mob memory is to kill the relevant mob (although you can always store a new target to mob memory with a new mob remember).<br />
<br />
Examples: 738, 1501, 3142, 5508, 2727<br />
<br />
;CALL:mob call <vnum> [victim] [obj1] [obj2]<br />
This command executes a mobprog subroutine. Essentially, when you put in a mob call command, the MUD goes into the mobprog of the given vnum and executes it. Once the sub-prog finishes, the main prog continues as normal. Victim, obj1, and obj2 are optional parameters that specify what $n, $o, and $p are in the subroutine, respectively. If they are left out, the subroutine will execute with $n, $o, and $p set to null. If you want these variables to be null, just type null in the appropriate fields. Victim, obj1, and obj2 will look for mobs or objects in the same room as the mob. A mobprog can call itself recursively, but the MUD will stop such infinite loops after 5 recursive calls.<br />
<br />
Examples: 1368, 47, 1400, 2395, 5661<br />
<br />
;COUNTER: mob counter <value OR 'zero'><br />
This command allows basic addition and subtraction operations to be performed on a variable stored on a mob. An ifcheck exists to take advantage of the command (if counter). The value parameter can be either positive or negative to perform either addition or subtraction. The word 'zero' sets the counter to zero.<br />
<br />
Examples: 21, 22<br />
<br />
;FACE:mob face <long/short/name> <string><br />
This command changes the mob's long or short desc, or name, to whatever is specified. <br />
<br />
Examples: 9038<br />
<br />
;FLAG:mob flag <victim> <flag type> <flag> +/-<br />
The Flag command can modify the act, act2, affect, shield, imm, resist, vuln, and off flags of a mob. A mob can use this command to change its own abilities on the fly.<br />
<br />
;SDAMAGE:mob sdamage ??? ???<br />
Appears to be an uncoded solution to the problem that the $a flag fixed.<br />
<br />
;SPAWN:mob spawn <victim> <room vnum><br />
The Spawn command will change the target's recall point to the specified room vnum.<br />
<br />
Examples: 9098<br />
<br />
;RESCUE:mob rescue <victim><br />
The Rescue command works as the Rescue skill does, but without the restrictions on grouping or any skill checks.<br />
<br />
;EXITPERMIT:mob exitpermit<br />
Exitpermit allows mobs with exit progs to allow the character through the exit normally, instead of requiring transfer commands or other sneaky tricks.<br />
<br />
Examples: 2917<br />
<br />
;ASSET:mob asset <victim> <art/sound> <file> [duration in beats]<br />
The Asset command is used for enhanced asciiart and sound functions using the Project Tuna client. For advanced usage, see [[Project_Tuna#Mob Asset]].<br />
<br />
Examples: 10289, 12002<br />
<br />
;OSET: mob oset <object name> <field> <value><br />
Fields: name(a), short(a), long(a), level(#), wear(a), extra(a), extra2(a), extra3(a), condition(#)****, weight(#), cost(#), timer(#), value0(#), value1(#), value2(#), value3(#), value4(#) or v0-v4<br />
****condition is not oset into a true value but adjusted ex: mob oset $o condition -20 will reduce its condition by 20 regardless of its previous condition.<br />
<br />
Value:<br />
(a) = requires a string or bit/flag name in place of value<br />
(#) = requires a numerical value<br />
<br />
Mob oset will only target objects in the mob's inventory or in the same room as the mob.<br />
<br />
;MSET: mob mset <target> <field> <value><br />
Fields: str(#), dex(#), sex(a/#), level(#), maxhp(#), hp(#), maxmana(#), mana(#), maxmove(#), move(#), align(#), damtype(a), hitroll(#), magroll(#)<br />
<br />
This command seems to be incompletely implemented. Mobs can currently only mset themselves, but can be mob forced by other mobs to mset themselves.<br />
<br />
* See [[Oset_and_mset_tips_and_tricks]] for more information<br />
<br />
;ADDLAG: mob addlag <target> <value><br />
This command adds pulses of lag to a player (in which they can not act or move at all). Allowed value is anywhere from 1 to 100. Useful for keeping players still during a story scene or if mobs need to perform their actions without player interruption.<br />
<br />
;CLAN: mob clan <target> <clan><br />
This command allows a mob to add a player to a clan instead of requiring an Immortal's assistance. The clan must already be created, however.<br />
<br />
;PRETITLE: mob mforce <target> mob pretitle self <pretitle><br />
This command allows a mob to set a player's pretitle instead of requiring an Immortal's assistance. Technically a mob can only set their own pretitle to avoid setting someone else's pretitle by mistake, so this syntax causes the mob to force the player to set their own pretitle.<br />
<br />
===MOB TRIGGERS===<br />
<br />
The triggers are listed alphabetically, since there aren't all that many of them and the ones that have a similar purpose have a similar name. Triggers are mostly self-explanatory, so the main use of this section will be to give examples of how the triggers are used in the MUD. Examples of usage will not be given in this section, but I will attempt to describe situations in which the triggers are usable. To see the triggers on any given mob, mpstat them.<br />
<br />
;ACT:addmprog <vnum> act <phrase><br />
The act trigger is the most versatile and basic trigger there is. The act trigger reads output directly from the MUD. It will activate when the <phrase> text appears to the mob. This means that act triggers will activate when a mob or player says something, when a mob or player does a social, or when a mob or player does an action (like give or eat or sleep). However, the act trigger will not activate on emotes. Act triggers are case insensitive. If an act trigger includes color codes, as with a color coded object being opened, the act trigger <phrase> itself will require the color codes in order to trigger correctly. Act triggers can use one or more words in <phrase> - to set the phrase as multiple words, surrounded the phrase with "quotation marks." When triggered by someone's speech, the act prog will activate before the <phrase> is actually spoken - making it look out of order. Many mobiles have an act prog with the phrase "talks to you," which triggers on the talk social. This is especially common in towns and with humanoid mobs.<br />
<br />
;BRIBE:addmprog <vnum> bribe <amount, in silver><br />
<br />
;DAMTYPE:addmprog <vnum> damtype <type of damage><br />
The damtype trigger is activated when a mob receives damage of a particular type. Be aware that multiple-hit attacks such as Pearl, kick, etc. will trigger the prog with every hit. The damtype specified is it's number, not its name:<br />
0 - None* 1 - Bash 2 - Pierce 3 - Slash 4 - Fire 5 - Cold 6 - Electric<br />
7 - Acid 8 - Poison 9 - Negative 10 - Holy 11 - Energy 12 - Mental 13 - Draining<br />
14 - Water 15 - Light 16 - Other* 17 - Harm* 18 - Charm 19 - Sound 20 - Wood<br />
21 - Silver 22 - Iron 23 - Wind 24 - Earth 25 - Dark<br />
<br />
* Very, very few attacks use the None, Other, Harm, or Charm damtype to actually deal damage.<br />
<br />
;DEATH:addmprog <vnum> death <percent><br />
<br />
;DELAY:addmprog <vnum> delay <percent><br />
The delay trigger is activated when the delay timer for the mob decrements to 0. To set a mob's delay timer, use the mob delay command. The trigger has a <percent> chance of activating when the delay timer hits 0, although in almost every usage of this command, 100 is used for the <percent> parameter. Delay triggers are known to occasionally and randomly not work. Delay timers will only count down if players are currently in the mob's area or have recently been in the area. It is important to note that delay triggers are checked at the same time as schedule and random triggers. A simultaneous schedule trigger activation will override a delay trigger, and a delay trigger will likewise override a random trigger activation.<br />
<br />
;EXALL:addmprog <vnum> exall <exit number><br />
The exall trigger works exactly like the exit trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the EXIT trigger.<br />
<br />
;ENTRY:addmprog <vnum> entry <percent><br />
The entry trigger is activated whenever the mob walks into a new room. The trigger has a <percent> chance of activating on each mob movement. The entry trigger does not carry a $n target into the mobprog, so, in general, this trigger is not as useful as greet or grall. <br />
<br />
;EXIT:addmprog <vnum> exit <exit number><br />
The exit trigger is checked whenever a PC tries to exit the mob's room. The trigger will activate whenever a player tries to use <exit number>'s exit. It is important to note that if an exit trigger activates, the player's movement will be cancelled - so if you want a player to be able to move after an exit trigger has been activated on him, you'll need to use the mob transfer or mob exitpermit commands. The exit trigger will only activate if the mob can see the target character. Exit triggers will activate for mobiles as well, so exceptions will have to be made within the prog to avoid this if desired.<br />
<br />
The following <exit numbers> collaborate with the indicated exits:<br />
0 - north 1 - east 2 - south 3 - west 4 - up<br />
5 - down 6 - ne 7 - nw 8 - se 9 - sw<br />
<br />
;FIGHT:addmprog <vnum> fight <percent><br />
The fight trigger is checked at the end of each combat round for the mob. The trigger has a <percent> chance of activating each round. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Most mob combat routines are activated with the fight trigger.<br />
<br />
;GIVE:addmprog <vnum> give <object><br />
The give trigger is checked when an object is given to the mob. When an item of keyword <object> is given to the mob, the trigger activates. The phrase 'all' can be used for <object> to cause the give trigger to activate when any item is given to the mob. In the mobprog triggered by the give trigger, the variable $o represents the object given. It is common practice to design all give triggers with the 'all' phrase and then have specific object keywords checked within the mobprog. This is so that objects can be given back to the character who gave them with the 'give $o $n' statement.<br />
<br />
;GRALL:addmprog <vnum> grall <percent><br />
The grall trigger works exactly like the greet trigger with the difference that the mob does not have to see the target character in order to activate the trigger. For further information, please see the GREET trigger.<br />
<br />
;GREET:addmprog <vnum> greet <percent><br />
The greet trigger is checked whenever a character enters the room that the mob occupies. It has a <percent> chance of activating each time a character enters the room. Note that if several characters enter the room simultaneously, such as when characters travel in a group, the greet trigger will activate for each of the characters. The greet trigger activates for mobiles as well as players, so exceptions must be made within the prog to ignore them if desired. The greet trigger will only activate if the mob can see the target character. <br />
<br />
;HPCNT:addmprog <vnum> hpcnt <hp percent><br />
The hpcnt trigger is checked at the end of each combat round for the mob. The trigger will activate if the mob's hp percentage drops below the <hp percent> level. Both a hpcnt trigger and a fight trigger can activate in the same combat round. Hpcnt is frequently used as an easy way to activate mob desperation attacks.<br />
<br />
;KILL:addmprog <vnum> kill <percent><br />
The kill trigger is checked when someone initiates combat with the mob. The trigger has a <percent> chance of activating whenever someone initiates combat with the mob. This trigger only activates when someone attempts to kill the mob when it was not previously fighting. That is to say that the trigger activates only when combat is initiated, not when additional characters (such as groupmates) start attacking the mob.<br />
<br />
;RANDOM:addmprog <vnum> random <percent><br />
The random trigger is checked once every mob pulse for the game. A mob pulse is equal in frequency to a combat pulse. For reference, there are 15 mob pulses in a tick and a mob pulse triggers about once every 4 seconds. Random triggers have a <percent> chance of activating every mob pulse, but only if players are currently in the mob's area or have recently been in the area. A mob with the update_always act flag will have its random triggers checked every mob pulse, regardless of the status of players. Random triggers are commonly used for all sorts of mob activity. It is important to note that random triggers are checked at the same time as schedule and delay triggers, and the simultaneous activation of either of these triggers will prevent a random trigger from happening. Random triggers can activate while a mobile is fighting, but sometimes it will not, so it is not reliable.<br />
<br />
;SCHEDULE:addmprog <vnum> schedule <hour><br />
The schedule trigger is checked once every hour, on the hour. The <hour> parameter equals a number from 0 to 23, where 0 is midnight and 12 is noon. If the <hour> equals the current hour, then the trigger activates. Schedule triggers are commonly used for time-based mob activity, especially mobs that move based on the time of day. It is important to note that schedule triggers are checked at the same time as random and delay triggers, and the activation of a schedule trigger will override any simultaneous delay or random trigger.<br />
<br />
;SPAWN:addmprog <vnum> spawn <percent><br />
The spawn trigger is checked whenever a mob is reset into an area or loaded, either with a mob mload command or an immortal load mob command. When the mob is loaded or reset into the area, there is a <percent> chance that the spawn trigger will activate. For the most part, the spawn trigger is used to load equipment onto a mob when one does not want said equipment reset 100% of the time like with a normal reset, but there are a wide variety of uses.<br />
<br />
;SPEECH:addmprog <vnum> speech <phrase><br />
The speech trigger is mostly identical to the act trigger, with the biggest difference being that the speech trigger only activates when a mob or player uses the 'say', 'osay', or 'tell' commands. The speech trigger is best used when one wants to limit mob response to speech instead of actions. Of further interest, the speech trigger will occur AFTER the target has actually spoken, unlike the act trigger. For further information, please see the ACT trigger.<br />
<br />
;SURRENDER:addmprog <vnum> surrender <percent><br />
The surrender trigger, while present on the triggers list, is defunct and is not actually used.<br />
<br />
*I like using this trigger to show what mprogs my mob calls within its other mprogs. -Ageatii<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Builder_Applications&diff=2128Builder Applications2018-09-27T18:07:17Z<p>Pascal: </p>
<hr />
<div>'''Certain rules must be followed when submitting an application to become a builder.'''<br />
<br />
# Be at least level 50 or remorted before submitting your application.<br />
# Application must be a note to ALL immortals, titled: Builder Application<br />
#* You may also email us your application. Post a titled note if you do so.<br />
# Applicant must submit a minimum of 3 room descriptions.<br />
## Descriptions must be at least 255 characters long.<br />
## Descriptions may include extra descriptions (keywords within the room description that can yield further descriptions.) Extra descriptions are encouraged and have no minimum or maximum size.<br />
# Applicant must submit a minimum of 2 object descriptions.<br />
## Must include the short description. ex. (an apple)<br />
## Must include the long description. ex. (A small red apple is seen here.)<br />
## Must include the extra/full description. (What you see when you look at it)<br />
# Applicant must submit a minimum of 2 mobile descriptions.<br />
## Full descriptions must be a minimum of 255 characters long.<br />
## Must include the short description.<br />
## Must include the long description.<br />
## Must include a response for when you TALK to the mob.<br />
# Descriptions should be well formatted and include minimal spelling and grammatical errors.<br />
# Must include two detailed descriptions of sample quests/events that, to the best of their knowledge, will work reasonably within the code of this MUD.<br />
#* The samples do not need actual code with them.<br />
# Application must be easy to read and properly organized.<br />
<br />
An applicant may not necessarily be accepted even if they follow all of the guidelines.<br />
Respect the Staff's decision. We don't care if you build/code/own another MUD, you still must<br />
follow the guidelines. The reason for the<br />
level requirement is to demonstrate your dedication to the MUD. Applicant may also be subject<br />
to an interview with the Staff.<br />
<br />
<br />
* '''Concerning those who become Builders.'''<br />
<br />
# Your first area shall contain a maximum of 25 vnums.<br />
## 25 room vnums, 25 object vnums, 25 mobile vnums, 25 mprogs.<br />
## 100 vnums in total. No one can waive this rule.<br />
# Your first area cannot be a city or any other specifically residential area. <br />
#* No first area can contain any shop unless authorized by a staff member.<br />
# Only higher immortals have access to mprogs (for security reasons).<br />
#* If you need an mprog in your area, ask an immortal of status ADV or higher.<br />
# Repeating room descriptions are mostly unacceptable.<br />
# Abuse of privileges (see help rules), will not be tolerated.<br />
# Your area must be complete (descwise) within a month or you shall be fired.<br />
# Fail to log on within this time period and you shall be fired.<br />
# Should a Builder quit or be fired while an area is in progress, the Staff may still use it and edit it as they see fit.<br />
# All areas are subject to revision by Staff if necessary.<br />
<br />
-Ageatii, Head Builder</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Apr_2018:Booster_Tower&diff=2127Apr 2018:Booster Tower2018-09-27T17:16:30Z<p>Pascal: </p>
<hr />
<div>Area of the Month for April 2018 is [[Booster_Tower|Booster Tower]]!<br />
<br />
A template format for your review is below; click 'edit' at the top of the page, copy-pasta from the <nowiki>----</nowiki> to the next <nowiki>----</nowiki>, and fill in the gaps!<br />
<br />
('''''Yes,''''' a wiki account is required to edit the page and therefore post your review, but take heart: The wiki is hosted by the Cleft itself, not a third party!<br />
<br />
**Post-reviews, Booster Tower was altered too significantly to note every change here, thanks. 9/27/2018<br />
<br />
<br />
----<br />
<br />
'''Player: You!(Class/Level)'''<br />
<br />
'''Review Date(s): '''<br />
<br />
<br />
'''Descriptions: X/10'''<br />
<br />
How does the area's room descriptions(descs) work for you? Do they give you a good idea of the area? Do things that stand out in the desc and NEED explanation GET that, either from flavor text(extra-descs) or NPCs in the room or anything?<br />
<br />
What about mobiles(mobs) and their descriptions? Can you get a decent mental image of who or what this NPC/monster is? Do they respond when you talk or interact with them?<br />
<br />
Some areas have interact-able objects like fountains. Do they stack up well also?<br />
<br />
<br />
'''Balance: X/10 (OR N/A)'''<br />
<br />
(NOTE: combat will be most accurately gauged when your character is in the area's suggested level range.)<br />
<br />
If this area has combat, how does it feel? Does anything jump as horribly overpowered and impossible to deal with? What about the flipside, anything far too easy to beat? <br />
<br />
Are purchased or rewarded items at the appropriate strength levels? Is the effort required to obtain rewarded items reflected in their usefulness (or uniqueness and fancifulness)<br />
<br />
<br />
'''Attractions: X/10'''<br />
<br />
Why would you suggest someone come to this area?<br />
Is it just a good place to grind experience(lots of mobs)?<br />
Does the area provide a chunk of good gold and loot?<br />
<br />
What about the quests? Does this area's quests feel properly done, or is there some part of it that you feel needs work?<br />
<br />
For towns, are the shops good? Any other non-combative attraction for the area?<br />
<br />
<br />
'''Connections: X/10 '''<br />
<br />
How easily and well does this area connect to its nearby areas?<br />
Does it make sense thematically to be connected to the areas it is?<br />
<br />
<br />
'''Personal'''<br />
<br />
Any comments you'd like to make that you don't feel apply to the other sections can go here!<br />
<br />
<br />
<br />
----<br />
<br />
'''Player: Scribble(Knight/16)'''<br />
<br />
'''Review Date(s): 4/1/2018'''<br />
<br />
<br />
'''Descriptions: 4/10'''<br />
<br />
The descriptions of the mobs are short and sweet, which is fine. They describe them rather well, but just somewhat unimaginatively. The Snifits all share a description except for one, describing them as Booster's "three main toadies" even though there is a fourth. This fourth one is also a shopkeeper, but looking at him still reveals his condition as if he were killable.<br />
<br />
The room descriptions are easy to ignore and very short. A few are even one sentence. The room you are sent to after taking the trip there refers to the event that sent you there, even though it's possible to leave from this room and then go back through it normally, obviously not having arrived there the same way as you did initially. There are very few things in the room descriptions to look at and nothing in them is ever important, every important interactable object and mob being plainly visible in the room.<br />
<br />
While reading the descriptions does help mildly paint a picture of the area, the tower is more or less a free for all killing spree zone without much to look at. The only location within this area that is actually interesting to read is the Marrymore Province, but it lacks extra descriptions. On that note, extra descriptions are highly lacking and the ones that *do* exist do not add much more to the area.<br />
<br />
This is somewhat an important note as, being a very popular, easily accessible area that nearly every newbie will visit, it does not help adjust them to the fact that reading room descriptions is typically very important in the Cleft. Though, arguably, completing the quests would still be very hard to do without reading the descriptions of the mobs involved.<br />
<br />
<br />
'''Balance: 8/10'''<br />
<br />
The balance here is good, in regards to mobs. There are large numbers of killable mobs all around the tower, ranging from 15 to 19. All of the named mobs, with sparse few exceptions, are killable and much higher level, however they are only so much more difficult than the regular mobs, except for a few (the Apprentice for example is rather tough). My character is perhaps slightly more well geared than your typical newbie, though these mobs will be harder for some classes than for others, as well. At level 17 (I leveled while writing this) I'm able to kill the level 25 mobs here, as long as I'm paying attention. For a lower level area, perhaps this is okay. The trash mobs are of varying difficulty and introduce some new status effects to new players, which is important, though annoying. <br />
<br />
For instance, I've just been not killing Orb Users because I can't re-equip my shield after using shield slam due to being blinded. This is just annoying and not really a huge issue. Bob-Ombs are probably the weakest enemies, but will explode for no experience if not killed quickly, which is a neat mechanic, teaching new players that not all fights will be so cut and dry.<br />
<br />
The items available here are decently balanced, though the level requirement for certain quest rewards is worth some discussion, mentioned below. The actual strength of these items is probably fine.<br />
<br />
<br />
'''Attractions: 7/10'''<br />
<br />
Booster Tower is obviously a hotspot for leveling and it's suggested quite frequently already. Its location is incredibly convenient, much closer to Truce than other similar leveled areas, and a useful spot for much longer than others. It's a good leveling spot for first life characters and newbies from its starting level (depending on the skill and class of the player, possibly earlier), though it tends to lose its steam quite a few levels before its suggested ending level range.<br />
<br />
There are useful pieces of gear, here, from quests or otherwise, that are typical standard fare for your general player. Some of the quest rewards are not useable until the very last level of the range of the tower. Even for a first life character, the quests are not difficult to complete before level 25, even *far* before 25, potentially teaching newbies the hard way that items will poof from your inventory if they are 10 levels out of reach. By the time you can actually use them, you probably won't even be in Booster Tower anymore.<br />
<br />
The "main" quest (the one with the most steps) is not too hard to follow and figure out, although considering its main mechanic is giving items to NPCs, it's unfortunate that some of the NPCs may keep these quest items when they are the incorrect recipient. There is inconsistency here, as some NPCs WILL give back wrong items and others will not. It's not clear if this is intentional, but if so, it's not really a great sort of 'difficulty modifier' in my opinion, and moreso just annoying.<br />
<br />
It's also worth questioning if it's worth preserving the situation within this quest where the final turn in item is a potentially useful item for certain classes to keep, while the final reward would be bad for those classes. It's possible to do the quest over again, but that would insist that if the final reward is not good for your class, you basically just do it again, while other people would not have to. I'm not sure this is a great mechanic, personally.<br />
<br />
One of the quests can be cheesed (I won't explain how publicly!) really easily, while another requires an item that requires level 20 to wear, but the reward requires level 25 to use. The item also doesn't *necessarily* require combat to acquire, so the jump in level requirements is potentially super annoying. Basically if you complete it as soon as you are able, you'll still have an unusable item in your inventory for five levels before you even know if it's worth the space to keep it.<br />
<br />
These level requirements for the quest rewards is the only thing I would really think to take a second look at, if only for the fact that Booster Tower - despite being level 16-25 - becomes less useful and will typically be finished significantly before its final level of 25, even by newbies, as has been demonstrated recently.<br />
<br />
<br />
'''Connections: 5/10 '''<br />
<br />
This is one of the most easily accessible, mob-dense areas for low level leveling in the game for a Truce start. Thematically, Booster Tower is questionable in its location. It's just a short walk from Truce, between there and Rocket Town. The entrance to the tower itself implies the tower is somewhat unpleasant looking, saying that the door has been broken down. For an area openly displayed between two neat and orderly towns, this seems like something that may be of interest to be addressed by the authorities. Maybe it's mentioned and I just haven't seen it.<br />
<br />
<br />
<br />
----<br />
'''Player:''' Aludra(Wizard/8) -- Token'd<br />
<br />
'''Review Date(s)''': 04/06/2018<br />
<br />
<br />
'''Descriptions''': 5/10<br />
<br />
The area itself is fairly decent. Some rooms have much shorter descriptions than others, but the environment is rather same-y all in all. Especially in the source material. There are only so many ways to say 'big ugly marble chessboard room.' I wouldn't mind seeing some colour pops though, just to highlight some of the more interesting things. There aren't really any extra descriptions of note other than the TV near the top. Cute, but not inspiring.<br />
<br />
Most of the mobs have strange formatting and linebreaks. Snifit 1 for example:<br />
<br />
He wears a grey coat over his whole body, a black belt, and a black gas <br />
mask covering his face. He is one of Booster's three main toadies and loves<br />
to catch beetles and eat cake. <br />
<br />
And, of course, a Spookum: <br />
<br />
Spookums are the same height and wear the same mask as Snifits, but their<br />
rank is lower and their robes are blue rather than grey. They came to<br />
become Snifits under Booster's training, but he only wants four. <br />
<br />
They all seem to be written under a very short linewrap. I'm not going to paste every single mob description, but there are a lot of them with this issue.<br />
<br />
Other than that, they're all nice and concise and give a good idea of what you're dealing with.<br />
<br />
As for area objects, such as the toy chest and therein, these objects suffer the same linewrap issue. One of the trains are barely described at all. Player-ownable objects (such as the balloons) have equally lackluster notes. Some colour pops would be great there too.<br />
<br />
All in all, the writing is decent, but it's lacking in content. Jazz it up!<br />
<br />
'''Balance''': 7/10 (OR N/A)<br />
<br />
The chain chomps are probably the most difficult thing here to fight. Disproportionately so, given their relative level.<br />
<br />
Fireballs are definitely the weakest, and their level/xp are true to that. Would be neat if they were more in line with the rest of the area.<br />
<br />
Second to fireballs, bombs are definitely probably the weakest. I just wish they didn't cease to give you XP if they delete themselves via explosion. If they survived that with 1hp, I'd be a lot happier. <br />
<br />
<br />
I wish the rewards were more consistently leveled though. Equipment and items you can get here range from 15 to 45. By level 25, there are definitely way better places to be and much better items to use. At least the level 45 item isn't terrible. It's very easy to lose track of though, especially at a lower level where it will disappear and you'll forget about it entirely.<br />
<br />
<br />
'''Attractions''': 7/10<br />
<br />
There's basically no reason not to come to this area if you're starting out on the Truce side. It's easily located, it's packed to the gills with things to kills. The money drops aren't too bad for the level. There are plenty of little hidden treasures you can acquire if you know what to do. And, most importantly, you can do the beetle hunting minigame and rack up all kinds of dosh if you're bored.<br />
<br />
The main questline here is pretty slick. It takes a little bit of trial and error, but once you get rolling, it's hard to stop!<br />
<br />
There are three shops. None of which have any weapons or armor, but you can get some useful goodies here, if you know where to use them!<br />
<br />
<br />
'''Connections''': 10/10<br />
<br />
It connects Truce, Rocket Town and Rabite forest. Or, I'm assuming. I've never found the key to the locked back door. But I'm assuming! If the door does go where I think it was, it's a quick trip through Booster's Tower to get to Neko's Cabin, which backdoors into Guardia Castle. Pretty handy shortcut, if true. But where's the key? This might be a Thief Only scenario.<br />
<br />
<br />
'''Personal'''<br />
<br />
All in all, this area is a great springboard into the teen-levels, and further adventure. At least one of the rewards is good for all levels. I just wish it were more visual.<br />
----<br />
<br />
<br />
'''Player: Kaze(Warrior/10ish, Theif 10-15)'''<br />
<br />
'''Review Date(s): April 1st for the Warrior, April 15th for the Thief'''<br />
<br />
<br />
'''Descriptions: 7/10'''<br />
<br />
I like the descriptions as a rule. It's good. Many of the rooms are pretty bland. One common issue is that the names are the primary way to get a feel for relative height short of mapping, not the descriptions.<br />
<br />
The rooms that are noteworthy locations are pretty well described. That includes the entryway, Thomp's room, Booster's room, and Marymore... Dodo, etc. The knifey dude is pretty much the only interesting feature of his room.<br />
<br />
Most of the puzzles are in the descriptions, fair dinkum. This is good. Some level of hand holding is appropriate such an early stage, even, so the clarity is welcome.<br />
<br />
Mobs are pretty descriptive and have a jovial feel. None stood out as particularly bad, but a few were especially good. Valentina's rich trailer-trash vibe was readily apparent. The train's animation played in my head.<br />
<br />
'''Balance: 9/10 (OR N/A)'''<br />
<br />
Fire vulnerability is NASTY in the tower. <br />
<br />
The Bob-ombs seem overpowered for their level. You need DPS to drop them. The boom is devastating or deadly at the low end of the level. (If you have the HP to survive, I suspect they are much easier. Warrior handled them much lower than thief, say) Still, if you ''have'' enough, they are otherwise a bit easy. They are pretty binary that way. Going into the tower at level, I'd recommend most steer clear. On your way out, waste them for the exp.<br />
<br />
Orb users can also be deadly, especially to the fire vulnerable, but their tricks mostly seem challenging to me, not unfair. They blind and hit hard, yet are a bit fragile. I think they're well balanced for level.<br />
<br />
Spookums are pretty fair, given they act as a pretty solid entry requirement. Must be this big to enter. They are pretty much average, Maybe a touch weak, but given their company, that's far from a bad thing.<br />
<br />
Chomps are tough little cookies at level. Got to use dirty tricks or resources to fight them until about mid level. They are fairly easy to avoid and, frankly, used quite well. <br />
<br />
The bosses are a bit of a ramp, as expected and desired. The only one that really seems out of range is Val. Especially if you have the wrong vulnerabilities, she's realy good at smacking a low level character around. It generally wise to come back to finish her off.<br />
<br />
Item rewards range from about what you'd purchase to nice for the level. Clown Gloves are really nice for their level. Otherwise things tend to be a bit light.<br />
<br />
All in all, this is pretty much my standard for combat balance. It's one of the best zones, that way.<br />
<br />
<br />
'''Attractions: 9/10'''<br />
<br />
It's got fun and amusing little secrets. It's got challenging MOBs. It's got some decent EQ. If you like MUDs, it's for you. <br />
<br />
Loot isn't much of a draw, though the shops are. Gold is decent.<br />
<br />
Quests are average. They mostly aren't hard. The Chain Chomp thing is pretty obscure. The Sniffits are humerous but the rewards are pretty pointless. Marymore is cool looking but one of its quest elements is tricky to even spot, much less solve. <br />
<br />
A few more scattered hints are in order. Given the nature of the area, that's probably best solved in other zones, predominantly, but some on site would be good, too.<br />
<br />
<br />
'''Connections: 7/10 '''<br />
<br />
''Why'' it's where it is isn't clear, but it does link to its surroundings in a rational way. Really ought to have a bit more description on the road, though. A tower that big would be visible from quite a ways off.<br />
<br />
<br />
'''Personal'''<br />
<br />
It's my favorite low-level area. <br />
<br />
A clever way across the fireball floor without an encounter would be welcome, as would some more flavor in the interstitial floors.<br />
<br />
<br />
<br />
----<br />
<br />
'''Kolem (Playing as Belle, L. 8-13 Moogle Geomancer, with various others; also Paisley, L~10 thief)'''<br />
<br />
'''Review Date(s): 4/26/2918'''<br />
<br />
As is standard with my reviews, all sections begin with five points. Consistent positives or excellent examples gain points; consistent negatives lose points or half points. Here we go!<br />
<br />
<br />
'''Descriptions: 5/10'''<br />
<br />
Oh, Booster tower. You hold a special place in my heart, but you show your age in a lotta places. One of them is the near-dearth of extra look descriptions--the only ones there are for interactables, as well as a single T.V. On the bright side, all monsters in the tower respond to talking, and spookums and snifits aside, seem to be desced decently. I was gonna ding this area half a point for lack of extra descriptions, but it doesn't really IMPEDE the player--it just feels like a missed opportunity, especially given the bonkers nature of the source material. I'll give it functional marks, but this is an area for improvement.<br />
<br />
<br />
'''Balance: 5/10'''<br />
<br />
This is a hard one, and I feel like it's one of Booster Tower's high points--and low points. The real problem I have with the zone is that, outside of the boss enemies and quest items, there aren't any real 'drops' to speak of in the tower. Spookums, Bob-ombs, Orb Users, Chain Chomps, and Remo Cons don't appear to have any drops whatsoever, and the boss rewards are either high-end of the range or storebought at the very lowest end of the scale (as is the case with Valentia's drops). <br />
<br />
On the other hand, I have nothing but praises to sing ABOUT those mobs. Booster Tower's mobs--the ones above, before we get to the bosses--all have interesting, engaging combat tricks. Analyze reveals that chain chomps have a random major weapon resistance, making melee classes have to think and plan, while Bob-Ombs will severely punish, say, a caster who bungles a few spells (this happened to me more than once). Orb users introduce low level blind and fire attacks into the mix, while Remo Cons inflict the Curse ailment, which can lead to real problems. Coupled with the levels you might attempt the tower being the introduction to the necro mechanics, these monsters are incredible teaching moments. Which leads us to...<br />
<br />
The bosses. They can and WILL thrash players who are much too low level to challenge them, with powerful attacks. One sore point is the Apprentice miniboss, who can come off as a nasty surprise the first time you encounter them, and is probably single handedly responsible for most of the new player deaths in the tower. Fireballs are also fairly obnoxious, but much less challenging than just about everybody else in the zone. Some sort of trick mechanic to switch them 'off' for a bit might be cool, similar to the trick for the chain chomps and spookum at the doorway. Maybe a minor in-room puzzle? Booster can call for help, and Valentia has powerful spells for the level. <br />
<br />
Another sore spot is the items--not just the lack thereof from the main common monsters, but the boss drops, as well, and those items gleaned through quests and mini-quests. They're all over the scale, swinging wildly from cheap but usable to high level and very useful, with levels that don't really quite suit their placement. The Balloons item, wands, and rod in particular in this zone are all handy to have, but have caveats--whether they be rot-death, high level, or simply hidden in a multi-level quest with a slightly obscure (but fun!) beginning. I kinda wish it was possible to expand the entry point to the quest, just because I enjoy it personally.<br />
<br />
All in all: Plus one full point for dynamic, interesting monsters that have multiple approaches to fights, minus one half for a lack of drops, and minus another half for the swinginess of item level and placement--it's items that hold this zone back, and that's a pity, because the combats here are genuinely a blast. (Hah!)<br />
<br />
<br />
'''Attractions: 7/10'''<br />
<br />
Hmm. While Booster Tower has solid experience payouts, the treasures--once you know what is here--are pretty useful, even though their levels are skewed. Additionally, there's at least one major item for a tie in quest later. I wish there were more to recommend here, especially in Marrymore--it's just big enough and themed enough with enough facilities to suggest expanding it to a mini-town, like Monstro Town or Medina. It'd really add some zing to the tower! There are also some mini-quests available in other areas that tie here, and a little lateral thinking can net you an nice piece of equipment. I can award one point for that--the distinctive items that are here are pretty fun, but I wish there was more reward for the lower end challenges here. See the Suggestions section for more. <br />
<br />
Additionally, the Beetle-catching minigame--and the hidden quest given by it--is really fun, but as others have pointed out, the mobs in the tower don't return items. I'll award another half point to the beetle game, and I wish there was more to do with it. There's also a minigame miniboss, which is always nice to see! I'll award it another point for that.<br />
<br />
<br />
'''Connections: 5/10 '''<br />
<br />
Booster tower itself has been worked on, off and on, by different builders for several years. This sorta patchwork addition is fine, but the surrounding environments--truce and Rocket town--refer to it only sparsely. It might be nice if it being obnoxious and visible played into more areas.<br />
<br />
Ultimately, it only has two exits, and one of them is locked by default. Which is... ehhhn. I wish there was more to Marrymore, and I wish there were more connections to external zones--it feels like the sort of place a Cannon Travel guy would totally make an installation on a balcony, or something. <br />
<br />
Five points for a functional, easy connection to one of the starting towns, but it could always stand to be improved.<br />
<br />
'''Personal'''<br />
<br />
Woof. What do I even say here? Booster's tower is practically a fixture of my time in the cleft, and it really sold me on the kind of lateral-thinking fighting on your feet that comes more into play as you fight later monsters. I love the flavor of the enemies here, but the tower itself could use a lot of touch ups. <br />
<br />
FINAL AVERAGE: Out of four categories, average score is '''5.5'''.<br />
<br />
SUGGESTIONS FOR IMPROVEMENT:<br />
<br />
*Rebalance item levels and flags and grant minor loot drops to the lower end monsters. One suggestion that sticks out in my mind is a hunk of Cosmo Brimstone as an uncommon drop from bob-ombs, regardless of if they explode or not--one gold treasures are decent enough for the level, and it would reward players with crafting components that they could feasibly use to start poking the crafting shops. It would also be thematically consistent with the bob-omb recipe sold in cosmo canyon.<br />
<br />
*Touch up room, mob, and extra descriptions. For being such a gaudy place, Booster Tower uses criminally little color--the portraits are begging for ascii art or at least extra descriptions, along with loads of other spots it'd be easy to add more un-style.<br />
<br />
*Expand the beetle minigame! Yes this is silly and dumb and unnecessary but I love it, and I wish more beetle-based enemies yielded special rewards / there were more variants of beetle / a beetle box event item. Shush don't judge me.<br />
<br />
*Add additional resources to Marrymore. It has a fountain and even benches--expanding it into a minitown would reward adventurous players, and would be a great spot for 'toys' and the like to be sold in the future.<br />
<br />
*Give more external clues about the way to bypass the guard / get various prizes / bypass the chomps with the use of a logically fitting item.<br />
<br />
<br />
----<br />
<br />
<br />
[[Category:Area of the Month|*]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=July_2018:_Faron_Woods&diff=2126July 2018: Faron Woods2018-09-27T17:15:01Z<p>Pascal: </p>
<hr />
<div>Area of the Month for July 2018 is [[Faron_Woods|Faron Woods]]!<br />
<br />
A template format for your review is below; click 'edit' at the top of the page, copy-pasta from the <nowiki>----</nowiki> to the next <nowiki>----</nowiki>, and fill in the gaps!<br />
<br />
('''''Yes,''''' a wiki account is required to edit the page and therefore post your review, but take heart: The wiki is hosted by the Cleft itself, not a third party!<br />
<br />
<br />
----<br />
<br />
'''Player: You!(Class/Level)'''<br />
<br />
'''Review Date(s): '''<br />
<br />
<br />
'''Descriptions: X/10'''<br />
<br />
How does the area's room descriptions(descs) work for you? Do they give you a good idea of the area? Do things that stand out in the desc and NEED explanation GET that, either from flavor text(extra-descs) or NPCs in the room or anything?<br />
<br />
What about mobiles(mobs) and their descriptions? Can you get a decent mental image of who or what this NPC/monster is? Do they respond when you talk or interact with them?<br />
<br />
Some areas have interact-able objects like fountains. Do they stack up well also?<br />
<br />
<br />
'''Balance: X/10 (OR N/A)'''<br />
<br />
(NOTE: combat will be most accurately gauged when your character is in the area's suggested level range.)<br />
<br />
If this area has combat, how does it feel? Does anything jump as horribly overpowered and impossible to deal with? What about the flipside, anything far too easy to beat? <br />
<br />
Are purchased or rewarded items at the appropriate strength levels? Is the effort required to obtain rewarded items reflected in their usefulness (or uniqueness and fancifulness)<br />
<br />
<br />
'''Attractions: X/10'''<br />
<br />
Why would you suggest someone come to this area?<br />
Is it just a good place to grind experience(lots of mobs)?<br />
Does the area provide a chunk of good gold and loot?<br />
<br />
What about the quests? Does this area's quests feel properly done, or is there some part of it that you feel needs work?<br />
<br />
For towns, are the shops good? Any other non-combative attraction for the area?<br />
<br />
<br />
'''Connections: X/10 '''<br />
<br />
How easily and well does this area connect to its nearby areas?<br />
Does it make sense thematically to be connected to the areas it is?<br />
<br />
<br />
'''Personal'''<br />
<br />
Any comments you'd like to make that you don't feel apply to the other sections can go here!<br />
<br />
<br />
<br />
----<br />
<br />
'''Player:''' Emouse (Dollmage, L100, ~4 remorts)<br />
<br />
'''Review Dates:''' 8/14/2018-8/15/2018<br />
<br />
'''Descriptions: 7/10'''<br />
<br />
Disclaimer: I have unrealistic standards for frequency of roomdesc responses.<br />
<br />
The descriptions and items here are good, but not incredible: The first few rooms heading west from the Zigolis Swamp entrance have one interesting things to find, and the lead-in to the main spidery area has some neat descriptors, but the swampy rooms are sparsely described and there are a few things that I was curious about but have no description:<br />
<br />
The spidery cave area has a few things like eggsacs and captured prey that feel like great excuses for extra flavor/detail/interaction but go unused.<br />
<br />
Speaking of the spiders: Phase Spiders, Sword Spiders, and the miniboss spider all attack when 'talk'ed to. This is a common enough result, but there's no extra flavor text about their reaction before/in the process of attacking, like some other mobs in other areas. Worth adding?<br />
<br />
The Ranch Entrance room has a few interesting tidbits that could have more detail (gate and vines/briers, mostly), and the desc for the orchard's olive press is missing the "bucket" keyword used as part of the object in the room desc.<br />
<br />
Really, everything here is functional and present, just a bit sparse after the first few rooms.<br />
<br />
'''Balance: N/A'''; estimates below<br />
<br />
I can't comment on combat balance due to being, uh, well out of the level range. Sorry. But I can try to comment on the loot:<br />
<br />
Item Balls and their occasional Surprise are pretty neat. A fair resource for early-game supplies. I think these are good as they are.<br />
<br />
What I've seen of drops from the Spiders are interesting and appropriate for the level. I like it. Although I am confused by the sword drop being an exotic weapon...? well, it does make some sense under the circumstances.<br />
<br />
But I don't like the current version of the Manly Fish. The level 0 equipment that they carry and drop produces lots of heavy, low-value clutter you're really better off ditching, but ends up in every body of one of the most frequent mobs in the area. Very annoying. It's tempting to let them drop generic level 5 gear as from Crystia so the loot is worth lugging off to sell or use if you get the right kind, but I don't know if that would make them too dangerous or lucrative for the area.<br />
On the upside: their bonus wand drop is wonderful on multiple levels.<br />
<br />
That said, after writing that, I encountered a few level 6 equipment drops from the Beastman Mender, Clockwork Knight, and Territorial Ossier that are comparable in effectiveness and lower in price - aside from the increased hassle to obtain them, I think these are nice.<br />
<br />
In terms of aesthetics and combat complexity, I do like that the Mender/Clockwork Knight spawn and operate as a group - there are very few team battles in the cleft that don't turn into a dogpile or utter chaos. Probably really easy to break, though...<br />
<br />
'''Attractions: 3/10'''<br />
<br />
Faron Woods is... nice to check out once, but has no real staying power. The main quest and descriptions are nice and it's good for resupplying at low levels at a low cost, but once you've seen it once there's not much reason to look back. The other loot and mob density in Faron are both poor, making it lackluster for XP and unreliable for equipment pickups - in a lot of ways it's better to just level up elsewhere and catch up on gear in a higher-level zone. Faron Woods is an area you pass through, not an area you stay in. Do we want to change that?<br />
<br />
The fact that nothing here carries silver to loot doesn't help, either.<br />
<br />
That said: The Lantern Refill for sale is a very unique attraction. I don't know of any other source of Phlogiston currently available, though I suspect it was implemented as a qskill without being finalized in helpfiles or wiki data. From the current casting level of 1 I saw it restore 12 hours to a level 80 light source... I don't know whether level affects its potency or not, but I do like having the option available for recharging rare lights. With the risks announced in the helpfile, of course. It's very distinctive, but it doesn't feel like expanding the scale of this is an appropriate way to make Faron stand out more.<br />
<br />
'''Connections: 9/10'''<br />
<br />
For theme and environments the surrounding areas all work well. My only complaint would be the transition between Faron Woods and Midnight Gardens being abrupt - a little more hint about what you're heading into/out of in the one or two last Faron Woods rooms would be nice. I wish I could better navigate the route to reach Carnival Night Zone vs. Midnight Gardens, but I think that's my own fault...<br />
<br />
'''Bugs/Exploits:''' (because this is me)<br />
<br />
Corporal Wolfdog is involved in quests here, but can be attacked and is not immune to Summon/Charm. He's currently being held hostage in my player house. (Kind of.)<br />
<br />
As much as I love the idea of having an actually coordinated opponent group, neither the Beastman Mender or the Clockwork Knight are immune to summon/charm. Haven't seen what happens if you drag one off without the other but I doubt it's been accounted for.<br />
<br />
**Made above mobs imm charm/summon<br />
<br />
'''Overall: C+'''<br />
<br />
Faron Woods is in a messy spot: The only other 5-10 area near Viorar is Luon Trail, so it ends up with little competition for the time for equipment, supplies, and quests. However, it's also a short-lived path from point A to point B for several other zones in the area, so it can't afford to be very complicated or involved, either. That in mind: It looks like it's functional as a resupply/minor loot area while going for more serious battles in Kakariko or Midnight Gardens, possibly with curbstomps in Zigolis Swamp. Where Luon Trail is well-populated and provides food and water with reliable silver income, Faron provides healing items and equipment from combat without questing. It's servicable as an intermediary area, but is a bit lacking in, ah, spice to make it stand out and be worth sticking around in.<br />
<br />
<br />
----<br />
<br />
<br />
[[Category:Area of the Month|*]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Flags_Compendium&diff=2125Flags Compendium2018-09-26T21:09:15Z<p>Pascal: /* EXTRA3 FLAGS */</p>
<hr />
<div>==FLAGS COMPENDIUM==<br />
===ROOM FLAGS===<br />
{|<br />
|dark || Need a light source <br />
|-<br />
|always_night || Room is always night; sun never rises, 'look sky' always shows stars.<br />
|-<br />
|no_mob || Mobs won't wander in here. Mobs on scripts and charmies are unaffected<br />
|-<br />
|indoors || Won't see [[weather]] or [[time|sunrise/set messages]]<br />
|-<br />
|private || Two people at a time<br />
|-<br />
|arena || Players don't leave corpses or lose XP when they die. Players also don't lose XP for fleeing combat.<br />
|-<br />
|safe || No fighting allowed<br />
|-<br />
|solitary || One person at a time<br />
|-<br />
|pet_shop || Can buy pets here. Pet cost is the 'wealth' of the mob, but purchased pets will be flat broke. Builders should reset the pet mobs into next room vnum.<br />
|-<br />
|no_recall || Can't recall from here<br />
|-<br />
|imp_only || MTS only<br />
|-<br />
|gods_only || Staff only<br />
|-<br />
|heroes_only || Also Staff only<br />
|-<br />
|newbies_only || Level 5 or less only<br />
|-<br />
|law || Prevents use of Charm, Tame, and Hypnotize spells (for some reason). Other stock ROM effects have been commented out.<br />
|-<br />
|nowhere || Can't Scan into this room<br />
|-<br />
|wilderness || Was supposed to involve some sort of overworld map? Doesn't do anything now.<br />
|-<br />
|overgrown_1 || Room has +1 level of overgrowth.<br />
|-<br />
|overgrown_2 || Room has +2 levels of overgrowth. This can stack with overgrown_1.<br />
|-<br />
|always_day || Room is always day; sun never sets, 'look sky' shows the sun.<br />
|-<br />
|lit || Room is always lit, don't require a light.<br />
|}<br />
====SECTOR====<br />
{|<br />
!Sector !! Movement Rate !! Properties !! Geomance Element !! Dance Element<br />
|-<br />
|Inside || 4 || Stays lit at night || Pierce || No effect<br />
|-<br />
|City || 4 || Stays lit at night || Bash || No effect<br />
|-<br />
|Field || 4 || || Slash || Pierce<br />
|-<br />
|Forest || 6 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Hills || 6 || || Slash || Pierce<br />
|-<br />
|Mountain || 8 || || Earth || Earth<br />
|-<br />
|Water (swim) || 4 || || Water || Water<br />
|-<br />
|Water (noswim) || 8 || Can't enter without a boat or the Swim affect || Water || Water<br />
|-<br />
|Unused || 1 || || Wind || No effect<br />
|-<br />
|Air || 4 || Can't enter without the Float affect || Wind || Wind<br />
|-<br />
|Desert || 8 || || Earth || Wind<br />
|-<br />
|Rock || 4 || || Earth || Earth<br />
|-<br />
|Road || 4 || || Wind || No effect<br />
|-<br />
|Enter || 4 || || Wind || No effect<br />
|-<br />
|Snow || 8 || || Cold || Cold<br />
|-<br />
|Swamp || 8 || || Water || Earth<br />
|-<br />
|Jungle || 8 || Has 1 level of overgrowth || Wood || Earth<br />
|-<br />
|Ruins || 4 || || Bash || No effect <br />
|-<br />
|Mount2 || 16 || || Earth || No effect<br />
|-<br />
|Coastal || 4 || || Earth || Wind<br />
|-<br />
|Developed || 4 || || Bash || No effect <br />
|-<br />
|Void || 4 || || Wind || No effect<br />
|-<br />
|Lava || 8 || || Fire || Fire<br />
|}<br />
<br />
====[[Exits|EXITS]]====<br />
{|<br />
|door || Exit has a door -- Required for most other exit flags<br />
|-<br />
|closed || Door resets to closed<br />
|-<br />
|locked || Door resets to locked<br />
|-<br />
|pickproof || Door can't be picked<br />
|-<br />
|nopass || Door can't be Pass Door'd<br />
|-<br />
|easy || Pick Lock doesn't take many tries<br />
|-<br />
|hard || Pick Lock takes a few tries<br />
|-<br />
|infuriating || Keep pickin'<br />
|-<br />
|noclose || Door can't be closed<br />
|-<br />
|nolock || Door can't be locked<br />
|-<br />
|hidden || Exit can't be seen by normal means<br />
|-<br />
|swim || Only players who can fly or swim, or are on a flying or seaworthy [[vehicle]] can pass.<br />
|-<br />
|fly || Only players who can fly or are on a flying [[vehicle]] can pass.<br />
|}<br />
<br />
===MOB FLAGS===<br />
*Mobs with the None [[damage type]] will randomly have Slash, Pound, or Pierce.<br />
<br />
====FORM FLAGS====<br />
Most of these don't do anything. The ones that have a coded effect are listed below!<br />
{|<br />
|edible || Mob's parts are edible, and the corpse can be butchered into meat.<br />
|-<br />
|poison || Mob's edible parts are poisonous, and meat butchered from the corpse will be poisoned. Bloodsucking will poison the bloodsucker.<br />
|-<br />
|instant_decay || Mob doesn't leave a corpse at all.<br />
|-<br />
|animal || Mob is affected by the Tame spell<br />
|-<br />
| || Mobs with any of the mammal, bird, reptile, amphibian, fish, or snake form flags can also be Tamed.<br />
|-<br />
|sentient || Mob is affected by the Hypnotize spell and can be haggled with if it's a shopkeeper.<br />
|-<br />
|cold_blood || Mob has blood that can be bloodsuck'd.<br />
|-<br />
|warm_blood || Mob can be seen in the dark by characters with Infrared and can be bloodsuck'd.<br />
|}<br />
<br />
====PART FLAGS / WEARLOCS====<br />
Mob parts determine what equipment it can wear.<br />
<br />
{| <br />
! Wearloc !! Required Part flag<br />
|-<br />
|take || none<br />
|-<br />
|finger || fingers<br />
|-<br />
|neck || head<br />
|-<br />
|body || guts<br />
|-<br />
|head || head<br />
|-<br />
|legs || legs<br />
|-<br />
|feet || feet<br />
|-<br />
|hands || hands<br />
|-<br />
|arms || hands<br />
|-<br />
|shield || hands<br />
|-<br />
|about || guts<br />
|-<br />
|waist || legs<br />
|-<br />
|wrist || hands<br />
|-<br />
|shoulders || head<br />
|-<br />
|wield || hands<br />
|-<br />
|hold || hands<br />
|-<br />
|nosac || not actually a wearloc<br />
|-<br />
|wearfloat || none<br />
|-<br />
|face || head<br />
|}<br />
<br />
* The Brawling warrior style has special attacks that only execute if the opponent has certain parts; eye, tail, feet, or arms.<br />
* The guts, head, heart, arms, legs, and brains parts can cause dismembered mob organs to be created when the mob dies.<br />
* A mob requires the brains part in order to take any damage from the Brainbuster spell.<br />
* '''A mob without hands cannot hold items, use weapons, or equip shields.'''<br />
* Items which do not have the Take flag can't be sacrificed, so it is redundant to put nosac on these items also.<br />
* Items without a Take flag can't be held by players or mobs at all. Avoid resetting these onto mobs or trying to have mobs oload them.<br />
<br />
====ACT FLAGS====<br />
{|<br />
|sentinel || Mob won't wander between rooms (although it can still move if instructed to by an mprog).<br />
|-<br />
|scavenger || Mob will pick up takeable objects in the room, starting with the most valuable.<br />
|-<br />
|inert || Mob can't be seen in the room (but can still be interacted with).<br />
|-<br />
|omnisight || Mob can see everyone despite invisibility etc but can't necessarily see in the dark.<br />
|-<br />
|aggressive || Doesn't do anything; the code for this function has been commented out.<br />
|-<br />
|stay_area || Mob won't wander outside the area it was reset into.<br />
|-<br />
|wimpy || Mob will try to flee from combat at 20% hp or less.<br />
|-<br />
|pet || Mob is a pet? Probably reserved for pet code. Don't use this.<br />
|-<br />
|train || Players can Train at this mob -- defunct<br />
|-<br />
|practice || Players can Practice at this mob -- defunct<br />
|-<br />
|passive || Mob doesn't fight back with autoattacks, its current health isn't visible when you 'look' at it, nor will Peek work on it.<br />
|-<br />
|hyper || Mob wanders around real fast.<br />
|-<br />
|visdeath || Mob can only be seen by immortals and can't be interacted with by players.<br />
|-<br />
|mage || Mob gets -5 to Saves<br />
|-<br />
|thief || Mob has the Smokescreen skill<br />
|-<br />
|warrior || Mob has the Shield Block skill<br />
|-<br />
|noalign || Mob won't affect player alignment at all when killed.<br />
|-<br />
|nopurge || Mob can't be purged by immortals (the Mob Purge command from a mob can still affect these).<br />
|-<br />
|outdoors || Mob won't wander into Indoor flagged rooms.<br />
|-<br />
|indoors || Mob won't wander outdoors.<br />
|-<br />
|healer || Mob offers hardcoded heal-for-cash services (EG Selan).<br />
|-<br />
|gain || Doesn't do anything -- in stock ROM allows for gaining new skills.<br />
|-<br />
|update_always || Mob does things even when no player in the area.<br />
|-<br />
|changer || Mob is a [[bank]].<br />
|-<br />
|hyper_res || Mob takes 1/4 damage from sources it resists (instead of 2/3) and double damage from sources it's vulnerable to (instead of 3/2).<br />
|}<br />
<br />
Notes on wandering mobs:<br />
* When mobs try to move, they make three attempts. Each attempt, they pick a random exit in the room and then look at it more closely. If they can't move, they try again. If they can move, they do.<br />
* Mobs will not wander through closed doors (even if affected by pass_door) or into no_mob rooms.<br />
* Mobs with the stay_area flag will not wander between areas (which area its' vnum is in doesn't matter).<br />
* Mobs with the Outdoors flag won't wander into Indoors rooms. Mobs with the Indoors flag won't wander into rooms that aren't flagged Indoors.<br />
* Only Flying mobs will move into Air sector rooms. Only mobs with the Swim affect will move into any sort of water room. <br />
** A mob without the Swim affect ''will'' attempt to move into a noswim sector room (and fail to move, unless it has a boat object), but will not even try to get into a swim sector room unless it has the affect (even though it would be allowed to move there if it tried). This doesn't make a lot of sense but that's how it is.<br />
<br />
====ACT2 FLAGS====<br />
{|<br />
|doublexp || Mob gives double XP.<br />
|-<br />
|halfxp || Mob gives half XP.<br />
|-<br />
|noxp || Mob gives no XP.<br />
|-<br />
|noparts || Mob leaves no parts when killed.<br />
|-<br />
|sociable || Mob talks to or slaps people that use socials on it.<br />
|-<br />
|aquatic || Mob won't wander outside water rooms.<br />
|-<br />
|xpandahalf || Mob gives 1.5x XP.<br />
|-<br />
|adept || Mob uses skills at 100% (instead of 75%).<br />
|-<br />
|inept || Mob uses skills at 50% (instead of 75%).<br />
|-<br />
|carryall || Mob has no weight or item# limits.<br />
|-<br />
|priority || Mob will be targetted first by opponents with the AI_1 flag.<br />
|-<br />
|antihyper || Mob wanders especially slowly.<br />
|-<br />
|parsename || Mob will have a unique name as its first name when it resets.<br />
|-<br />
|noattack || Mob can't be attacked by anyone.<br />
|-<br />
|necromancer || Mob offers corpse retrieval for cash services, as Xzar, Caroline, etc.<br />
|-<br />
|raidmob || Mob can be attacked by anyone with no regard to 'kill stealing'.<br />
|-<br />
|carrynone || Mob can't pick up or be given items<br />
|-<br />
|passivelite || Mob won't auto-attack but still has visible health and such<br />
|-<br />
|ally || Is treated as a PC for some attack-safety purposes -- EG Ally mobs won't hit other Ally mobs with area attacks<br />
|-<br />
|shopkeepitems || Shop will not slowly discard items sold to it.<br />
|}<br />
<br />
====OFF FLAGS====<br />
A lot of these are affected by the adept/inept Act flags<br />
{|<br />
|area_attack || Mob hits everything that's fighting it with its normal attacks.<br />
|-<br />
|backstab || Mob is capable of using the Backstab skill, and would if it aggroed, but mobs don't aggro, so it does nothing.<br />
|-<br />
|bash || Mob has a 12.5% chance of using the bash skill, if it's not lagged.<br />
|-<br />
|berserk || Mob has a 12.5% chance of using the berserk skill, if it's not lagged and isn't already berserk.<br />
|-<br />
|disarm || Mob has a 12.5% chance of using the disarm skill, if it's not lagged. The mob needs a [[weapon]].<br />
|-<br />
|dodge || Mob can dodge melee attacks as a player with the dodge skill at 75%.<br />
|-<br />
|fade || Doesn't do anything.<br />
|-<br />
|fast || Mob attacks twice always, doesn't stack with Haste. Mob will ignore Slow if affected. Mob gets +2 DEX when spawned.<br />
|-<br />
|kick || Mob has a 12.5% chance of using the kick skill, if it's not lagged.<br />
|-<br />
|dirt_kick || Mob has a 12.5% chance of using the dirt kick skill, if it's not lagged.<br />
|-<br />
|parry || Mob can parry attacks; works half as often with no [[weapon]].<br />
|-<br />
|rescue || Mob will try to rescue the target of its target, if that target is at 50% hp or less.<br />
|-<br />
|tail || Mob has a 12.5% chance of.. not doing anything (the code for this attack is commented out).<br />
|-<br />
|trip || Mob has a 12.5% chance of using the trip skill, if it's not lagged.<br />
|-<br />
|crush || Mob has a 12.5% chance of using the smash skill, if it's not lagged.<br />
|-<br />
|assist_all || Mob will assist all other '''mobs''' that it sees fighting.<br />
|-<br />
|assist_align || Mob will assist other mobs with a similar alignment, chunked out to good/neutral/evil.<br />
|-<br />
|assist_race || Mob will assist other mobs of the same race.<br />
|-<br />
|assist_players || Mob will assist players as long as the player isn't more than 5 levels above them. This has precedence over the other assist flags.<br />
|-<br />
|assist_leader || If following someone, mob will assist its leader.<br />
|-<br />
|assist_vnum || Mob will assist mobs of the same vnum.<br />
|-<br />
|second_attack || Mob has the 2x-Cut skill.<br />
|-<br />
|third_attack || Mob has the 3x-Cut skill.<br />
|-<br />
|ai_retargeting || Mob will aggro onto players that have recently fled from it, and selectively hit targets with the Priority act flag. If the mob's attacks are ineffective, it will re-target randomly to another member of the same group.<br />
|-<br />
|ai_flees || Mob will flee from sandstorms, flurries, miasmas, wildfires, etc unless it's immune to the appropriate damage type.<br />
|-<br />
|ai_rests || Mob will rest when injured (hp<50%), stand up when it's recovered (hp>75%).<br />
|-<br />
|}<br />
* Only one of the various 12.5% flags can trigger in any given round. A mob will all eight will try to use one (and only one) every single round.<br />
<br />
====BEHAV FLAGS====<br />
{|<br />
|random_innate || Mob randomly has one of the 6 elemental innates. This creates one resistance and one vulnerability.<br />
|-<br />
|rand_phys_resist || Mob randomly resists one of bashing, slashing, or piercing.<br />
|-<br />
|rand_misc_resist || Mob randomly resists one or two non-physical elements.<br />
|}<br />
<br />
====AFFECT FLAGS====<br />
{|<br />
|blind || Character can't see anything! Mobs ignore this flag so their mobprogs work<br />
<br />
|-<br />
|invisible || Character can only be seen and targetted by things with detect_invis.<br />
|-<br />
|detect_evil || Character sees evil objects and characters with a red aura.<br />
|-<br />
|detect_invis || Character can see invisible objects and characters, and knows they're invisible.<br />
|-<br />
|detect_magic || Character sees a blue aura around magical objects.<br />
|-<br />
|detect_hidden || Character can see hidden objects and characters, and knows they're hidden.<br />
|-<br />
|detect_good || Character sees good objects and characters with a gold aura.<br />
|-<br />
|sanctuary || Character is permanently under the effects of Nayru's Love (half damage from everything).<br />
|-<br />
|faerie_fire || Character has a pink aura. Negates invisibility.<br />
|-<br />
|infrared || Character can see warm_blood mobs in the dark.<br />
|-<br />
|curse || Character is flagged as cursed. All skill effectiveness is reduced by 15% while this flag is applied, but the character is immune to the Curse spell.<br />
|-<br />
|solidified || Character is completely frozen!<br />
|-<br />
|poison || Character is flagged as poisoned. This flag has no affect on stats but the character can't be poisoned again. Regeneration is decreased while this flag is applied, however.<br />
|-<br />
|protect_evil || Character takes 2/3 damage from evil foes.<br />
|-<br />
|protect_good || Character takes 2/3 damage from good foes.<br />
|-<br />
|sneak || Character doesn't generate echoes when moving from room to room. Triggers GRALL but not GREET progs.<br />
|-<br />
|hide || Character is hiding. Using any command removes this effect.<br />
|-<br />
|sleep || Character is under the effects of ''permanent'' magical sleep!!<br />
|-<br />
|charm || Character is under the effects of a Charm spell. Don't use.<br />
|-<br />
|flying || Character is flying: reduced MV costs everywhere (by 1 per room), can travel into air sector rooms, and doesn't need a boat to travel into noswim sector rooms. Also immune to Trip and Earthquake.<br />
|-<br />
|pass_door || Character can walk through some closed doors.<br />
|-<br />
|haste || Character is under the effects of Haste: '''always''' gets exactly 1 extra attack in combat, but regenerates at half speed. <br />
|-<br />
|calm || Character is under the effects of the Calm spell. Character can't use berserk.<br />
|-<br />
|plague || Character is flagged as plagued. Regeneration is decreased but the player can't be hit with the Bio 2 spell.<br />
|-<br />
|locusts || Character is a swarm of locusts per the Plague Swarm spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|dark_vision || Character can see anything in any kind of darkness without a light source.<br />
|-<br />
|berserk || Character is under the effects of Berserk! Character can't cast spells, everything the character sees is red, and they get a 50% penalty to all saving throws.<br />
|-<br />
|swim || Character doesn't need a boat to enter noswim sector rooms.<br />
|-<br />
|regeneration || Character regenerates HP twice as fast!<br />
|-<br />
|slow || Character has a chance to simply not attack during combat. 2x-cut and 3x-cut chances are reduced dramatically. Ignored if the mob is flagged off_fast. Character also regenerates at half speed AND spends more MV when traveling.<br />
|-<br />
|scarecrow || Character is affected by the Scarecrow spell -- can't eat, drink, or move, and melee attacks do reduced damage.<br />
|}<br />
<br />
====AFFECT2 FLAGS====<br />
{|<br />
|focus || double mana regeneration<br />
|-<br />
|motivation || slight movement regeneration<br />
|-<br />
|theatrical || takes damage when receiving an affect<br />
|-<br />
|frenzy || grants extra attack<br />
|-<br />
|vampirism || ??<br />
|-<br />
|paralysis|| ??<br />
|-<br />
|fast|| no command lag when moving rooms (like vehicle fast)<br />
|}<br />
<br />
====SHIELD FLAGS====<br />
{|<br />
|charge || Character does 1.5x damage with all applicable spells. DOES NOT DISSIPATE UNLESS IT IS APPLIED BY THE CHARGE SPELL.<br />
|-<br />
|sabotaged || Character takes damage when using skills or spells.<br />
|-<br />
|hallucinating || Character is under the effects of the Mushroomize spell; all MUD output turns wacky.<br />
|-<br />
|terrified || Character may cower helplessly in combat, with a greater chance is the foe's level is higher than the character's. Also makes the character try to flee.<br />
|-<br />
|haunted || Character is tormented by minighosts.<br />
|-<br />
|confused || Character hits itself sometimes in combat.<br />
|-<br />
|stat enhancement || Character is under the effects of one of Sage Aura, Brilliance, Limber, Valor, or Vigor/Warcry and can't be affected by another one.<br />
|-<br />
|ice shield || Returns 20 to 30% of melee damage as bash-type damage<br />
|-<br />
|thorn shield || Returns 20 to 30% of melee damage as pierce-type damage<br />
|-<br />
|crystal shield || Returns 20 to 30% of melee damage as slash-type damage<br />
|-<br />
|osmosis || Character loses MP steadily. Also decreases MP regeneration.<br />
|-<br />
|volta || Character does not auto-attack but has double normal dodge chances.<br />
|-<br />
|manashield || Character has Mana Shield permanently up. It will give the 'your shield broke' message with every attack if they're at 0MP but they'll still take full damage.<br />
|-<br />
|kamikaze || Character is going to Detonate. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|zeal || Character fails all saving throws but receives a bonus to damage for each bad affect<br />
|-<br />
|bleeding || Character loses HP steadily. Some types of bleeding make you bleed worse than others!<br />
|-<br />
|undead || Character is a zombie with a relentless hunger for delicious brains. All text is dark gray, healing spells do damage instead of healing, and the poor bastard doesn't necessarily die when they drop below 0hp! This is distinct from the undead form flag.<br />
|-<br />
|oozaru form || Character is an oozaru and can't cast spells.<br />
|-<br />
|double image || Character has a double image. It will take one attack and then vanish.<br />
|-<br />
|ink || Character has been inked. Display is all goofed up with large black splotches.<br />
|-<br />
|seraph form || Character has seraph form and can't cast spells.<br />
|-<br />
|reflect || Spells targetted at the character bounce back the wrong way<br />
|-<br />
|surefire casting || Character has surecasting on.<br />
|-<br />
|jinx || Character has a 33% chance of dropping any [[weapon]] they're wielding in any combat round.<br />
|-<br />
|leechseed || Character is under the effects of the Leech Seed spell. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bees || Character is covered in bees which deal periodic damage.<br />
|-<br />
|choke || Character is affected by Choke and casts spells at 3/4 the normal strength.<br />
|-<br />
|endure || Character cannot be reduced below 1hp.<br />
|-<br />
|sheltered || Character is being sheltered by a friendly Templar. *Cannot be set on a mob's template or applied by an item.<br />
|-<br />
|bide || Character is using the skill Bide. *Cannot be set on a mob's template or applied by an item.<br />
|}<br />
<br />
Some of these affects can't be applied to a mob's template, only by spells; homing attack, stat enhancement, extension, kamikaze, short term combat effect, oozaru form, double image, seraph form, Jumi empathy, surefire casting, and leechseed.<br />
<br />
===OBJ FLAGS===<br />
For more details on object types see [[Flags Compendium/Obj Types]]<br />
<br />
{|<br />
|[[light]] || Light sources, go in a special 'light' slot when equipped no matter what wear flags you use<br />
|-<br />
|[[scroll]] || Can be recited or read to cast 1-4 spells on a target. Works from base inventory, consumed when used, uses [[Artifice]] skill.<br />
|-<br />
|[[wand]] || Can be zapped or used to cast 1 spell a set number of times on a target. Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[staff]] || Can be brandished or used to cast 1 spell a set number of times on all targets in a room! Must be equipped, any slot is OK. Uses [[Artifice]] skill. Explodes when out of charges unless NOEXPLODE extra flag is set.<br />
|-<br />
|[[weapon]] || Changes wearer's melee autoattack damage to the type and amount specified in the object. Must be in the Wield slot to work.<br />
|-<br />
|[[treasure]] || No inherent properties, reserved for salable loot.<br />
|-<br />
|armor || Modifies wearer's armor values. Can be equipped anywhere.<br />
|-<br />
|[[potion]] || Can be quaffed or drunk to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|-<br />
|[[furniture]] || Various flags allow characters to sit, rest, stand, or sleep on, in, or at these objects. Recovery rates can be modified as well.<br />
|-<br />
|[[trash]] || No inherent properties, reserved for nonsalable loot.<br />
|-<br />
|[[container]] || Object that holds other objects. Can be closable/lockable like a door.<br />
|-<br />
|[[drinkcontainer]] || Holds a set quantity of a certain [[liquid]]. Liquids can be replaced with different liquids. Disappears when empty unless NOEXPLODE is set.<br />
|-<br />
|[[key]] || Object vanishes on logout. Has no other properties.<br />
|- <br />
|[[food]] || Can be eaten for food/full value and cast 1 spell on the eater.<br />
|- <br />
|[[money]] || Is abstracted into current wealth when picked up by a player. Dropped wealth turns into a money object. The Priest class can sacrifice money to recover mana for 1 MP per 50 silver.<br />
|- <br />
|boat || Can be equipped or in base inventory for players to move in water rooms. Defunct.<br />
|- <br />
|npccorpse || NPC [[Corpse]]. Reserved.<br />
|- <br />
|[[fountain]] || Like a drinkcontainer but the [[liquid]] inside can't be poisoned. Drinkcontainers can also be 'fill'ed from it.<br />
|- <br />
|[[pill]] || Can be eaten to cast 1-4 spells on the drinker. Works from base inventory, consumed when used.<br />
|- <br />
|protect || Uncoded junk. Don't use.<br />
|- <br />
|map || Uncoded junk. Don't use.<br />
|- <br />
|[[portal]] || Objects that can be 'entered' to take the character to a set room. Can be closable/lockable like a door.<br />
|- <br />
|warpstone || Used to be necessary for the Nexus spell.<br />
|- <br />
|roomkey || Uncoded junk. Don't use.<br />
|- <br />
|gem || Uncoded junk. Don't use.<br />
|- <br />
|[[jewelry]] || No inherent properties. Used for equippables that aren't armor.<br />
|- <br />
|[[Event Item|event]] || An object with both charges and cooldown capability, which executes an mprog when 'zap'ped or 'use'd. Uses [[Artifice]] skill.<br />
|- <br />
|slotmachine || <s>Type "Game slots" at a slot machine to spin the wheel. Slot machines can have their cost and jackpot size specified in the object template.</s> Just kidding! Disabled.<br />
|- <br />
|gun || Uncoded junk. Don't use.<br />
|- <br />
|ammo || Uncoded junk. Don't use.<br />
|- <br />
|[[vehicle]] || Vehicles allow players to consume less movement points as they travel, move faster, and/or travel to rooms they can't enter on foot.<br />
|- <br />
|exit || Uncoded junk. Don't use. Not the same as a real [[exit]].<br />
|- <br />
|[[rod]] || Can be zapped or used to cast 1 spell on a target with a set delay between uses. Must be equipped, any slot is OK. Uses [[Artifice]] skill.<br />
|}<br />
====EXTRA FLAGS====<br />
{|<br />
|glow || Item can be seen in the dark, shows (glowing) before its short desc<br />
|-<br />
|hum || Item shows (Humming) before its short desc<br />
|-<br />
|norecharge || Wand, staff, rod, or event can't be recharged with the Recharge spell.<br />
|-<br />
|autoconsume || Item is automatically used as soon as it's picked up off the ground. Works with [[potions]], [[pills]], and [[artifice]] items.<br />
|-<br />
|evil || Item has a red aura if you can detect evil, can be removed with Bless.<br />
|-<br />
|invis || Item can only be seen if you have detect invis, and shows (Invis) if you can<br />
|-<br />
|magic || Item shows as magic if you can detect magic<br />
|-<br />
|nodrop || Item can't be dropped, can be removed with Bless<br />
|-<br />
|bless || Item has a blue aura if you can detect good, can't be poisoned, and is a little easier to enchant. Is removed by Curse.<br />
|-<br />
|noremove || Item can't be removed. This flag is removed by uncursing<br />
|-<br />
|inventory || Item is part of a shopkeeper's inventory and will be sold with infinite quantity left. Also evaporates when the holder dies, like rotdeath.<br />
|-<br />
|nopurge || Item can't be purged. Use sparingly!<br />
|-<br />
|rotdeath || Item poofs when whoever is holding it dies. If a mob dies with one of these, it will vanish.<br />
|-<br />
|visdeath || Item can only be seen by immortals<br />
|-<br />
|uncounted || Item doesn't count against the holder's carry number or weight capacities.<br />
|-<br />
|nonmetal || Item is unaffected by Heat Metal<br />
|-<br />
|meltdrop || Item poofs when dropped or stolen. If a mob dies with one of these, it will appear in the room. <br />
|-<br />
|decaying || Item loses 1 condition per minute, then disintegrates.<br />
|-<br />
|sellextract || Item poofs when sold to shopkeeper -- doesn't show up in their inventory<br />
|-<br />
|nodestroy || (AKA burn_proof in the code for some reason) Item can't be poisoned, and can't be destroyed by various item-destroying affects (which I think are disabled)<br />
|-<br />
|nouncurse || Item can't be uncursed. (nodrop, noremove flags)<br />
|-<br />
|runic || Unused<br />
|-<br />
|adhesive || Item stays with a player, not on their corpse<br />
|-<br />
|nochk || [[Wand]], [[Scroll]], [[Staff]], [[Rod]], and [[Event Item|Event]] items with this flag won't check a character's [[artifice]] skill when used, but just always work<br />
|-<br />
|noremort || Item can't be carried through a remort<br />
|-<br />
|inert || Item doesn't appear in rooms its in<br />
|-<br />
|noexplode || Wand and staff type item won't disintegrate when their charges are used up. Drinkcontainers won't poof when empty.<br />
|}<br />
<br />
====EXTRA2 FLAGS====<br />
{|<br />
|antihuman || Can't be equipped by Human race<br />
|-<br />
|antimoogle || Can't be equipped by Moogle race<br />
|-<br />
|antisaiyan || Can't be equipped by Saiyan race<br />
|-<br />
|antiesper || Can't be equipped by Esper race<br />
|-<br />
|antihylian || Can't be equipped by Hylian race<br />
|-<br />
|antikokiri || Can't be equipped by Kokiri race<br />
|-<br />
|antigiganto || Can't be equipped by Giganto race<br />
|-<br />
|antimatango || Can't be equipped by Matango race<br />
|-<br />
|antireploid || Can't be equipped by Reploid race<br />
|-<br />
|antikoopa || Can't be equipped by Koopa race<br />
|-<br />
|antipmpkn || Can't be equipped by Pumpkinhead race<br />
|-<br />
|antiknight || Can't be equipped by Knight class<br />
|-<br />
|antiwarrior || Can't be equipped by Warrior class<br />
|-<br />
|antithief || Can't be equipped by Thief class<br />
|-<br />
|antiwizard || Can't be equipped by Wizard class<br />
|-<br />
|antipriest || Can't be equipped by Priest class<br />
|-<br />
|antigeomancer || Can't be equipped by Geomancer class<br />
|-<br />
|antisummoner || Can't be equipped by Summoner class<br />
|-<br />
|antifemale || Can't be equipped by female characters<br />
|-<br />
|antimale || Can't be equipped by male characters<br />
|-<br />
|antineuter || Can't be equipped by sexless characters<br />
|-<br />
|cursed || Item becomes noremove when equipped<br />
|-<br />
|unique || Characters can't pick up one of these if they already have one.<br />
|-<br />
|remortable || Item was carried through a remort and won't vanish on logout if it's out of the player's level range.<br />
|-<br />
|antinu || Can't be equipped by Nu race<br />
|-<br />
|antikirby || Can't be equipped by Kirby race<br />
|-<br />
|antilobsterman || Can't be equipped by Lobster race<br />
|-<br />
|antiranboob || Can't be equipped by Ranboob race<br />
|-<br />
|antijumi || Can't be equipped by Jumi race<br />
|-<br />
|antidancer || Can't be equipped by Dancer class<br />
|-<br />
|antimob || Can't be equipped by mobs<br />
|}<br />
<br />
* NOTE: Old classes are affected by antiwizard, etc, just as new ones are.<br />
<br />
====EXTRA3 FLAGS====<br />
{|<br />
|exalted || Can only be equipped by players who have remorted at least once (if remort $n >= 2)<br />
|-<br />
|heroic || Can only be equipped by players who have remorted at least five times (if remort $n >= 6)<br />
|-<br />
|epic|| Can only be equipped by players who have remorted at least ten times (if remort $n >= 11)<br />
|-<br />
|perishable|| Object will disappear on logout if the character is not in the object's source area.<br />
|-<br />
|owned|| Object cannot be equipped unless it shares all name keywords with the character.<br />
|}<br />
<br />
* NOTE 1: Objects restricted by number of remorts will also not be saved to unqualified player files when logging out, UNLESS they are somehow also flagged as remortable.<br />
* NOTE 2: Mobiles cannot remort, so exalted, heroic, and epic objects are effectively also antimob.<br />
<br />
===AREA EXFLAGS===<br />
{|<br />
|visdeath || Area is not visible on 'areas' display.<br />
|-<br />
|norecall || No recalling anywhere within this area.<br />
|-<br />
|nosummon || No summoning within this area.<br />
|-<br />
|noweather || Weather is always 0 wind, 0 sky, and the 'weather' command fails with no map displayed.<br />
|}<br />
<br />
[[Category:Technical Information]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=Booster_Tower&diff=2124Booster Tower2018-09-26T19:45:30Z<p>Pascal: </p>
<hr />
<div>{{AreaStats | color = #FF6699 | picture = boostertower.png | name = Booster Tower | source = Super Mario RPG | builder = dataAndrew, Ageatii, Benamas | level range = 16-20 | linked = Yes | caption = The lobby!}}<br />
<br />
Booster Tower is a wooden tower build along the north side of the road between [[Truce]] and [[Rocket Town]], owned by Booster. Due to the owner's fascination with magical toys and knack for hiring incompetent henchmen, the tower is full of monsters and treasure, making an excellent training ground for level 16-20 adventurers.<br />
<br />
== History ==<br />
<br />
'''324''' - Booster decides to move out of Truce's city limits because of their "anti-beetle hunting policy." He sells all his assets to construct a gaudy tower just outside of Truce.<br />
<br />
'''325''' - Booster Tower construction is complete. A huge party is thrown in the tower halls to commemorate the triumph - all of Truce and Rocket Town is invited. A freak accident involving a jump rope and a thousand stuffed-toy jigglypuffs cuts the party short.<br />
<br />
'''326''' - In one year, Booster is cited for 312 noise violations and 192 smell violations by Truce. When voluntarily coming to the [[Truce Council]] to address the violations, Booster catches a young woman (name withheld) who drunkenly fell out of her second story window. They immediately marry and go back to the tower, much to the dismay of her parents.<br />
<br />
'''327''' - After several conflicts with the woman's family and her return home, Booster signs the Bundt Contract with Truce. Truce has it's first peaceful night of sleep in 2 years.<br />
<br />
'''328''' - Another young woman, Valentina, falls out of the sky into Booster's arms, convinces Booster to marry her and give her partial ownership of the tower.<br />
<br />
== Sights ==<br />
<br />
=== Marrymore ===<br />
<br />
There is a town built entirely of large LEGOs hidden somewhere inside Booster Tower. It's a bright happy fun place and you need to crawl into a box to get there.<br />
<br />
== Travel ==<br />
<br />
Booster Tower is within walking distance from [[Truce]]! It is on the way through the road that connects Truce and Rocket Town.<br />
<br />
== Inhabitants ==<br />
<br />
=== Kamenbito ===<br />
<br />
Booster keeps a large staff of Spookums and Shyguys - small robed people who wear masks to cover their identities.<br />
Those kamenbito who Booster has the most fun with get promoted to Snifit status. There are currently Snifits 1 to 4.<br />
<br />
=== Magical Constructs ===<br />
<br />
Many weird creatures wander the halls of the tower, including Bob-ombs (walking bombs) and Remo-Con, (walking wood puppets). They just want to play, but they play hard.<br />
<br />
== Law, Government, and Politics ==<br />
<br />
Booster Tower is owned by Booster (70%) and Valentina (30%).<br />
<br />
After signing the Bundt Contract, Booster was allowed to run whatever operations he wanted inside his tower, as long as they didn't cause "public nuisance." Under the contract, Booster Tower receives annual visits from [[Truce]] to ensure that nothing -too- wacky is going on inside.<br />
<br />
== Quests ==<br />
Two kamenbito once discussed ideas on how to become Snifit 5 someday. They put together a list that would later be carried away by mischievous beetles: <br />
<br />
- Have you made it to the top floor?<br />
<br />
- Found Booster's lost item?<br />
<br />
- Bested a clown in a guessing game?<br />
<br />
- Helped the puppet ringers?<br />
<br />
== The Great Explorer Luigi Says ==<br />
[[file:luigi.jpg]]<br />
"Luigi is-a patient enough to wait for-a Blindness to pass on its own, but he always keeps-a few Oral Eyedrops from [[Truce]] handy just in case he needs them. Kamenbito shoot things at-a Luigi after attacking him, so he eats-a mushroom to stay healthy."<br />
<br />
[[Category:Areas]]</div>Pascalhttp://wiki.cleftofdimensions.net/index.php?title=September_2018:_Safari_Zone&diff=2121September 2018: Safari Zone2018-09-20T01:41:03Z<p>Pascal: </p>
<hr />
<div>Area of the Month for September 2018 is the [[Safari_Zone|Safari Zone]]!<br />
<br />
A template format for your review is below; click 'edit' at the top of the page, copy-pasta from the <nowiki>----</nowiki> to the next <nowiki>----</nowiki>, and fill in the gaps!<br />
<br />
('''''Yes,''''' a wiki account is required to edit the page and therefore post your review, but take heart: The wiki is hosted by the Cleft itself, not a third party!<br />
<br />
<br />
----<br />
<br />
'''Player: You!(Class/Level)'''<br />
<br />
'''Review Date(s): '''<br />
<br />
<br />
'''Descriptions: X/10'''<br />
<br />
How does the area's room descriptions(descs) work for you? Do they give you a good idea of the area? Do things that stand out in the desc and NEED explanation GET that, either from flavor text(extra-descs) or NPCs in the room or anything?<br />
<br />
What about mobiles(mobs) and their descriptions? Can you get a decent mental image of who or what this NPC/monster is? Do they respond when you talk or interact with them?<br />
<br />
Some areas have interact-able objects like fountains. Do they stack up well also?<br />
<br />
<br />
'''Balance: X/10 (OR N/A)'''<br />
<br />
(NOTE: combat will be most accurately gauged when your character is in the area's suggested level range.)<br />
<br />
If this area has combat, how does it feel? Does anything jump as horribly overpowered and impossible to deal with? What about the flipside, anything far too easy to beat? <br />
<br />
Are purchased or rewarded items at the appropriate strength levels? Is the effort required to obtain rewarded items reflected in their usefulness (or uniqueness and fancifulness)<br />
<br />
<br />
'''Attractions: X/10'''<br />
<br />
Why would you suggest someone come to this area?<br />
Is it just a good place to grind experience(lots of mobs)?<br />
Does the area provide a chunk of good gold and loot?<br />
<br />
What about the quests? Does this area's quests feel properly done, or is there some part of it that you feel needs work?<br />
<br />
For towns, are the shops good? Any other non-combative attraction for the area?<br />
<br />
<br />
'''Connections: X/10 '''<br />
<br />
How easily and well does this area connect to its nearby areas?<br />
Does it make sense thematically to be connected to the areas it is?<br />
<br />
<br />
'''Personal'''<br />
<br />
Any comments you'd like to make that you don't feel apply to the other sections can go here!<br />
<br />
<br />
<br />
----<br />
<br />
'''Player:''' Emouse (Dollmage, L100, ~5 remorts)<br />
<br />
'''Review Dates:''' 9/7/2018-9/8/2018<br />
<br />
'''Descriptions: 5/10'''<br />
<br />
The mobs in the Safari Zone are good, but not great: The lookdescs and combat progs are effective descriptions and show some personality, but outside of that the mobs are kinda lifeless. None of the pokemon have talkprogs to demonstrate non-violent interaction, there's no text while idle or interaction between pokemon in the wild, and Todd's involvement for his quest is... minimal. And easily sequence broken - you can walk straight to the Fearow and skip the rest of his requests. Of which I remember more than the one he currently makes, so I'm not sure if it's even operating as intended. You'd also think his enthusiasm would lead him to babble a lot about the pokemon in the region if prompted when following, but that's pure radio silence as well...<br />
<br />
Gotta say, the graffiti adds a lot of personality to the room descriptions. The river/pond region has a lot of little bonus descriptions that add life to the area... but the rest of the zone doesn't. The room descriptions in the caves and forest area are good, but there's little further details on items of interest from trying to 'look' at them, aside from one or two quest-related tidbits. Complete lack of detail on the Dustox colony in the forest and the various stalactites and water pools in the cave is saddening. It feels like the one N W W from the entrance of the caves would even be a fountain...?<br />
<br />
'''Balance: 7/10?'''; approximated by having level 30 pet solo battles<br />
<br />
The mostly-questing-prices Level 30 Knight-like pet that I brought here to fight could usually win solo battles before the Anger Rating maxxed out, but took nontrivial amounts of damage in the process, even with the modestly-interesting combat progs most of them had. Except against Gyrados, which is appropriate given the level jump. RIP.<br />
<br />
In terms of drops and loot, there are some finds here that... aren't very good, but have niche uses, and the pokemon in the area drop enough cash that the 100 silver entry fee isn't a huge deterrant. However, the drops have... pretty bad sell value, and feel rare for the narrow range where it's useful. For example, I managed to clear out the forest twice without getting the Scyther equipment drop.<br />
<br />
I'm not sure how to feel about the frequency of the pokemon food dropping from everything in the area: It's such a poor food item that it can't be used to stave off hunger, but I don't know how common it should be to have it as an option to offset the anger meter mechanic for classes that aren't damage-focused, or if it should offer much side use for players that don't. Would 1 satiation/1 fullness to make it at least count as a snack for the shameless be too much?<br />
<br />
'''Attractions: 3/10'''<br />
<br />
The Safari Zone is in a weird place in terms of attractiveness. If you know enough about it already and have an aggressive enough skillset, it can be a servicable levelling spot with some niche drops available, but if you haven't figured the area out already, there's no real indication that sticking around is worth it - especially since the main attraction to the area is fighting the pokemon without being caught by the warden, when both the warden and Todd appear to discourage you from fighting them. Some more guidance that "yeah, beat 'em up but be careful" is the real point would probably make the area clearer. Perhaps Todd could drop a hint that you'll need to at least provoke pokemon to get the photos he needs and let the rest happen as it will?<br />
<br />
There are some hidden things hinted at or with requirements from other zones that are definitely worthwhile, but I don't know whether to count those as attractions for the Safari Zone, or attractions for those other zones that require you to look around further. They don't really add incentives to stay at the safari zone - just to visit briefly to get something else in an area you're already overlevelled for and might as well leave immediately afterwards. The items available are... usable, but not especially impressive outside of some distinct niches.<br />
<br />
Outside of the purely pokemon-flavored sightseeing there's not a lot here that you can't do better at elsewhere. Tonoe and Arlia aren't much further from Viorar with significantly wider options and more relevant quests...<br />
<br />
'''Connections: 2/10'''<br />
<br />
Another rough spot. The Safari Zone is entirely pokemon-based aside from references in the graffiti and a few external quest things that are hard to count as the Safari Zone specifically. But... it is specifically an animal reserve for pokemon and that's exactly what the Warden would do, so it's hard to justify further connection to the rest of the Cleft.<br />
<br />
At most, other visitors of different races/whatever as NPCs with hints or advice could be added, or adding references to external resources that the Warden would be willing to employ to try and keep the pokemon safe; hidden Monotoli-brand security cameras, for example. Still, whether the warden would have/use the resources to do this is difficult to say.<br />
<br />
The connections for Safari Zone are poor, but adding more is also difficult to justify. Hard to say what to do with this one: Probably best left as a low priority outside of a serious zone overhaul.<br />
<br />
'''Bugs/Exploits:'''<br />
<br />
Something I'm not sure is a bug - you can attack and kill Todd, the starter NPC for the only real quest in the zone. No special response or acknowledgement is given for this, and he's level 0. Should he be classified as either noattack or a player ally?<br />
<br />
'''Overall: C-'''<br />
<br />
The Safari Zone is not one of the Cleft's stronger zones. Between the mediocre attractions there and its dead-end location it's very easy to skip over or forget about entirely, though there are some neat points hidden away if you make a point of looking. Is it worth doing more than once? Well... not really. Todd doesn't even offer a mini medal for his miniquest, which is so small and simple that's even understandable. There's not much to do here aside from get into fights to level, but the zone flavor even discourages that. It looks so promising when you start out with the river and pond areas and all the graffiti descriptions, but falls apart pretty quickly once you go further and start really interacting with the area. If anyone particularly feels like revamping things, this is probably a good candidate for it.<br />
<br />
<br />
----<br />
<br />
Player: Patapon(Warrior/25)<br />
<br />
Review Date(s): 9/19/18<br />
<br />
'''Descriptions: 5/10'''<br />
<br />
Marginal typographical errors throughout the area, not bad enough to really distract too terribly. The mobs are described well, however the descs are all short and formatted inconsistently. There are almost no extra descs except for some graffiti and one random lantern that is formatted kind of crazily and seems almost cryptic and meaningful, but isn't, like most things in this area.<br />
<br />
It's not the worst I've ever seen but it's right about bare minimum for acceptable.<br />
<br />
<br />
'''Balance: 4/10'''<br />
<br />
The fights are very easy, but I am also a warrior so that might be a side effect. There are a lot of mobs to fight so it's a pretty mindless grind. The anger mechanic exists. I'm sure it's helpful but it's mostly a non-issue, it's never difficult to toss a food at a pokemon, especially since they drop all over.<br />
<br />
The random rarer pokemon are marginally harder, which makes sense.<br />
<br />
The gear attained here is entirely ignorable. There is nothing significant that better can't be found before or at the same level, some of it from vendors. Even random drops from mobs should be better than vendor gear.<br />
<br />
<br />
'''Attractions: 1/10'''<br />
<br />
I immediately lost Todd in a tree before finding the pokemon he requested. Looking around the entire place, I'm not sure it even exists. The quest ends abruptly with screen spam. It could be tidied up with some delays. The quest could also be made better by not being so terrible.<br />
<br />
There is nothing here of value or interest, except for two different unrelated things from completely different areas that you wouldn't know about just from going here.<br />
<br />
I'm giving it 1 point because pokemon themselves are an attraction. It was fun finding the different pokemon, like gyarados. However, defeating them always let me down.<br />
<br />
<br />
'''Connections: 1/10'''<br />
<br />
From a straight-forward approach, the connections here are close enough to non-existent to be statistically insignificant. However, it could easily be speculated that the Safari Zone as a wildlife preserve is controlled by the nearby Fort Walla Walla, one of the only 'law and order' type establishments in this region of Fa'diel and possibly the only ones interested in preserving wildlife. Otherwise, the "don't fight the pokemon" command doesn't make any sense. As is, there is no connection, but potential exists to tie it in much better.<br />
<br />
<br />
'''Personal'''<br />
<br />
The way to get in is not straightforward. It says you have to pay, but what he means is you have to buy a ticket. I am not the only person who did not figure out that you had to actually buy a physical ticket from the guard via typical shop mechanics. The first time I came here I couldn't figure it out literally at all and got in by sneaking through. When I came back without sneak, it took me 10 minutes to figure out. He also says you need to put away your weapons, but you actually don't, which is lame.<br />
<br />
This area has great potential. Even with the mediocre descriptions, the aesthetic is nice. Just by merit of having pokemon and being the safari zone, this area is okay. If it was anything else, I would probably say it was terrible.<br />
<br />
----<br />
<br />
[[Category:Area of the Month|*]]</div>Pascal