All versions
0.7.6+26.2+neoforge
Release
fzzy_config-0.7.6+26.2+neoforge3 weeks ago 2,032
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Breaking changes in 0.7.x
ValidatedEnumMapis removed- Removed all methods and properties marked as Deprecated and for removal 0.7.0
SmallSpriteDecoration#<init>SpriteDecorated#textureSet&texturesis now a required overrideSpriteDecoration#<init>CustomButtonWidget#<init>& builder is now only non-override method for adding custom button- Removed
ActiveButtonWidget - Removed
TextlessActionWidget DynamicListWidget.EntryPosand implementations madeinternalPopupWidgetposition elements;LayoutWidgetno longer inherits from the PopupWidget variant- Removed deprecated overrides of
PopupControllerfromPopupParentElement SuggestionWindowListenerandSuggestionWindowProvidermoved out ofinternalsub-package- Removed
ImmutableRelPos RenderUtil#renderBlur
- Throughout FzzyConfig
Translatable.Resulthas been replaced withTranslatable.ResultProvider. This affectsEntrySearcheras well asSearcher.SearchContent
Additions
- Various documentation updates for the Provider systems, including a wiki update
Changes
ValidatedField.translationProvider,ValidatedField.descriptionProvider,ValidatedField.attachProvider, and the associatedProvidertypes are now static (as well as instance methods) so java users won't have to call.Companion.anymore (but can)
Fixes
- Deprecated settings are properly read in from file for handling. They are still ignored in network traffic.
- The options in
ValidatedChoiceListand similar settings with an "inline" widget layout now properly show the tooltip for the individual options as well as the settings overall tooltip
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:lGlPvgBc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hYykXjDp:lGlPvgBc"
}


