Audit and update /docs against the actual plugin source so it's current and complete:
docs/reference/{treasury,business,chestshop,realty}.md) — every command and permission node accurate vs plugin.yml / @Route / hasPermission checks.Per-plugin audit (treasury + treasury-api-plugin, business-rian, ChestShop-3, realty) comparing doc ⇄ source: authoritative command list (usage + permission), permission-node list (default + description), key config keys; report missing/outdated/obsolete entries; then fix the docs in the existing user-docs house style.
Follow-up to PAR-162.
Beyond docs — a live config bug surfaced by the audit
The
tax.balance.bracketsbracket-key issue isn't only a docs gap. The shippedconfig.ymlin bothtreasury/andbusiness-rian/uses decimal threshold keys (100000.00:…). Bukkit/SnakeYAML treats the.as a path separator, so those keys are parsed as nested sections (100000→00) instead of scalar keys — the loader (getKeys(false)→new BigDecimal(key)/getString(key)) then reads the rates as0. The map isn't empty (the integer parts parse), so it does not fall back to the correct hard-codedDEFAULT_BRACKETS.Net: balance tax brackets may not be applying as intended in prod (rates effectively zeroed), on both personal (Treasury) and firm (Business) balance tax — matching the earlier "why isn't the balance tax config working on SC?" report. The unit tests only feed integer keys, so the mangling is untested.
Recommended plugin-side fix (separate from the docs): change the shipped
config.ymlbracket keys to integers intreasury/andbusiness-rian/, and update any live serverconfig.yml. Docs now WARN operators to use integer keys (PR #20).