As part of the Default Rule, you need to establish the core set of conditions under which LevelledMobs can function. This includes at minimum the worlds and entities which you want LevelledMobs to function. If no world is specified, then as a protective measure LevelledMobs will presume it does not have access to any world; The same will apply to entities.
We also offer options to help identify either pets via the mob-tamed-status condition, or whether a mob has a nametag or custom-name applied via the mob-customname-status condition.
Here is where you would apply the default settings for the mobs conditioned to receive a level earlier.
You would also include any attribute-modifiers you wanted to apply under settings: as well, however we used the Presets section to include an appropriate Challenge which includes these configuration options.
After establishing the level range, and the construct-level, we have a list of multiple optional settings to apply various changes to how LevelledMobs functions; from enabling the Custom Drops system, to managing the level inheritance of certain mobs, etc.
From here we are going to make several modifications to the Default Rule by creating multiple Custom Rules based on a variety of conditions, and explain why we made these decisions os you can decide if the default configuration is right for you and how you might make the changes you desire to make it perfect.
In the next section, we will explain each of the Custom Rules as part of the default configuration.
