Getting Started

Elib 1.4+26.3 targets Minecraft 26.3 and Java 25. It runs on the client. Choose one Elib artifact for each loader-specific module of your mod.

Add the Maven repository

In the relevant Gradle project, add the release repository:

repositories {
    maven {
        url = uri('https://maven.elpu7.dev/releases')
    }
}

Add the dependency

These Groovy Gradle examples use the same implementation configuration as the Elpu7 mods that consume Elib:

Loader	Dependency
Fabric	implementation 'dev.elpu7:elib-fabric:1.4+26.3'
NeoForge	implementation 'dev.elpu7:elib-neoforge:1.4+26.3'
Quilt	implementation 'dev.elpu7:elib-quilt:1.4+26.3'

Add only the line for your loader. If your build uses a different dependency configuration for mod JARs, use that configuration instead. Do not shade Elib into your mod: users need Elib installed as a separate mod.

Declare the runtime dependency

Your mod's loader metadata must require elib at runtime. As an example, a Fabric fabric.mod.json can include:

"depends": {
  "elib": ">=1.4+26.3",
  "fabric-api": "*"
}

Elib's Fabric build requires Fabric API. Declare it if your Fabric mod needs Elib. For NeoForge, add an elib dependency to neoforge.mods.toml; for Quilt, add it to quilt.mod.json. Specify the minimum Elib version that your mod has actually been tested with. If you publish on Modrinth, also mark Elib as a required project dependency for each loader-specific version.

Once the dependency is available, continue with Config-Menu-Integration or Config-Storage. You can use either feature independently.