What the library does
Fzzy Config is a configuration library created by fzzyhmstrs for Java mod developers. It writes data to TOML files automatically. You can build your setups using basic Java or Kotlin objects, or you can create granular options patterned after default Minecraft settings. The library also includes its own networking API for cross-loader communication.
It fits developers who want clean setup files without writing manual menu screens.
Screen generation and accessibility
The library builds user interfaces directly from the layout of your config files. You do not need to register screens or assemble individual display elements by hand. Here's the thing, it ties into ModMenu and Catalogue on its own.
Accessibility is built into these screens. Every interface supports keyboard navigation and narration directly out of the box. A visually impaired member of the modding community tested and vetted the screen features during development. You can also attach action buttons to these menus to run specific commands or link directly to an external wiki.
Synchronization and validation
Fzzy Config handles network synchronization between connected clients and dedicated servers. Players can send live configuration updates from their client straight to a server. You can also share your local settings with other players.
Value checking goes beyond basic data types. The library validates input values, corrects invalid choices, and provides automatic suggestions for resource identifiers and tags. If you're migrating from an older configuration format, the library lets you scrape previous config files. It also handles versioned file updates through a single method implementation.
Compatibility and license rules
Fzzy Config requires installation on both the client side and the server side. It supports the Fabric, Forge, and Neoforge mod loaders. Supported game releases are Minecraft versions 26.3, 1.20.1, 26.2, 26.1, 1.21.11, 1.21.10, 1.21.9, 1.21.8, 1.21.7, and 1.21.6.
The mod is released under the TDL-M license. Under the terms of this license, you cannot bundle the library using jar-in-jar packaging or include mechanisms in your build files.
