Let islands choose who may claim chunks

[tastybento]

Stacked on #17. Based on feat/claim-confirmation so the diff shows only the rank work. GitHub will retarget this to develop once #17 merges.

Claiming was hard-coded to the island owner, and a teammate who hit the border got nothing back at all — no message, no sound, ChunkClaimListener simply returned. That reads as a broken mechanic rather than as a permission, and it is the concrete complaint behind #6.

Who may spend the island's level credit is now the CHUNKBLOCK_CLAIM_CHUNKS protection flag. An island can open expansion to sub-owners, members, trusted or coop through the ordinary island settings GUI, and servers can move the default in default-island-flags. It defaults to owner rank, so nothing changes until an island says otherwise.

That covers the first three options Floris asked for — owner only, sub-owner or higher, configurable island rank — using machinery BentoBox already has rather than a bespoke setting.

Feedback

• A teammate below the rank is now told why: "Your rank cannot claim chunks for this island!" with the bass note, throttled through the existing 2s cooldown.
• Visitors and passers-by still get nothing. They see the ordinary locked-chunk message from the guard listener; another island's credit is none of their business. There is a test pinning this.
• ChunkGuardListener.sendBumpMessage carried the same hard-coded owner check, so a teammate walking into the border never saw the claim hint even on an island that had opened claiming to them. It now asks the same flag.

Tests

627 green. Five new: below-rank denied with feedback, a non-owner member allowed once the island opens it, a visitor told nothing, the bump inviting an allowed player, and the bump only saying "locked" otherwise.

Both listener test classes move from mock(ChunkBlock.class) to spy(new ChunkBlock()) — a mock leaves the final flag fields null, and BossBarListenerTest already establishes the spy pattern for exactly this reason. That is the bulk of the test diff.

Deliberately not included

The team proposal and team vote options from #6. They are a workflow engine for a one-click action, and the confirmation step in #17 already solves the underlying "don't waste the island's levels by accident" worry that motivated them. Easy to add later if the rank flag proves too blunt.

So #6 should stay open after this merges, or be closed with a note about the voting options being declined — your call.

Unrelated observation

MAGIC_BLOCK at ChunkBlock.java:128 uses an unprefixed flag ID that AOneBlock almost certainly also registers. Duplicate flag IDs get rejected by FlagsManager, which is why CHUNKBLOCK_BOSSBAR/ACTIONBAR/START_SAFETY were renamed — this one looks like it was missed. Not touched here (renaming resets the flag on live islands), but it likely wants its own issue.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Taa2snoHkvtcZ6e5rAHDQS

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud