🌟customdrops.yml
Custom Drops Configuration
LevelledMobs' customdrops.yml
file allows you to build custom drops utilizing many different config options to create unique materials and custom commands to add to or replace an entity's drops.
Defaults:
These config options will apply to all drops constructed within CustomDrops unless you have modified a drops' individual properties to override these default settings. Each of these must have a value in order for LM's CD to function properly, but once it is set here, you do not need to set it within your individual drops if the value would not change. These defaults apply to all systems within the CD file, including Drop Tables.
For any value listed as a percent:1.0
= 100% ;0.0
= 0%
Config Line Option | Description |
---|---|
| This represents the percent chance of an individual CD being dropped. Supports sliding values. |
| If the chunk kill count system is enabled in |
| This represents the number of individual CD being dropped. This may be ranged, such as |
| This represents the minimum and maximum level required of the entity before an individual CD will drop.
Replace with |
| The amount of damage the item will have. Can use a number or a number range. The higher the value, the more damaged it will be. |
| This is an advanced config option; This represents a custom model to apply to the material CD. |
| This represents the check whether a CD will or will not multiply according to the |
| This represents the check whether a CD will or will not apply to an entity spawned by a Spawner Cube. |
| This represents the percent chance of an individual CD being equipped by the entity if it is able to. It will first attempt to place in the hands, then the skull, and otherwise will ignore if the entity could not normally equip an item (such as Silverfish). Supports sliding values. |
| If |
| When set to |
| This represents the name to apply to the material drop when it is used on a |
| This structure of config options allows you to set multiple lines of lore to apply to a |
| This structure of config options allows you to apply enchantments to items.
Replace |
| This will determine whether LM will process CD alongside the vanilla drops, or replace them entirely. |
| Using |
| The |
| By default, CD processes the drops in a similar fashion to how LM processes the rules tree.
By setting a |
| This represents the check on whether the entity's death was caused by a player, or whether it was environmental.
It is recommended that you do not change this from |
| This represents a percent chance of any of the EntityType's CD being processed at all. This only needs to be placed once for an EntityType, and if the chance fails, none of the CD for that EntityType will process. Supports sliding values. |
| This allows you to specify any NBT data to apply to a material drop. NOTE: This requires the soft-dependency NBT-API. |
| This allows you to specify the various |
| This represents a check, if an Entity has |
| A |
| A |
| This represents the minimum and maximum Minecraft level required of the Player before an individual CD will drop.
Replace with |
| If this config option is set, the above |
| If this config option is set, you can instead check for a text-based value from a a |
| When used with LM Items Official Plugin, this sets the amount internally to the specified plugin |
| When used with LM Items Official Plugin, this sets the item type (currently only supported with MMOItems) |
| Applicable only to custom commands, determines if it will be executed when a mob spawns in |
| Applicable only to custom commands, determines if it will be executed when a mob dies |
| Applicable only to custom commands, this is the number of ticks that will elapse before the command is executed |
Universal Groups:
LM includes several groups of entities which are bundled together in a convenient format. Each of these groups function as their own EntityType, applying to multiple entities at once. You can refer to the EntityType Universal Groups for the different types!
Specified Mobs:
LM has listed all vanilla entities as of Minecraft 1.20 within the CD file. You should locate the entity you wish to modify instead of adding additional entities at other spots within the config, as they will most likely not process as expected. You may delete any entities you do not use if you so choose, as you can always add them back again later.
Sliding Values
There are three options that support sliding values; chance
, equipped
and overall_chance
. You can either use a decimal to represent a percent or assign tiers that represent a level range and an assignment range. The syntax is:
On the left side you put the min and max levels that the tier can match, then on the right side put the min and max chance those level ranges will use; where the assigned value slides based on the level values assigned. If the mob level is between the min and max then it will use the assigned min and max assignment. For example:
In the above example, level 1 mobs will have a 20% chance. Level 10 mobs will have 80% chance and any mob levels in between will scale accordingly. For mobs levelled 11 through 20, they will have a 100% chance. Any mob levels without an assignment will have 0% chance, such as level 21+ in the above example.
Drop Tables
CD includes the Drop Table system, which allows you to construct groups of materials or custom commands which can be attached to any EntityType as a single line item utilizing usedroptable: tableName
, helping to reduce any instances of duplicate drops covering multiple entities. This can also be used to craft 'tiered' drops.
When constructing drops with the Drop Table, you can replicate the same formatting used for any other drop, replacing the EntityType with the tableName.
NOTE: It is highly recommended that you instead use the Rules file to implement any drop table. It will provide far more accurate conditioning for when and how to apply drop tables.
LM Items - External Plugin Support
If you want to use custom items from external plugins, take a look at LM Items. This plugin bridges the gap so you can use third party items natively. Download from https://www.spigotmc.org/resources/lm-items.102081/
An example of how LM Items improves your server: Adding Player Heads to mobs!
Here is an example of how to use the - HeadDatabase:
LM Items item-type.
You supply the skull ID number from Minecraft Heads, which is provided in the URL of the skull which you select, and append it to the HeadDatabase:
item-type as shown above.
For example, the url https://minecraft-heads.com/custom-heads/humanoid/61942-demon-helmet
would have the ID 61942
.
Materials, Commands, and Special Items
MATERIAL:
drops gather their config options from the Defaults section listed above. Any config option listed there can be used within any MATERIAL:
or customCommand
drop.
customCommand:
tells CD that you wish to setup a command to process like any other drop.
In order for this feature to function, it requires at minimum the command:
config option with a valid console formatted command present.
You can also use multiple commands at once by listing them as demonstrated above.
An example of a valid command might be effect give %player% strength %ranged_a% %ranged_b%
.
The tags prefixed with ranged_
are unique. These allow you to construct a random number generator to be used within commands as placeholders. The example config above demonstrates how you would utilize the ranged config option, appending an A/B/C/D, et cetera to the end of ranged_
creates the tag, while the value represents a range of potential values which could be applied to the placeholder tag present in the individual command drop. Using the previous example command, with the ranged_A: 1-2
and ranged_B: 3-5
, then the first tag would be any value between 1-2, while the second would be any value between 3-5 when utilized within the command being activated.
ENCHANTED_BOOK
is a special type of MATERIAL
drop which will enable anvil-ready enchanted books by utilizing the enchantments:
config option.
Last updated