feat: Configurable radius for OBSIDIAN_SCOOPING flag

[Copilot]

The OBSIDIAN_SCOOPING flag had a hardcoded 2-block radius for the nearby-obsidian check, with no way to tune it per server. This adds a BentoBox-wide config setting for that radius and surfaces it in player-facing messages.

Changes

Settings.java

• New island.obsidian-scooping-radius config option (int, default 2, valid range 0–15)
• Setter clamps values to [0, 15]
• Setting to 0 disables the nearby check entirely — any lone obsidian can be scooped

ObsidianScoopingListener.java

• Reads radius from Settings instead of the hardcoded 2
• Skips the nearby-obsidian check when radius == 0
• Passes [radius] as a text variable to the obsidian-nearby message

# config.yml
island:
  obsidian-scooping-radius: 2  # 0 disables the restriction

Locales

• en-US: obsidian-nearby reworded to "…within a [radius]-block radius…"; description updated to say "the configured radius" instead of "a 2-block radius"
• All 22 other locale files: ([radius]) appended to obsidian-nearby so the radius value is always visible to players regardless of language

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Configurable radius for OBSIDIAN_SCOOPING flag</issue_title>
<issue_description>### Description

Is your feature request related to a problem?

A discussion on Discord with an admin raised some misconceptions of the OBSIDIAN_SCOOPING flag, namely a vague explanation of what the flag does and an insufficient feedback to the player that does not let him know why he could not scoop up the obsidian block. Those have already been fixed in this commit (f04a4fb).

It appeared, though, that there was some lack of understanding about how the OBSIDIAN_SCOOPING flag worked overall. Most notably, the fact that there must not be any other obsidian block within a 2-block radius of where the block is.

Describe the solution you'd like us to implement.

To further improve the solution to that issue, I suggest that we add a configurable radius for the OBSIDIAN_SCOOPING flag. It will bring some more customization capabilities, even allowing the admin to get rid of that restriction.

Following are the specifications of this feature:

• Config option allowing to set the radius within a (0..15) range.
• [radius] text-variable in the protection.flags.OBSIDIAN_SCOOPING.obsidian-nearby message.
• Edit the OBSIDIAN_SCOOPING flag description to not mention the 2-block radius rather the config-defined radius.

Questions are:

• Should it be a BentoBox setting or a gamemode one?

Describe alternatives you've considered.

None.

Additional context

None.</issue_description>

<agent_instructions>make the radisu a setting in BentoBox config.yml and edit the text for the flag to include the placeholder across all locales.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@tastybento I'd prefer BentoBox so it's consistent across game modes. If the idea is to reduce confusion then it should be consistent. But also, if that's the goal, then it'd be better if there's just one standard across all servers. Does this really have to be configurable? Won't that just cause more questions? "On XYZ server it works, but here is doesn't, why admin?"

• Fixes Configurable radius for OBSIDIAN_SCOOPING flag #1184

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud