Tags
Creators
Details
Licensed MPL-2.0
Published 5 years ago
Updated last month
All versions
3.2.4
Release
[FABRIC] [1.18.2] ForgeConfigAPIPort-v3.2.44 years ago 108.4K
Compatibility
Minecraft: Java Edition
1.18.x
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Unavailable version
Changes
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
[v3.2.4-1.18.2] - 2022-08-20
Changed
- Fabric Api is no longer bundled again, was causing issues with Quilt and was an inconvenience when bundling the mod as jar-in-jar
Fixed
- Fixed missing sub-folders not being created for configs not in the main config directory
[v3.2.3-1.18.2] - 2022-08-02
Fixed
- Fixed required version of Fabric Api
[v3.2.2-1.18.2] - 2022-08-01
Fixed
- Fixed start-up crash due to wrong dependency
[v3.2.1-1.18.2] - 2022-07-31
- Bundled Fabric API, it's no longer an external dependency
- Publish latest 1.18.2 build to Maven and Modrinth
[v3.2.0-1.18.2] - 2022-03-03
- Compiled for Minecraft 1.18.2
[v3.1.1-1.18.1] - 2022-01-10
Fixed
- Fixed a bug where the game would crash during start-up due to the required config library not having been loaded yet
[v3.1.0-1.18.1] - 2021-12-12
- Compiled for Minecraft 1.18.1
[v3.0.1-1.18] - 2021-12-06
Fixed
- Hopefully fixed a bug where config loading would very rarely lead to an exception due to the toml file format not being recognized
[v3.0.0-1.18] - 2021-12-02
- Ported to Minecraft 1.18
Optional dependencies
Unavailable version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| ForgeConfigAPIPort-v3.2.4-1.18.2-Fabric-sources.jar | Unknown | 73.18 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:ohNO6lps:XGKEYlsw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ohNO6lps:XGKEYlsw"
}

