hytale-plugin-config

Access and mutate configuration values at runtime from various classes by utilizing the Config<T> structure, which supports automatic persistence and runtime updates when you apply changes through the established withConfig pattern.

The best way to define Hytale plugin settings is creating a configuration class with a BuilderCodec<T> and a default constructor, using capitalized keys to ensure proper serialization and loading via the plugin lifecycle.

Yes, you need a default constructor to manage Hytale plugin config data. The configuration pattern requires a default constructor alongside capitalized keys and the withConfig field initializer to properly create and save the config file in the server mods folder.

Your Hytale plugin config file fails to generate if you do not use withConfig as a field initializer. Applying withConfig correctly ensures the config file is automatically created and persisted in the server mods folder during plugin setup.

Yes, you can access and mutate Hytale plugin configuration values from multiple classes at runtime. The Config<T> pattern supports runtime updates and automatic persistence when you call config.save() during the plugin lifecycle setup.