# Running the Default Configuration ## **The Default Rule and Presets** 
#
#   ---------------  -  ------------------------------
#        Section 03  |  Set the Default Rule
#   ---------------  -  ------------------------------
#
default-rule:
  use-preset:
    #===== Choose a Challenge =====
    #- challenge-vanilla
    #- challenge-bronze
    - challenge-silver
    #- challenge-gold
    #- challenge-platinum
    #- challenge-formula
    
    #===== Choose Strategies =====
    #- lvlstrategy-random
    - lvlstrategy-weighted-random
    - lvlstrategy-distance-from-origin
    #- lvlstrategy-y-coordinate

    #===== Choose Modifiers =====
    - lvlmodifier-player-variable
    - lvlmodifier-custom-formula

    #===== Choose Additional Options =====
    - nametag-using-numbers
    #- nametag-using-indicator
    #- nametag-minimized
    #- nametag-disabled
    #- custom-death-messages


#
#   ---------------  -  ------------------------------
#    Section 03 - A  |  Default Rule / Conditions
#   ---------------  -  ------------------------------
#
  conditions:
    worlds: ['*']
    #biomes: ['*']
    entities: ['*']

    mob-customname-status: EITHER
    mob-tamed-status: EITHER


#
#   ---------------  -  ------------------------------
#    Section 03 - A  |  Default Rule / Conditions
#   ---------------  -  ------------------------------
#
  conditions:
    worlds: ['*']
    #biomes: ['*']
    entities: ['*']

    mob-customname-status: EITHER
    mob-tamed-status: EITHER
#
#   ---------------  -  ------------------------------
#    Section 03 - B  |  Default Rule / Settings
#   ---------------  -  ------------------------------
#
  settings:
  # Core LevelledMobs Settings
    minLevel: 1
    maxLevel: 50

    construct-level: '%distance-from-origin% + %weighted-random% + %player-variable-mod% + %rand_-5_5% + %custom_special%'

  # CustomDrop Settings
    use-custom-item-drops-for-mobs: true

  # Additional Nametag Settings
    nametag-placeholder-levelled: ''
    nametag-placeholder-unlevelled: ''
    nametag-visible-time: 5s
    nametag-visibility-method: [ 'TARGETED', 'ATTACKED', 'TRACKING' ]

  # Adjusts the `%tiered%` and `%health-indicator-color%` placeholders
    tiered-coloring:
      1-09: '&#22E76B' #Green
      10-19: '&#528CFF' #Blue
      20-29: '&#FFCD56' #Yellow
      30-39: '&#F2003D' #Red
      40-49: '&#B447FF' #Purple
      50-50: '&#FFD700' #Gold
      default: '&#FFFFFF' #White
      
    health-indicator:
      colored-tiers:
        tier-1: '&#22E76B' #Green
        tier-2: '&#528CFF' #Blue
        tier-3: '&#FFCD56' #Yellow
        tier-4: '&#FE803C' #Orange
        tier-5: '&#F2003D' #Red
        tier-6: '&#B447FF' #Purple
        default: '&#B447FF' #White
      scale: 5
      max: 5

  # LevelledMobs Spawner Cube Settings
  # Use Command:  /lm spawner
    spawner-particles: 'SOUL'
    spawner-particles-count: 10

    baby-mobs-inherit-adult-setting: true
    transforming-mobs-inherit-level: true
    riding-passengers-match-vehicle-level: false

  # Miscellaneous Settings
    multipliers:
      vanilla-bonus:
        excluded-list: ['LEADER_ZOMBIE_BONUS', 'RANDOM_SPAWN_BONUS']

    sunlight-intensity: 5
    creeper-max-damage-radius: 3
The above set of code is copied from the `rules.yml` file for `v4.0.0 b1`. *** ## The initial presets section {% code overflow="wrap" %} ```yaml use-preset: #===== Choose a Challenge ===== #- challenge-vanilla #- challenge-bronze - challenge-silver #- challenge-gold #- challenge-platinum #- challenge-formula #===== Choose Strategies ===== #- lvlstrategy-random - lvlstrategy-weighted-random - lvlstrategy-distance-from-origin #- lvlstrategy-y-coordinate #===== Choose Modifiers ===== - lvlmodifier-player-variable - lvlmodifier-custom-formula #===== Choose Additional Options ===== - nametag-using-numbers #- nametag-using-indicator #- nametag-minimized #- nametag-disabled #- custom-death-messages ``` {% endcode %} Starting from the top section, we see a collection of various `use-preset:` options, most of which have been commented out. These make liberal use of the **Presets** section located in the area above the **Default Rule** to allow for quickly changing between a handful of both common and useful options; some being the same with different values, others offering optional features and a convenient way to apply them either in the **Default Rule** or **Custom Rules.** In this instance, we have separated the various **Preset** types into four categories: *Challenges*, *Strategies*, *Modifiers*, and *Miscellaneous*. Under the *Challenges* section, we have six degrees of play-tested challenge presets: *Vanilla*, *Bronze*, *Silver* \[Default], *Gold*, *Platinum*, and *Formula*. These presets include the settings associated with altering the attributes of the entities, with *Vanilla* representing zero change to the attributes; *Bronze* containing modest increases; *Silver*, our default, being our middle ground between fun and challenge; *Gold* often requires players to be fully armored and weaponized to take on, while *Platinum* is made for the hardcore player or server which gives players non-vanilla abilities. *Formula* is a new addition with LevelledMobs 4; creating a challenge on par with the *Gold* challenge, but handled using our new custom formula mechanic, allowing you to use some degree of math to craft your own attribute changes. The *Strategies* section includes any enabled *Strategy* which may be used to calculate the level of a mob. This section, in tandem with the *Modifiers* section, produce internal-use placeholder tags associated with the relevant strategy. With LevelledMobs 4, you can specify multiple running *strategies* or *modifiers* which can be combined together in multiple ways. We suggest using the `construct-level:` configuration setting (which is described below) to build your level exactly how you desire. Beneath this section resides the *Miscellaneous* options which include presets of optional features from the unique nametags, custom entity names, custom player-death messages, health indicator display, and more. *** ## The Construct-Level New to LevelledMobs 4, the Construct-Level setting allows you to take the output from various *Strategies* or *Modifiers* and incorporate basic math functions to produce a final level to apply. This feature allows you to have multiple strategies enabled at once, each providing their own numerical 'level' value, which can be put together how you choose. Using the default configuration (sampled below), we take the output from the enabled **Distance-from-Origin** and **Weighted Random** strategies, in the form of the placeholders of the same name, as well as the modifiers **Player Variable** and **Custom Formula** under their own placeholders, added a new **Random** variable between -5 and 5, and finally using math combine the values to provide a unique levelling strategy. If you do not specify the `construct-level:`, then the *strategies* and *modifiers* output will be combined together to produce the final applied level. {% code overflow="wrap" %} ```yaml construct-level: '%distance-from-origin% + %weighted-random% + %player-variable-mod% + %custom_special% + %rand_-5_5%' ``` {% endcode %} ## The difference between attribute modification and level There is an important distinction between levels, levelling, and the `minLevel` or `maxLevel` values; and the actual modification of the attributes of the mob. When you establish the `minLevel` and `maxLevel`, you are telling LevelledMobs what the lowest and highest numerical level value can be for a mob. By default, under most instances, `minLevel` should probably remain at `1`, but there are valid reasons to have this value higher (perhaps you want mobs to all start out with an artificially higher starting increase to their attributes). As for `maxLevel`, that is far more subjective and dependent on how you want to stretch out the changes to the attributes for mobs. By default, we use `maxLevel: 50` which means that we stretch attribute changes from Level 1 to Level 50. ## Attribute-Modifier When you set an `attribute-modifier:` using the original LevelledMobs method (sampled below), then the plugin will use the value as the 'multiplier increase when at max level' and provide equal portions of that value to every level below maximum. {% code overflow="wrap" %} ```yaml settings: attribute-modifier: max-health: 5.0 ``` {% endcode %} $$ f(x) = attribute + ((attribute \* config) \* (level / maxlevel)) $$ There are also several special multipliers, whose output must result in a value between `0.0` and `1.0` , due to the nature of how the attribute works in Minecraft. We use the following formula when using the original LevelledMobs method (sampled below) to apply the values these special attributes. {% code overflow="wrap" %} ```yaml # Special Multipliers (0.0 Min - 1.0 Max) armor-bonus: 0.5 armor-toughness: 0.5 attack-knockback: 0.5 knockback-resistance: 0.5 zombie-spawn-reinforcements: 0.15 ``` {% endcode %} {% hint style="info" %} Where `attribute.max` is populated by the following values: ``` armor-bonus: - 30.0 armor-toughness: - 20.0 attack_knockback: - 5.0 knockback_resistance: - 1.0 zombie-spawn-reinforcements: - 1.0 ``` {% endhint %} $$ f(x) = (level / maxlevel) \* (attribute.max \* config) $$ However as part of LevelledMobs4, you can now use a basic mathematical formula to adjust the attribute (sampled below). Using this sample, we take the placeholder value of the same attribute, representing the base attribute value of the entity, and then add to this value the level times the their health multiplied by 0.25. The end result of this formula is that for each level, the health increases by 25% of the original entities' health value. {% code overflow="wrap" %} ```yaml settings: attribute-modifier: max-health: '(%level-ratio% * %max-health% * 5)' ``` {% endcode %} *** ## ## In the next section, we will explain how the Default Rule is applied as part of the default configuration.