CyclopsMC / CyclopsCore / 37130598555

31%

master-1.21: 31%

push

github

Register config properties in the spec of their location

Properties were always defined on the COMMON spec builder, so CLIENT and
SERVER properties ended up in the common (local) config file and their
own specs stayed empty. Each property now goes into the builder of its
configLocation, and loading or reloading a config only syncs the
properties that belong to it, since values of a config that is not
loaded yet cannot be read.

This is a breaking change: values that were customized in the common
config file for CLIENT or SERVER properties are no longer read.

Also add a TODO to rename COMMON and SERVER to match NeoForge's
LOCAL and SYNCED config types in the next major version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RSz5r6eowhjNuANBjZE2v6

1317 of 4619 branches covered (28.51%)

Branch coverage included in aggregate %.

3941 of 12096 relevant lines covered (32.58%)

1.59 hits per line