
Modrinth · Minecraft mod
Unified API
A comprehensive data-driven multiloader modding api built for both modders and data-packers
Quick answer
Which Unified API release should I use?
Unified API 26.2-r2.5-fabric targets 26.2 with Fabric. Installation on the client is optional. Installation on the dedicated server is optional. No extra mods listed for this file.
Where it goes
Is Unified API required on the client, server, or both?
Installation on the client is optional. Installation on the dedicated server is optional.
The source marks this as usable on both the client and server.
What else does Unified API 26.2-r2.5-fabric need?
26.2-r2.5-fabric. Change the file and its required mods may change too.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add Unified API without breaking your instance.
Built for Unified API 26.2-r2.5-fabric. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use 26.2-r2.5-fabric. It targets 26.2 with Fabric; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
Installation on the client is optional. Installation on the dedicated server is optional.
- 04
Pick the file you checked
Use the “Get this file” button beside 26.2-r2.5-fabric. It opens that exact file at the source.
About this project
What does Unified API add?
About
Unified API is a cross-loader API for both Fabric & NeoForge that enables you to create multiloader mods at no additional effort.
It is also a data-focused library that provides powerful new features to datapacks and resource packs, including data-driven blocks, items, entity variants and much more.
Additionally, this library is an advanced data generator for modders, with unified registration generators that put all your block, item and entity code in the one place.
The goal of this project is to provide an up-to-date, efficient & flexible way of creating modded content at a much faster pace than what is typically afforded both by competing multiloader projects and the official loaders themselves.
To prove the true extent of these features, you'll need to visit the Unified API Documentation.
Feature Highlights
All-in-one registration generation.
Register your content in one place. All behaviour is handled by vanilla and Unified API-specific JSON, generated from this code. JSON can then be overriden by users or other projects for full customisability.
public static final SuppliedItem EXAMPLE_ITEM = ITEMS.register(
"example_item",
VanillaItemCodecs.ITEM.create(),
builder -> builder
.properties(properties -> properties
.stacksTo(16)
.rarity(Rarity.UNCOMMON)
)
.assets(assets -> assets
.handheld()
)
.data(data -> data
.dropSelf()
)
);
Data-driven Registries
Blocks, Items, Entities, Creative Tabs, Sound Events and more can all be created via JSON.
{
"type": "minecraft:block",
"properties": {
// properties go here
}
}
Traditional Multiloader Deferring
In a multiloader environment, your content needs to be deferred. UnifiedRegistries coupled with Supplied<Object> handles this much like other multiloader projects, with some convenient bonuses.
Extensive Events & Helpers
Modify biome attributes or features, change default components, inject loot tables or alter individual entries, create mob variants and much more - supported via both code-driven events and data-driven listeners.
Furthermore, there is a full networking api, data attachments, structure-specific music and anything else you'd expect to need when making complex mods.
Instantly create entire sets
Common, tedious-to-create content like woodsets, brick sets, colored sets, equipment sets and more can be generated as JSON in an instant, with all functionality you'd normally spend a while creating manually. Cutting down on meaningless busywork was a major motivator in creating Unified API over using options already out there.
An Absurd Amount More
The goal of Unified API is to drastically reduce the time it takes to add modded content, whilst additionally exposing many new features to non-modders. You do not need to use another api alongside this one, and migration from your existing systems should be relatively simple considering the inclusion of more traditional registries alongside new, more agile features.
Once again, be sure to check out unified-api.dev for documentation and the full feature set!
Project description from Modrinth.
Pick your setup
Unified API by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
26.2
2 loader builds26.1.2
2 loader builds26.1.1
2 loader builds26.1
2 loader buildsCheck the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
Unified API versions and loaders
26.3-1.0-beta-19-fabric
unified-api-26.3-1.0-beta-19+fabric.jar
16 Oct 2026
26.3-1.0-beta-19-neoforge
unified-api-26.3-1.0-beta-19+neoforge.jar
16 Oct 2026
26.2-1.0-beta-19-fabric
unified-api-26.2-1.0-beta-19+fabric.jar
16 Oct 2026
26.2-1.0-beta-19-neoforge
unified-api-26.2-1.0-beta-19+neoforge.jar
16 Oct 2026
26.1-1.0-beta-19-fabric
unified-api-26.1-1.0-beta-19+fabric.jar
16 Oct 2026
26.1-1.0-beta-19-neoforge
unified-api-26.1-1.0-beta-19+neoforge.jar
16 Oct 2026
26.1-1.0-beta-18-fabric
unified-api-26.1-1.0-beta-18+fabric.jar
16 Oct 2026
26.1-1.0-beta-18-neoforge
unified-api-26.1-1.0-beta-18+neoforge.jar
16 Oct 2026
26.1-1.0-beta-17-fabric
unified-api-26.1-1.0-beta-17+fabric.jar
16 Oct 2026
26.1-1.0-beta-17-neoforge
unified-api-26.1-1.0-beta-17+neoforge.jar
16 Oct 2026
26.3-1.0-beta-16-fabric
unified-api-26.3-1.0-beta-16+fabric.jar
15 Oct 2026
26.3-1.0-beta-16-neoforge
unified-api-26.3-1.0-beta-16+neoforge.jar
15 Oct 2026
Looking for an older file? The official Modrinth project page is in Resources.