🌟settings.yml
Should LM stop sending packets if an entity has died?
true- Once an entity has reached zero health, packets for that entity will no longer be sent.false- Once an entity has reached zero health, LM may send extra packets to try make sure the entity's nametag data (such as their health) is accurate.
This setting attempts to fix a compatibility issue with ViaBackwards where VB detects LM sending name tag packets of entities which are dead.
It is not recommended that you change this setting unless you understand exactly what you are doing.
Automatic Asynchronous Nametag and Level Updater
This setting will check the the area within X blocks of a player, where X is the async-task-max-blocks-from-player:, for any entities which should have been levelled, LM nametagged, or are missing attributes for whatever reason.
The async-task-update-period: is counted in seconds.
Customize Summon Command Limit
This setting will forcibly limit the number of entities which can be summoned with LM's /lm summon command per use.
This is used to help prevent any accidents or overloading your server with countless entity summons.
Head Drop Multiplier
true- Mob head item drops will not be multiplied if they otherwise would be.false- Mob head item drops will be multiplied as if they were any other material drop.
On some servers, heads are considered too valuable of a resource to be multiplied alongside the other drops of an entity. This setting allows you to decide whether you want to allow these drops to multiply alongside everything else that would have dropped.
Customize Command Drop Limiters
This helps to prevent any accidental crashes through an entity running more commands than your server can handle upon death. This will set a hard-limit on any custom commands dropped through the Custom Drops system, overriding any set amount: which is above this value.
Mob Processing Delay
This will add an additional amount of delay, counted in ticks, before LM begins to process the entity. Adding delay is only useful in situations where other plugins need time to process before LM applies any values.
It is not recommended that you change this setting.
Summon Command Spawn-Distance-from-Player
This will determine the maximum distance from a player an entity will spawn when you utilize /lm summon <quantity> <entity> <level> here.
This will determine the minimum distance from a player an entity will spawn when you utilize /lm summon <quantity> <entity> <level> here.
Kill-Skip Conditions
For each kill-skip condition above:
true- Entities under that condition will be skipped during LM's kill command.false- Entities under that condition will not be skipped during LM's kill command.
You can also specify specific mob types in a similar fashion to the Condition check for entities.
These will specify what entities are skipped when you utilize /lm kill.
This is useful to prevent any pets or other unintended entity deaths.
It is recommended that you do not adjust these settings without knowing what you are doing.
Use Translation Components
true- Any default entity names will be displayed to the player in the native language used in the players' client.false- Some older and customized clients do not support this feature, so you may disable this if your servers' environment requires this circumvention.
This system provides a quality of life mechanism and should be enabled in most situations; this feature does not exist in older Minecraft clients and some customized clients, and can result in broken names being displayed to the player. Should your server necessitate this kind of circumvention, then by disabling this feature you are instead referencing an internal table of English names. You can still modify the name of entities via the apply-setting: entity-name-override: feature of the rules.yml.
Verify Entities on Chunk Load
true- Loaded chunks nearby players will be checked for any entities which are missing a level which should not be.false- Entities which were not levelled for whatever reason will not be double-checked.
This system acts like a janitor, checking loaded chunks nearby players for any entities which should be levelled and are not.
It is recommended that you do not change this setting if you do not understand its effects.
Print LM Summon Command Results to Console/Player
true- When enabled, use of the LM Summon Command will be output into console.false- When disabled, use of the LM Summon Command will not be output into console.
This setting manages whether the LM Summon Command output text will be displayed in the console or not. Disabling this setting might be useful if you utilize the command regularly or repeatedly which might fill the console with notices.
Level Entities on Spawn
true- Once an entity has been spawned into the world, LM will immediately attempt to apply a level to the entity.false- Entities will not receive a level until they either take damage from a player or have targeted a player.
Chunk Kill Count System
true- When the chunk kill count system is enabled and reaches the threshold for max deaths a chunk, a message will be sent to the player that killed the mob.false- No messages will be sent to any players for the chunk kill count system.
Check Mob Rule Hash
Mobs which have been levelled by LevelledMobs will receive a uniquely generated hash key. This key is unique to the settings and layout of your rules.yml and is generated during server startup and any /lm reload thereafter. This setting handles what the listener will do when it detects a hash key that does not match to the current rules hash key. This task is performed during the automatic asynchronous tasks ping (default of six seconds) as well as when chunks are loaded and the level verification listener is performing. It is recommended that you do not change this setting as this resolves a long-standing issue of outdated levelled mobs existing in long-forgotten unloaded chunks.
true- When an entity is determined to have a missing or invalid hash key, the entity will immediately be re-evaluated using the current rules arrangement and receive an updated hash key.false- Entities will not be re-evaluated if there is a missing or invalid hash key. This means that entities which had become unloaded during a previous hash of the rules will not be re-evaluated once they become reloaded.
Player Levelling Strategy Settings
player-levelling-relevel-min-time: represents the time, in milliseconds, before an entity is updated against the nearest player. Setting this to 0 will prevent any relevelling.
These settings revolve around the levelling modifier known as Player Variable Modifier.
Nametag Placeholder Distance
nametag-placeholder-maxblocks: represents the the maximum distance from the player an entity can be to be registered under %levelledmobs_mob-target%.
Updates and Debug Settings
use-update-checker: When set to true, this will notify you once at server startup whether you have an up-to-date version of LM.
debug-entity-damage: When set to true, this will display detailed attribute information in-game when you hit an entity.
debug-misc: Refer to settings.yml/Debug-Misc for further details.
file-version: This value represents the config processing version. Do not alter this value, or you may break your plugin and configs.
LivingEntityWrapper [LEW] Cache Settings
This establishes the timetable on which any stagnant or expired LEW which were not cleared automatically are cleared by force. This is to help prevent any memory issues. It is not recommended that you change this setting.
Exclude Creative-Mode Players from PVM
true- A player in Creative mode in-game will not be counted when the Player Variable Modifier updates any mob values.false- The player can be in Creative or Survival mode.
Last updated