Tags
Creators
Details
3.4.0+1.20.1-forge
Compatibility
Required content
Changes
YetAnotherConfigLib 3.4.0
This build supports the following versions:
- Fabric 1.20.1
- Fabric 1.20.4
- Fabric 1.20.5
- Forge 1.20.1
- NeoForge 1.20.4
For developers...
This is the first build which uses a new build toolchain to support multiple minecraft versions in the same codebase. With this change, the artifact of the mod has changed.
modImplementation "dev.isxander:yet-another-config-lib:{modversion}+{mcversion}-{loader}"
// for example...
modImplementation "dev.isxander:yet-another-config-lib:3.4.0+1.20.1-fabric"
If you are using YACL in an architectury project (one with a common subproject), you will from now on depend on the fabric version of YACL. There is no longer any common artifact. I don't believe there to be any issues with doing it like this.
Additions
- New colour picker widget by Superkat32
- This works with existing colour options.

- Added a custom tab API so categories can provide their own GUI, instead of YACL options.
- Mod developers can make their category class implement
CustomTabProvider. Javadoc is available.
- Mod developers can make their category class implement
- Add a new Kotlin DSL for creating your YACL UIs. This is a wrapper on top of the java builder interface providing extra functionality for Kotlin users.
- YACL does not provide any kotlin libraries, nor does it depend on them. If you would like to use this DSL, make sure your own mod depends on your loader's Kotlin mod.
- This is included in the main artifact. You don't need additional dependencies.
- An example usage can be found in the testmod
- Improved the backend of dropdown controllers by Crendgrim
Bug Fixes
- Fix GIFs not being preloaded in the resource reloader
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:WTCAdLsq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1eAoo2KR:WTCAdLsq"
}

