All versions
0.5.6+1.21+neoforge
Release
fzzy_config-0.5.6+1.21+neoforge2 years ago 2,930
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Additions
- Added a flag system
EntryFlagtoValidatedFieldandConfigAction. Currently only has one flagREQUIRES_WORLD. A field marked with REQUIRES_WORLD marks that the player needs to be in-game for the setting to work properly. The config screen will show Not in Game instead of the setting, when not in game. - Added
ofDynamicKeybuilder methods toValidatedIdentifier. Use ofofRegistryKeyfor non-synced dynamic registries (Loot registries, or modded dynamic registries that don't sync, primarily) is now deprecated and will log a warning.ofDynamicKeyhandles synchronization of predicated registry lists more robustly. - Added zh_tw translations
Changes
ValidatedIdentifiernow automatically appliesREQUIRES_WORLDto validation for dynamic registries, which require the world to be loaded. They will now not be available out of game.- Validation wrappers (lists, ValidatedCondition, etc.) will inherit their delegates flags automatically
- ConfigActions based on
ClickAction.RUN_COMMANDorClickAction.SUGGEST_COMMANDnow automatically applyREQUIRES_WORLD
Fixes
ValidatedIdentifierwithout validation no longer tries to "force" you to use the minecraft namespace in the text box- Enums revert to their proper default when automatically validated (plain field in the config)
- Config actions now respect permissions
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| fzzy_config-0.5.6+1.21+neoforge-sources.jar | Unknown | 401.65 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:74aEky0E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hYykXjDp:74aEky0E"
}


