Configuring the mod
Every parameter described in this wiki, tables included, is accessible and modifiable in-game in three equivalent ways, without a server restart.
Command
/lethalconfig (permission level
2,
operator required) takes no arguments: typed in game, it opens the configuration interface directly. From a
server console, where no interface can open, it falls back to a full text listing of every option. Editing and
resetting happen inside the interface, one option at a time, there is no subcommand to remember.
In-game GUI
Typing /lethalconfig with no argument opens a configuration screen:
search bar, categories in the sidebar, options as checkboxes or numeric fields. Every change
is archived immediately (no Save/Cancel button).
JSON file
The entire configuration lives in config/oas/lethalbreed.json. The
file is rewritten in full on every server startup: an option added by a mod update therefore appears
automatically with its default value, without ever corrupting an existing
file.
Recorded mechanism. Any non-final public static field of a
configuration class is exposed automatically across all three interfaces (command, GUI, JSON) via
reflection: adding a parameter to the code requires no manual wiring anywhere else.
Nothing internal is exposed. The development tooling (test benches, instrumentation, performance probes) is compiled separately and absent from the shipped jar. Every option you see in the interface or in the JSON file is a real operational setting, meant to be tuned. None is an inert leftover.