Tags
Creators
Details
Licensed MPL-2.0
Published 5 years ago
All versions
v20.4.3-1.20.4-Fabric
Release
[FABRIC] [1.20.4] ForgeConfigAPIPort-v20.4.32 years ago 747.7K
Compatibility
Minecraft: Java Edition
1.20.4
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Changes
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
[v20.4.3-1.20.4] - 2024-01-22
Fixed
- Fix
mods.tomlentries for NeoForge
[v20.4.2-1.20.4] - 2024-01-13
Changed
- Implement
UnmodifiableConfigWrapperforIConfigSpecadapters on NeoForge & Forge
[v20.4.1-1.20.4] - 2024-01-10
- Huge internal restructure, including new publications for NeoForge (for using Forge configs) and Forge (for using NeoForge configs)
- The Fabric publication still includes all classes for both config systems, the api package has been split from
fuzs.forgeconfigapiport.api.configintofuzs.forgeconfigapiport.fabric.api.forgeandfuzs.forgeconfigapiport.fabric.api.neoforge - The common module is no longer published as
forgeconfigapiport-common, instead there are now two common publications which areforgeconfigapiport-common-forgeapiandforgeconfigapiport-common-neoforgeapi
Added
- Added
disableConfigWatcherconfig option to bothForgeConfigSpecandModConfigSpec
Changed
- Updated ForgeConfigSpec with changes from MinecraftForge#9810
Fixed
- Fixed
FileWatcherhanging due to an invalid path when unloading server configs
[v20.4.0-1.20.4] - 2023-12-21
- Updated to Minecraft 1.20.4 (thanks to Girafi for helping out!)
- The mod version now is more streamlined by including the targeted Minecraft version (e.g. Minecraft 1.20.4 -> Mod Version 20.4.X)
Optional dependencies
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:ohNO6lps:xbVGsTLe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ohNO6lps:xbVGsTLe"
}


