Tags
Creators
Details
All versions
0.3.0+26.2-neoforge
Beta
Syrup Library 0.3.0+26.2-neoforge5 days ago 5
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
0.3.0
Added
- Minecraft 26.3 support for Fabric and NeoForge.
- Generic config types with shared validation and constraints.
- Atomic config updates and saves with structured diagnostics.
- Client config screens for Fabric, Forge, and NeoForge.
- Mod Menu integration for Fabric.
- Config editor support for booleans, numbers, strings, lists, enums, and custom types.
Changed
- Config files now use the generic schema API.
- Config values keep immutable configured, effective, and startup snapshots.
- Missing schema values are filled into JSON5 files.
- Config specs can set an owning mod ID for loader config screens.
Breaking changes
- The typed config value wrapper classes were removed.
- Existing 0.2.x consumers must stay on 0.2.x or migrate to the generic API and rebuild.
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:9tBNzmjo:YJtXkpaK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9tBNzmjo:YJtXkpaK"
}

