owo-lib — Guide

Which Mods Need It

Install owo-lib whenever a mod you use lists it as a dependency. If it is missing, those mods will fail to load and the game will report a missing-dependency error for the mod id owo.

• Accessories depends on owo-lib - so any mod that uses the Accessories slot framework needs owo-lib in the mods folder as well.
• Through that chain, the Aether and other accessory-using mods rely on owo-lib.
• Various other mods that use owo's UI, networking, or config systems also require it.

Because it is a shared dependency, the rule of thumb is simple: add owo-lib when a mod tells you to, and leave it out otherwise.

Developer API

owo-lib is meant to be consumed by other mods as a dependency (mod id owo).

Adding it to a dev environment (Gradle):

repositories {
    maven { url " }
}
dependencies {
    // use the artifact/version that matches your Minecraft + loader
    modImplementation "io.wispforest:owo-lib:<version>"
}

Declare the dependency in your mod metadata so the game enforces load order, referencing the mod id owo.

Key entry points (package root io.wispforest.owo): - UI - io.wispforest.owo.ui - the declarative component/layout system for building screens and HUD overlays. - Networking - io.wispforest.owo.network (OwoNetChannel) - type-safe client/server packet channels. - Config - io.wispforest.owo.config - annotation-driven configs with auto-generated option screens. - Registry & items - helpers such as FieldRegistrationHandler and OwoItemGroup for registration and creative tabs.

Consult the upstream owo-lib documentation for full API details and current version coordinates.