Difference between revisions of "Category:Monster Condition"
Jump to navigation
Jump to search
m |
(adding custom conditions) |
||
| Line 4: | Line 4: | ||
<noinclude> | <noinclude> | ||
| + | == Adding Custom Monster Conditions == | ||
| + | |||
| + | Hook <code>checkMonsterCondition</code> has the following fields in argument hash: | ||
| + | * <code>monster</code> - currently checked monster's Actor object | ||
| + | * <code>prefix</code> - currently checked config block's prefix (blockOption's value would be <code>$config{$prefix."_blockOption"}</code>) | ||
| + | * <code>return</code> - set to '''0''' to indicate that condition failed | ||
| + | |||
[[Category:Reference]] | [[Category:Reference]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 08:50, 8 September 2010
Conditions about the monster status/information.
These condition attributes are shared between the attackComboSlot, attackSkillSlot, equipAuto, and monsterSkill configuration blocks.
Adding Custom Monster Conditions
Hook checkMonsterCondition has the following fields in argument hash:
monster- currently checked monster's Actor objectprefix- currently checked config block's prefix (blockOption's value would be$config{$prefix."_blockOption"})return- set to 0 to indicate that condition failed
Pages in category "Monster Condition"
The following 10 pages are in this category, out of 10 total.
