Cristel Lib Mod FAQ

It's a library mod that lets structures be configured through code or datapacks, so you can control where and how structures spawn. On its own it doesn't add any structures — it's the framework other mods and datapacks plug into.

You don't interact with it directly in-game; instead you install it alongside a structure mod or datapack that uses it, then edit or add structure configs. Start by checking whether the structure mod you're using already ships Cristel Lib configs you can tweak.

Yes — those mods rely on Cristel Lib for their structure configuration, so it must be present for their structures to generate correctly. If it's missing, the dependent mods may fail to load or their structures won't spawn.

Structure configs go in a datapack under the mod's expected data folder path, the same way you'd add any other datapack data. Load the datapack through your world or mod loader's datapack system and the config is read on world load.

Yes — Cristel Lib supports runtime datapacks, so you can add or modify structure data while the game is running. Reload the datapacks and the changes apply without a full restart.

You define the biome conditions in the structure's Cristel Lib config, listing which biomes it's allowed in or excluded from. The config is checked at generation time, so the structure only appears where the biome rules match.

Common causes are the config being in the wrong datapack folder, the datapack not being enabled, or the biome/spacing conditions excluding your test area. Double-check the datapack path and reload before assuming the config is broken.

Yes — it loads datapacks on both Forge (NeoForge) and Fabric, with checks in place so configs behave consistently across loaders. Make sure you're using the build that matches your loader.

It's a lightweight library, so the overhead comes mainly from the structure configs you or other mods define, not the library itself. Heavy structure sets with many biome checks will cost more during world generation regardless of the library.

Yes — if a mod's structures are driven by Cristel Lib, you can override or adjust their configs through your own datapack. This lets you change biome placement or spawn behavior without editing the mod itself.

Yes. Cristel Lib is a dependency for those mods, so it must be installed alongside them or the game will fail to load. It doesn't change anything on its own, it just provides the structure config system they rely on.

Decide first whether you're writing a datapack or using code. For datapacks, create a config file in the mod's expected data folder and define your structure's placement rules there, then load it into a world. For code, modders register the config through the mod's API instead.

Yes, Cristel Lib supports runtime datapacks, so you can add or change structure data while the game is running. Use the reload command after dropping your datapack files in, and the new configs should apply without a full restart.

Place the datapack in the world's datapacks folder like any normal datapack, then run the reload command in-game. Cristel Lib checks and loads it on both Forge (NeoForge) and Fabric, so the process is the same on either loader.

The most common causes are a wrong folder path, malformed JSON, or a missing namespace in the file. Double-check that your file sits in the correct data directory, that the JSON is valid, and that the structure ID you reference actually exists.

Yes, it's designed to support those mods and others that use its structure config system. If a supported mod is installed, Cristel Lib handles the config loading so their structures spawn correctly.

You can change the configs, but structures already generated in explored chunks won't move. New chunks generated after the config change will use the updated rules, so test in fresh areas.

Cristel Lib itself is lightweight since it's just a config library, so it shouldn't cause noticeable lag. Performance issues usually come from the mods using it or from very large datapacks with many structure entries.

Code-based configs are written by mod developers and compiled into the mod, so players can't easily edit them. Data-based configs live in datapacks, which means players and pack makers can add or tweak structure rules in-game without touching code.