Tags
Creators
Details
0.13.0+1.21.11
Compatibility
Required content
Changes
API Renamings
In preparation for future unobfuscated versions of the game, owo-lib is now developed using the official Mojang Mappings and relevant API elements have been renamed accordingly. Besides a number of straight-forward adaptations (like World -> Level), this also meant that the core class of owo-ui (previously Component) had to be renamed to UIComponent to avoid a name collision with net.minecraft.network.chat.Component. Related classes follow suit, e.g. ParentComponent -> ParentUIComponent, Containers -> UIContainers.
Language Extensions
In addition to Rich Translations, owo-lib now supports nested language files which help to greatly reduce repetition in language keys. Additionally, to reduce conflict potential, all of owo's language extensions are now opt-in. Check out the relevant section of the docs.
JSON5 Support
The majority of JSON files in any data/resource pack can be converted to use JSON5 when owo-lib is configured to read and convert them to JSON on-the-fly. Once again, check out the docs.
braid UI framework
Due to unforeseen technical circumstances (I did not want to remap the entire library twice), this build includes an early pre-alpha version of the upcoming braid UI framework. While reasonably well-tested and somewhat mature feature-wise, we do not consider it ready for release and we make absolutely no guarantees about API stability.
If you want to try it out or toy around with it anyways, check out the getting started guide. We'd love to get some early feedback!
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| owo-lib-0.13.0+1.21.11-sources.jar | Unknown | 722.09 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:ccKDOlHs:33Ei8Thm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ccKDOlHs:33Ei8Thm"
}

