All versions
0.6.5-fix1+1.20.1+forge
Release
fzzy_config-0.6.5-fix1+1.20.1+forgelast year 17K
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Changes
Reminder of breaking changes in 0.6.x
ValidatedEntityAttributeis removedCustom[Widgets]are moved from the internal widget package to the custom package- Several widgets and other classes have been deleted
PopupWidgethas many deprecations, and probably at least one breaking change despite my best efforts. Deprecations scheduled for removal 0.7.0- As of 0.6.3,
ActiveButtonWidgetis unused and deprecated, marked for removal by 0.7.0 - As of 0.6.3,
TextlessActionWidgetis unused and deprecated, marked for removal by 0.7.0 - Possibly more, I didn't take great notes
As of 0.6.0, 1.20.4 and 1.20.6 will no longer be receiving active updates.
Additions
- New
registerLenientS2CandregisterLenientC2Smethods in theNetworkApi. These methods will be propagated to all versions of Fzzy Config in 0.6.6, though in most versions will have no behavior difference compared toregisterS2C/C2S
Changes
- Internal Fzzy Config packet registrations now register leniently.
NetworkApi.canSendnow checks that one of it's registered methods can in fact send.
Fixes
- Fixed clients without Fzzy Config being prevented from joining a server with it. Obviously configs will not be synced in this circumstance, FC will simply pretend that client doesn't exist. Mods that can allow this behavior should of course also handle this circumstance.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| fzzy_config-0.6.5-fix1+1.20.1+forge-sources.jar | Unknown | 596.25 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:hYykXjDp:6FpN9Bn7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hYykXjDp:6FpN9Bn7"
}


