Conditions
Last updated
Last updated
| Modular Option Conditions | Description |
|---|---|
spawn-reasons:
Check against possible spawn reason flags.
You can reference the SpigotMC javadocs regarding CreatureSpawnEvent.SpawnReason for the different options. You may also use LM_SUMMON or LM_SPAWNER, referring to mobs created from the /lm summon or /lm spawner command.
worldguard-regions:
worldguard-region-owners:
Check against the WorldGuard region or region owner where the mob spawned.
apply-above-y:
apply-below-y:
Checks whether the mob is above or below a specific Y coordinate.
external-plugins:
Check against whether the spawned mob came from an internally or externally supported plugin.
biomes:
Check against the biome where the mob spawned.
custom-names:
Check against a mobs' Custom-Name when a level is first applied, presuming it has one.
chance:
Can be applied to a Custom Rule where the rule will only have the specified chance to apply the rule, otherwise it will be skipped. By default, a rule without a specified chance will always process if it has been enabled.
entities:
Check against the mob which is being processed.
minLevel:
maxLevel:
Check against the level of the mob after it has been applied. This check is only done for a handful of Settings, including Custom Drops.
min-distance-from-spawn:
max-distance-from-spawn:
Check against the minimum and maximum distance from the Minecraft server spawn coordinates where the mob spawned.
mob-customname-status:
mob-tamed-status:
Check against the Custom-Name or Tamed status of a mob.
NOT_SPECIFIED / EITHER (Default)
Check is disabled / Check value does not matter
NAMETAGGED / TAMED
Checked mob must be either Nametagged or Tamed
NOT_NAMETAGGED / NOT_TAMED
Checked mob can not be either Nametagged or Tamed
mythicmobs-internal-names:
Check against the internal name used within the MythicMobs custom mob configuration file.
permission:
Check against the allowed permission nodes established for the nearest player to the entity, OR the player who killed an entity, depending on it's implementation.
spawner-names:
Check against the name of the LM Spawner which created the entity.
scoreboard-tags:
Check against any possible Minecraft Scoreboard tags applied to a mob, and whether those specified tags exist.
stop-processing:
Can be applied to a Custom Rule where the rule will cause future rule processing to cease upon activation of the stop-processing: setting.
By default, a rule without a specified stop-processing be processed from top down; starting with the Default Rule, then the first Custom Rule, and all subsequent rules in order.
within-coordinates:
This system allows you set the start- and end- coordinates to define a region within your world to apply a rule within. You can just specify a single axis to mark a single point or line; specify two axis to make a square along those two axis; or specify three to make a cuboid region. You can also place '-' or '+' as the end- of any coordinate and it will go from the start- value to infinity in the direction specified. Finally, if you specify a start- but do not specify an end-, then the end- will be the same value as the start-; and vice versa.
worlds:
Check against the world where the entity spawned.
world-time-tick:
Check against the current time of day in the world, represented by ticks. A 24 hour day in Minecraft is represented by a world-tick value between 0-24000. You can get a better sense of the time of by by referencing this link. Only the Overworld has a 'time of day'.
cooldown-duration:
cooldown-limit:
Can be applied to a Custom Rule where the rule when successfully applied will count up from zero for each activation until it reaches the cooldown-limit:, then it will lock the rule from applying for the cooldown-duration: timer. Once the timer expires, the rule is unlocked and the limit count is reset.