Targeting Modded Structures Using Config Identifiers
If you are customizing data files for your world, Cristel Lib uses a standardized naming format to ensure your custom settings connect to the intended mod and structure.
The Identifier Format
Cristel Lib links configurations to specific mods using the <mod_id>@<config_name> syntax:
- Replace
<mod_id>with the exact identifier of the target mod (such as supported mods like Explorify, WWEE, or Towns and Towers). - Use the
@symbol as the separator. - Replace
<config_name>with the specific structure configuration you want to address.
Overriding Existing Structure Data
Using this identifier structure allows you to cleanly replace or customize default generation:
1. Identify the target mod ID and the configuration name you wish to alter.
2. Create your custom configuration entry using the full <mod_id>@<config_name> format.
3. Define your custom spawning rules or structure behavior within the configuration file.
When your world loads on Fabric, Forge, or NeoForge, Cristel Lib reads the identifier, recognizes the target mod, and replaces the default configuration with your custom data through its runtime datapack system.