Documentation

Troubleshooting

The problems that come up most, and what causes them.

Most reports come down to a handful of causes. Work through these before opening an issue.

The config does not appear in ModMenu

ModMenu asks for config screens during mod initialisation. If your config is not registered by then, load order can mean it has not been created yet when ModMenu asks. Registering earlier, from a static or object initialiser rather than an entrypoint method, fixes it.

The game will not start

Check three things in order: that the Fzzy Config file matches your exact Minecraft version, that it matches your loader, and that the Kotlin language loader it needs is installed. Fzzy Config is written in Kotlin, so Fabric and Quilt need Fabric Language Kotlin, and Forge and NeoForge need Kotlin for Forge or KotlinLangForge depending on version. The crash log names the missing piece.

Settings reset after a mod update

That is what @Version and update() exist for. Without a version stamp, a structural change can leave the old file unreadable and the defaults get written back. Bump the version and migrate the old values in update().

A setting will not sync

Check whether the field is marked @NonSync, whether the config was registered as RegisterType.CLIENT, and whether the player has the permission level the setting requires. All three produce the same symptom.

A hand-edited value is being changed

That is validation doing its job. A value outside the bounds you declared is corrected rather than accepted, both on load and in the screen. If the correction is wrong, the bounds are wrong.

Still stuck

The author takes bug reports on GitHub and questions in their Discord. From the README: "Stuck? Drop a line in my Discord server and I will help you out."

Need more depth on this topic? The wiki has a longer article. Read it on moddedmc.wiki.