
Dynamic Registries
Allows other mods to create data-pack based registries
About this Mod
dynamic registries
Dynamic registries is a library mod that allows the creation of new data-pack based registries. It's possible to define elements in code and trough data-packs (even the data-pack in your mod), but not necessary; you can also create elements only in code or in data-packs. Elements that were defined in code can also be overwritten from data-packs. Elements must be encoded in JSON.
This library is based on the changes introduced in this PR. This PR probably isn't going to be merged before 1.18.2 gets released, but I needed this feature already for 1.18.1, so I wrote this mod. There won't be versions of this library for other Minecraft version for this reason.
How to add this library to your mods dependencies
To add the library to your gradle setup, add modrinth to your dependency repositories.
repositories {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
content {
includeGroup "maven.modrinth"
}
}
}
Add the above codeblock to your build.gradle above your dependencies block (the order doesn't matter that strong, but lets assume that you've placed it there to simplify things a bit). If you already had a repositories block, only append the maven block to it.
We now define the dependency itself. Add the line below to your dependencies block in your build.gradle. Version 0.1.0 was the latest at time of writing. Replace that with the latest currently available version.
implementation fg.deobf("maven.modrinth:dynamicregistries:0.1.0")
You can now refresh your gradle project to download the dependencies and re-run IDE setup tasks (genIntellijRuns, genEclipseRuns or genVSCodeRuns)
You can now use dynamic registries in your development setup, but you should make the forge mod-loader check for it's dependencies when loading. That requires changes in your mods.toml (in src/main/resources/META-INF). Add the following block at the end of the file
[[dependencies.modid]]
modId = "dynamicregistries"
mandatory = true
versionRange = "[0.0.0,2.0.0)"
ordering = "NONE"
side = "BOTH"
Replace modid with the modid of your mod and rearrange the version range if necessary
Credits
- Won-Ton, the author of the PR that was the base for this library
- Mod Icon: flaticon.com
Available Versions
How to Install Dynamic Registries on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set forge Loader
In the panel under "Egg", select the forge loader and matching Minecraft version (1.18.1).
Install Mod
Open the mod browser in the dashboard and search for "Dynamic Registries". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
1.18.1
Server-side
✓ RequiredRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Dynamic Registries server crashes on startup – what to do?
Most common cause: wrong forge version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (1.18.1). You can switch loaders with one click in the panel.
Is Dynamic Registries compatible with forge?
Dynamic Registries officially supports forge for Minecraft 1.18.1. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Dynamic Registries – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Dynamic Registries consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Dynamic Registries with just one click on your server.