MeowMC

Configuration

MeowMC's configuration lives in a parallel system: its own YAML files, its own config classes, its own version counter and its own removed-key registry. Nothing is added to Paper's paper-global.yml or paper-world.yml, so a Paper update cannot silently drop or conflict a MeowMC key.

In this section

  • Files and precedence — the four files, __world_defaults__, the absent-means-inherit rule, the INHERIT sentinel, _version, and how renamed and retired keys are handled.
  • Global keys — every key declared in meowmc-global.yml, with its default and its status.
  • World keys — every key declared in meowmc-world-defaults.yml (and overridable per world).
  • Plugin policies — meowmc-plugin-policies.yml: how an unmarked plugin is treated, per-plugin tier assignments, and enforcement.
  • Tick modes — exec.mode: the one value with any effect in this build (compat), and the regionized modes the key will select once they exist.
  • Web panel — the /meow panel commands, the loopback pairing service, the session store and the audit log — in the jar today — plus the browser UI that is design-only for now.

The rules carried on every key page

  • Every key carries a status — wired (code reads it today) or declared (the field exists, nothing reads it yet, so flipping it changes nothing on the server). Declared keys land phase by phase behind their own correctness gates; a key whose feature has not landed is not a tunable.
  • Optimisation keys are described as trade-offs, never as wins. A key that is default-off is off because a gate has not been passed — a byte-identity proof, a client-side check, a benchmark.
  • No default is a promise about behaviour until the code behind it has passed its gate.

Java fields are camelCase, YAML keys are kebab-case

The mapping is automatic and total: regionThreads in the class is region-threads in the file, with no per-key annotations anywhere. There is exactly one forced exception — exec.threading.default, because default is a Java reserved word and cannot be a field name. The class field's comment is the authority over these pages.