This is used in many of our Fabric mods
Instead of having to manually register each and every thing, you can simple extend
or implement
one of our RegistryContainer
classes.
These utility interfaces are recognised by our mod by sticking RegistryContainer.register(ClassName.class, MOD_ID
into your mods #onInitialize
method.
We provide a custom class called SimpleDatapackRegistry
This allows your own classes to be read and registered straight from datapacks with ease!
For the kit to recognise your registry, in your mods #onInitialize
method, you need to call register
on your instance OR AmbleRegistries.register(MyRegistry.getInstance()))
We utilise annotations and the previously mentioned registry containers to automatically generate many features.
For example, automatic english translation for blocks -
By simply creating an instance of AmbleLanguageProvider
and passing in your BlockContainer
with the #withBlocks
method, next time you run datagen all these blocks will have english translations based off their identifiers.
There are more datagen utilities akin to this.
Github Template for Fabric 1.20.1 Modkit
repositories {
maven {
url "https://jitpack.io"
metadataSources {
artifact() // Look directly for artifact
}
}
}
dependencies {
modImplementation("com.github.amblelabs:modkit:${project.modkit_version}") {
exclude(group: "net.fabricmc.fabric-api")
}
}
or if you are using kotlin
repositories {
maven {
url = uri("https://jitpack.io")
metadataSources {
artifact() // Look directly for artifact
}
}
mavenCentral()
}
dependencies {
modImplementation("com.github.amblelabs:modkit:${project.property("modkit_version")}")
}
GitHub • CurseForge • Modrinth • Discord