Tags
Creators
Details
3.0.0+1.19.4-fabric
Compatibility
Changes
YetAnotherConfigLib v3
3.0 of YACL introduces a new UI layout, taking advantage of 1.19.4's new tab system!
Description Panel
The description panel takes the place of the old category buttons, you can now interact with the text by clicking or hovering and the description can contain an animated WebP file or a static image. This can help you as a developer to portray what your option does with an actual example. Like the old tooltip system, these descriptions can dynamically change based on the value of the option, including the image. After a few seconds of hovering, the description will start to auto-scroll if necessary so inputs such as controller can still use the UI.
.description(OptionDescription.createBuilder()
.text(Text.literal("Line 1"))
.text(Text.literal("Line 2"))
.webpImage(new Identifier("mymod", "config/screenshots/config_example.webp"))
.build())
the above is applicable to both groups and options
Tab System
YACL now uses a slightly modified version of 1.19.4's new create world screen, this adds tab overflow, so you can scroll through the tabs in case there are too many to fit on the screen.
Controller Builders
Controllers now use a builder system, rather than using constructors. This allows for more flexibility in the future.
You can still use your own controller implementations without creating a builder, using .customController().
For mod developers...
This update is for both 1.19.4 and 1.20, there is complete API parity. 1.20 is now the active branch, and 1.19.4 is now considered LTS and may receive features from 1.20 at a later date.
For users/modpack developers...
YACL 3.0 includes the old 2.x inside the new JAR. So you can safely upgrade to 3.0 without breaking mods that have not yet updated. However, the old UI will still be present for this outdated mods.
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:1eAoo2KR:Vc0cNGqC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1eAoo2KR:Vc0cNGqC"
}

