Tags
Creators
Details
Licensed MPL-2.0
Published 5 years ago
All versions
v21.0.8-1.21-Fabric
Release
[FABRIC] [1.21] ForgeConfigAPIPort-v21.0.82 years ago 1.05M
Compatibility
Minecraft: Java Edition
1.21
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Changes
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[v21.0.8-1.21] - 2024-08-06
Changed
- Update for NeoForge 21.0.159
[v21.0.7-1.21] - 2024-07-29
Changed
- Update for NeoForge 21.0.143
[v21.0.6-1.21] - 2024-07-26
Added
- Add new configuration screen for NeoForge configs, must be enabled via
ConfigScreenFactoryRegistry::register - Not compatible with Forge configs, and will crash in-game
[v21.0.5-1.21] - 2024-07-15
Changed
- Allow
net.minecraftforge.fml.config.ModConfig::saveto still be usable
[v21.0.4-1.21] - 2024-07-15
Fixed
- Fix
net.minecraftforge.fml.config.ModConfig::getFullPaththrowing aClassCastException - The class remains deprecated though and is only kept for binary compatibility
[v21.0.3-1.21] - 2024-07-15
Changed
- Add a few deprecation notices to highlight the internal migration to NeoForge's config system for Forge on Fabric, that will require registering Forge config classes via the NeoForge implementation in the future
- Add back contents to Forge's
ModConfigas it is still used in config events, it now serves as an adapter to NeoForge'sModConfigfor registered Forge configs
Fixed
- Fix Forge config events not being called on Fabric
[v21.0.2-1.21] - 2024-07-13
- Updated to Night Config v3.8.0
- Update for NeoForge v21.0.82
Changed
- Remove internal Forge classes from the Fabric publication, NeoForge's system is used to benefit from the concurrency safety it provides
- There should be no breaking changes in any public facing api classes
[v21.0.1-1.21] - 2024-07-01
- Updated for Night Config v3.7.0
Fixed
- Common publications no longer try to pull Fabric Loader
[v21.0.0-1.21] - 2024-06-14
- Update to Minecraft 1.21
- Forge distribution remains unpublished as long as it is not supported by Architectury Loom
Optional dependencies
Any compatible version
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:GOreNSW6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ohNO6lps:GOreNSW6"
}

