01
Structured configuration
Ukulib provides a configuration system that dependent mods can use instead of implementing the full settings layer independently.
Ukulib Mod reference
Use Ukulib Mod with the right version, loader, and dependency match.
Ukulib is a client-side Minecraft library that supplies shared configuration systems, interface widgets, and utility code for compatible mods. This guide helps players and modpack builders separate the modern 2.x line from legacy 1.21.x builds before they change a working profile.
Current 2.2.0+26.3 contextFabric + NeoForge guidanceLegacy 1.21.x compatibility
Library roleShared client utilities, settings, and widget infrastructure
Modern loader splitSeparate 2.x builds for Fabric and NeoForge profiles
Version readingMinecraft target appears after the plus sign in the release label
Profile planningCheck Minecraft version, loader, dependent mod range, and current Ukulib line before updating.
Better troubleshootingDependency issues are easier to solve when only one library version is present in the mods folder.
Safer updatesKeep the latest 2.x builds separate from legacy 1.21.x releases used by older setups.
What is Ukulib Mod?
A reusable client-side library, not a content pack.
The official project describes Ukulib as a Minecraft library built for the developer's collection of mods. Its current documentation highlights configuration infrastructure, config-screen widgets, and general Minecraft utilities.
Configuration systemShared structures help dependent mods define and present settings consistently.
UI utilitiesReusable widgets reduce the need for every dependent mod to rebuild interface components.
Multi-loader architectureThe 2.x line separates common code from Fabric and NeoForge platform builds.
Client-focused dependencyIts project metadata identifies Ukulib as a client-side library.
Features
What the library is designed to provide.
These are the practical feature areas documented by the current project rather than invented gameplay claims.
02
Config-screen widgets
The library includes utilities and reusable widgets intended for building cleaner configuration screens and text-input interactions.
03
Minecraft utilities
Shared Minecraft-facing helpers give related mods a common place for frequently reused client-side functionality.
04
Fabric / NeoForge split
Current 2.x development uses common, Fabric, and NeoForge artifacts so loader-specific code can stay separated from shared logic.
How it works
Three checks make version selection much easier.
Ukulib's version format and loader split give you a predictable way to validate a setup before launch.
1
Read the Minecraft suffix
A version such as 2.2.0+26.3 targets Minecraft 26.3. For the legacy line, 1.10.2+1.21.11 targets Minecraft 1.21.11.
2
Match the loader build
Use the Fabric build for Fabric profiles and the NeoForge build for NeoForge profiles. Current loader-specific artifacts are intentionally separate.
3
Verify the dependent mod
The mod that requires Ukulib is the final authority on the acceptable dependency range. Confirm its requirement before replacing a working library version.
Compatibility
Separate the modern 2.x line from legacy Minecraft builds.
The official 2.x documentation starts with Minecraft 26.1 and later, while the release history keeps older 1.x builds for Minecraft 1.21.x and earlier targets. Do not treat “latest” as automatically correct for an older profile.
2.2.0+26.3
Current release target: Minecraft 26.3.
Current release target: Minecraft 26.3.
2.0+ architecture
Fabric and NeoForge with a shared common code layer.
Fabric and NeoForge with a shared common code layer.
1.10.2+1.21.11
Legacy release specifically targeting Minecraft 1.21.11.
Legacy release specifically targeting Minecraft 1.21.11.
Loader match
Dependent mod + Minecraft + loader + Ukulib must agree.
Dependent mod + Minecraft + loader + Ukulib must agree.
Use cases
Where Ukulib fits into a modded setup.
Required dependency
A compatible client mod can declare Ukulib as required so shared configuration and utility classes are available at launch.
Multi-loader mod development
Developers can keep shared logic in the common artifact while using Fabric or NeoForge implementations where platform behavior differs.
HUD and interface mods
Projects such as armor-hud are cited in the official setup documentation as concrete examples that can use Ukulib's shared layer.
Installation / Setup
Keep player installation separate from developer source code.
For normal gameplay, a loader-compatible built JAR belongs in the profile's mods folder. A repository ZIP is source code and should not be mistaken for the installable JAR.
A
Back up the instance
Preserve worlds, the current mod list, and configuration files before changing a library dependency in a working profile.
B
Use the correct build
Match the dependent mod's required Ukulib range, Minecraft target, and Fabric or NeoForge loader before placing the JAR in the mods folder.
C
Launch with minimal changes
Test the required mod set first. If the game fails, inspect the first relevant dependency, mixin, or loader message in the latest log.
Download
Download the Ukulib Mod source archive.
The button below uses the project source archive supplied for this site. Important: a source ZIP is not the same thing as a ready-to-install loader JAR. Players should confirm the correct built release for their exact Minecraft version and loader before changing a profile.
Download Ukulib Mod
Safety notice
Dependency safety is mostly about provenance, version control, and backups.
Keep a restorable copy of the instance, avoid duplicate library files, use loader-appropriate releases, and verify what a downloaded archive actually contains before moving it into a game profile. This site is an independent reference and is not affiliated with the Ukulib project or third-party platforms.
Pros and cons
What a shared client library changes.
Advantages
- Centralizes configuration and utility code used by multiple compatible mods.
- Supports a cleaner split between common logic and loader-specific implementations in the 2.x line.
- Clear Minecraft target suffixes make release intent easier to read.
Trade-offs
- A library mismatch can stop dependent mods from loading even when the rest of the profile is correct.
- Loader-specific builds add one more compatibility dimension that must be matched.
- Updating the library independently can break a dependent mod that expects an older API range.
Current release context.
The official release history lists 2.2.0+26.3 as the latest release, dated September 15, 2026.
Its notes include the Minecraft 26.3 update, TextInputWidget internal changes, deprecation of getText/setText in favor of getValue/setValue, and updated NeoForge icon metadata.
Latest line
2.2.0+26.3
2.2.0+26.3
2.x loaders
Fabric + NeoForge
Fabric + NeoForge
Legacy 1.21.11
1.10.2+1.21.11
1.10.2+1.21.11
License
MPL-2.0
MPL-2.0
Troubleshooting
Diagnose the dependency chain before replacing random files.
Missing Ukulib
Confirm the JAR is inside the same launcher instance being started, then verify that its loader matches the instance.
Wrong version range
Compare the dependent mod's declared requirement with the installed Ukulib version instead of assuming the newest release is compatible.
UI or title-screen issue
If you are on the 26.2 line, note that 2.1.1 specifically fixed ModMenu title-screen button compatibility and Ukulib button visibility behavior.
Guides preview
Deeper guides for versions, loaders, and setup.
Ukulib Mod Features: What the Library Actually Provides
Configuration architecture, interface widgets, utility code, and the multi-loader split explained in practical terms.
Read guide →
Ukulib Mod Fabric Setup Guide
Choose the Minecraft target, verify the Fabric build, and avoid the most common dependency-placement mistakes.
Read guide →
Ukulib Mod Version Compatibility Explained
Understand the difference between the 2.x Minecraft 26.x line and legacy releases such as 1.10.2+1.21.11.
Read guide →FAQ
Ukulib Mod questions, answered with version context.
Exactly 20 software-specific answers grouped into compatibility and setup topics.
Ukulib is a client-side Minecraft library mod used by the developer's other mods. It provides shared configuration, screen-widget, and Minecraft utility code instead of acting as a large standalone content mod.
Ukulib 2.0 moved the current line to Minecraft 26.1+, added NeoForge support, removed deprecated APIs, and split development artifacts into common, Fabric, and NeoForge variants.
The current 2.x documentation explicitly covers Fabric and NeoForge. Match the loader-specific build to the profile instead of treating the files as interchangeable.
Ukulib uses semantic-style library versions plus a suffix for the targeted Minecraft release. In 2.2.0+26.3, 2.2.0 is the library version and 26.3 is the Minecraft target.
The official 2.x documentation is for Minecraft 26.1 and later. Minecraft 1.21.x uses the earlier 1.x release line, including 1.10.2+1.21.11 for Minecraft 1.21.11.
Its main role is shared infrastructure for dependent mods, including configuration and utility code. Most players encounter Ukulib because another mod requires it.
Yes. The official setup documentation points to armor-hud as an example of a project using Ukulib. The HUD behavior comes from the dependent mod, while Ukulib supplies shared library functionality.
The official project listing marks Ukulib as client-side, and the current NeoForge dependency example also declares the library on the client side.
Do not assume so. Current development artifacts are loader-specific, with ukulib-fabric and ukulib-neoforge variants, so the installed file must match the loader used by the profile.
The official repository and project listing identify Ukulib as licensed under MPL-2.0.
Start with the dependent mod's requirement, then match Minecraft version and loader. For 2.x releases, the suffix after the plus sign identifies the intended Minecraft target.
For a normal player profile, place the compatible loader-specific JAR in that instance's mods folder. Make sure the launcher is starting the same instance you edited.
No. A repository source ZIP contains project source files and is mainly useful for inspection or development. A normal Minecraft profile expects the matching built JAR for its loader and game version.
The usual causes are installing the file into a different launcher instance, using the wrong loader build, or choosing a version outside the range required by the dependent mod.
Avoid duplicate library versions unless a specific setup explicitly documents that arrangement. Duplicate or incompatible copies can create dependency resolution or class-loading conflicts.
Verify the dependent mods still accept the new version, keep the loader consistent, launch with a minimal required set first, and review the latest log before changing more files.
The official release history includes 1.10.2+1.21.11 for Minecraft 1.21.11. Keep that legacy line separate from the newer 2.x releases that target Minecraft 26.x.
The 2.2.0 release updated the project to Minecraft 26.3, reworked TextInputWidget internals, deprecated getText and setText in favor of getValue and setValue, and changed NeoForge mod icon metadata to iconFile.
The 2.1.1 release notes describe compatibility fixes for ModMenu's title-screen button and a fix for the player head not disappearing when the Ukulib button is disabled.
Work from the first relevant dependency or loader error in the log, confirm Minecraft and loader versions, remove duplicate libraries, then test with only the required mod set before restoring the rest of the profile.