Add ItemsAdder and Oraxen custom block limits

[tastybento]

Fixes #176.

Config

No new section — custom ids go straight into the existing blocklimits machinery (including -nether/-end and worlds: overrides):

blocklimits:
  HOPPER: 10
  "iafestivities:christmas/christmas_tree/green_orb": 5   # ItemsAdder namespaced id
  "oraxen:caveblock": 10                                   # Oraxen id, oraxen: prefix

The parser already produced NamespacedKeys for colon keys; registerLimit now accepts non-minecraft namespaces instead of rejecting them, and the per-env data model stores them natively (no migration).

How enforcement works

Two thin listeners, registered only when the respective plugin is installed (no hard dependency; the API jars are provided at the same versions BentoBox compiles against):

• ItemsAdderListener — CustomBlockPlaceEvent / CustomBlockBreakEvent
• OraxenListener — note-block and string-block place/break events

Both feed processKey, a public extraction of the existing count/limit core, so island lookup, per-environment limits, offsets, save batching, and the limits GUI (paper icon + prettified name) all work unchanged. Listening to the plugins' own events is what fixes the 2023 blocker on this ticket — the old prototype raced Bukkit's block events and the block placed anyway; the custom events can't desync that way.

The recount chunk scan can't see custom blocks (they're physically note blocks etc.), so RecountCalculator now carries non-minecraft counts across the reset instead of zeroing them. Documented in the config comments.

Deliberate v1 scope

• Oraxen furniture (entity-based) is not limited — note-block/string-block mechanics only.
• Permission-based limits don't match custom ids (perm segments are dot-separated; custom ids contain colons/slashes). Offsets via the admin command work.
• Per the ticket discussion: API access is BentoBox-hook style (no plugin API calls beyond their events); Nexo support would start with a BentoBox hook.

Testing

JUnit covers processKey (limit hit, count, decrement for a custom key), config parsing of custom keys, and id→key mapping. The listeners themselves need in-game verification with the real plugins — @Olthoo offered to test back in 2023 and users were still asking in 2025:

1. Install ItemsAdder, add a custom block id with limit 2 to blocklimits, restart.
2. Place 2 of the block → 3rd is blocked with the hit-limit message and the block does not appear (this was the 2023 failure mode).
3. Break one → placement works again. /is limits shows the custom entry (paper icon).
4. /is limits recount → the custom count is unchanged afterwards.
5. Repeat with an Oraxen note-block id under "oraxen:<id>".
6. Explosion/piston removal of a custom block → verify the plugin fires its break event and the count drops (if a gap shows up here, recount preserves rather than fixes custom counts — report it).

🤖 Generated with Claude Code

https://claude.ai/code/session_015dbJyrv2uxHfTmiWkqGUJB

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
32.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud