LevelledMobs - The Ultimate Mob Levelling Solution
  • LevelledMobs v4.0
    • 🌏Home
    • 🤖Installation
    • 💢Errors and Running LM
    • 🗣️FAQ
    • ⚙️For Developers
    • 🔑Commands and Permissions
    • 🔥Debugging
    • 🪨Placeholders
    • 📈Performance & Tweaks
    • 💠[Github] Latest Release Version
  • The Default Files
    • 🌟Understanding the Modular Rules System
    • 🌟Running the Default Configuration
      • The Default / Presets
      • The Default / Default Rule
      • The Default / Custom Rules
    • 🌟rules.yml
      • Conditions
      • Strategies
      • Modifiers
      • Settings
      • 👾Sample Custom Rules
    • 🌟customdrops.yml
      • 👾Sample Custom Drops
    • 🌟externalplugins.yml
      • Known Plugin Keys
    • 🌟settings.yml
    • 🌟messages.yml
      • 🧙‍♂️Official Translations
  • Credits and Misc
    • 🐐Developers and Contributors
    • 🤟Donations
    • 📐bStats Metrics
Powered by GitBook
On this page
  1. The Default Files
  2. rules.yml

Conditions

Click to view a comprehensive list of all Conditions
conditions: 
  spawn-reasons: ['']
  worldguard-regions: ['']
  worldguard-region-owners: ['']
  apply-above-y: 0
  apply-below-y: 0
  external-plugins: ['']
  biomes: ['']
  custom-names: ['']
  chance: 1.0
  entities: ['']
  maxLevel: 50
  minLevel: 1
  max-distance-from-spawn: 0
  min-distance-from-spawn: 0
  mob-customname-status: EITHER
  mob-tamed-status: EITHER
  mythicmobs-internal-names: ['']
  permission: ['']
  player-names: ['']
  gamemode: ['']
  spawner-names: ['']
  scoreboard-tags: ['']
  stop-processing: true
  within-coordinates: 
    start-x: 0
    end-x: 0
    start-y: 0
    end-y: 0
    start-z: 0
    end-z: 0 
  worlds: ['']
  world-time-tick: ['']
  cooldown-duration: 10s
  cooldown-limit: 0

Modular Option Conditions
Description

spawn-reasons:

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.

player-names:

Check against the name(s) of the nearest player to the mob.

gamemode:

Check against the current gamemode set for the nearest player to the mob. Valid options include: creative, survival, and spectator.

spawner-names:

Check against the name of the LM Spawner which created the mob.

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 mob spawned.

world-time-tick:

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.

Previousrules.ymlNextStrategies

Last updated 28 days ago

Check against possible spawn reason flags. You can reference 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.

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 . Only the Overworld has a 'time of day'.

🌟
the SpigotMC javadocs
better sense of the time of by by referencing this link