Kaledelights Compat

1.3.2 — Config Fixes & a Readable Config Format

Fixed

• Fixed: unify.json was never actually read. The generated _checklist was a JSON array while the field reading it was typed as a string, so Gson threw Expected a string but was BEGIN_ARRAY and the mod silently fell back to in-memory defaults — every setting in that file was ignored (preset rule groups, blacklist, custom mappings, block mappings, AllowItemDeletion). The field now accepts any shape, and a parse failure is logged as "all settings in this file will not take effect", so it can never fail silently again.

• Fixed: two of the three player "remove" switches did nothing. Blacklist and Rule Groups removed their rules too early — the removals were wiped when the replacement cache was rebuilt right afterwards. (Same timing issue that was fixed for AllowItemDeletion in 1.3.1; these two were missed there.) All three switches now register their removals and run them after the reload finishes, with a read-back check and a log line reporting how many rules were really removed.

• Fixed: only the last rule of a group was removed when that group contained several rules (the registration key collided).

Changed

• unify.json is now unify.omniconf — a sectioned, comment-friendly format: # comments, "Rule Groups" { B:deleteItems=true }, and S:Items < source_id to target_id > lists. Same style as the enigmaticaddons-common.omniconf already used in many packs.
  • The 100-line _checklist block is gone; the file shrank from 7.7 KB to 4.7 KB
  • An existing unify.json is migrated automatically on first launch and kept as unify.json.migrated.bak
  • A line the parser cannot read now only affects that line — a single bad entry can no longer invalidate the whole config
• Config keys are English-only. Chinese keys from 1.3.0 and older (森罗砧板, 盐, 允许删除物品, …) are no longer recognised. Old files do not cause errors, but every switch falls back to its default (all enabled, including AllowItemDeletion). Delete config/KaledelightsCompat/ so the mod regenerates the English configs, then re-apply your settings.

Added

• rules.txt — auto-generated next to unify.omniconf on every reload. It lists every built-in unification rule (source → target), whether each group is currently on or off, and the four ways to customise, so you can add your own unification or rescue a single item that would otherwise be removed.