Creators
Details
All versions
0.2.0
Release
Configory v0.2.0last month 152
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
Platforms
Fabric
Forge
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
0.2.0 (2026-07-08)
⚠ BREAKING CHANGES
- A config's id now maps to its file location and dotted paths are pure JSON nesting (previously the first path segment selected the file). The on-disk layout is now config/<id>.json (plus config/<id>/<name>.json for extra configs), ConfigPath dropped file()/DEFAULT_FILE, and Config.save(String) / dirtyFiles() were removed in favor of save() / isDirty(). See #43.
Added
- Add a type-agnostic display-string accessor to ConfigValue (#45) (8b29a41)
- Add defineX shorthand for typed config definitions (#19) (4361b1c)
- Add presence checks to ConfigValue for dynamic path reads (#23) (122a1cd)
- Add strict-bound and finite-float numeric constraints (#44) (14b07e1)
- Add trySet for validating dynamic writes without throwing (#24) (6c213c0)
- Allow injecting ConfigStorage through the registry and bootstrap (#41) (744e80f)
- Config id maps to the file location; paths are pure nesting (806721e)
- Declare per-loader Minecraft compatibility and add Forge (#55) (0592ebd)
- Generate a Brigadier command surface for config keys (#53) (b166660)
- Map the config id to the file location and make paths pure nesting (#43) (d7bcf3c)
- Publish to Modrinth Maven and document installation (#20) (fbb76f7)
- Ship Fabric and NeoForge metadata so Configory installs as a library mod (#22) (1b1a24f)
- Support enum-typed config keys (#46) (d08cee0)
- Write defaults to disk on first bootstrap load (#48) (4eef472)
Fixed
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| configory-0.2.0-sources.jar | Unknown | 40.65 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:aoem3zBJ:FotZI0Ns"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aoem3zBJ:FotZI0Ns"
}

