ChunkClaims

CHUNK CLAIMS
Fabric Mod for Minecraft Java 1.21.11

OVERVIEW

Chunk Claims lets players claim individual chunks and control who may interact
with them. Claims persist with the world, work in every dimension, and do not
prevent players from walking through claimed land.

Each player may own a configurable number of claimed chunks in total across all
dimensions. The default limit is 15.

The mod includes three trust levels, territory entry titles, operator-safe claim
removal, optional Xaero map integration, and optional Waystones compatibility.

REQUIREMENTS

- Minecraft Java 1.21.11
- Fabric Loader 0.19.3 or newer
- Fabric API 0.141.4+1.21.11
- Java 21 or newer

For Xaero integration:

- Xaero's Minimap 26.1.4
- Xaero's World Map 1.41.2

For optional Waystones compatibility:

- Waystones 21.11.x for Minecraft 1.21.11
- Balm, as required by Waystones
- Waystones and Balm installed on both the server and participating clients

Cloth Config is not required.

INSTALLATION

Install Chunk Claims and Fabric API on the server. Install the same Chunk Claims
jar and Fabric API on clients that need Xaero map controls and claim highlights.
Xaero's Minimap and World Map are client-side optional dependencies and are not
required on a dedicated server.

The same Chunk Claims jar works on dedicated servers and clients. Singleplayer is
also supported through Minecraft's integrated server.

COMMANDS

/claims add
Claims the chunk in which the player is standing. A chunk cannot be claimed when
another player already owns it.

/claims add (x1, z1) (x2, z2) <username|server>
Operator-only. Claims the inclusive rectangular area between two opposing
diagonal corners for the named player or for the server. The numbers are chunk
coordinates in the operator's current dimension. A maximum of 65,536 chunks may
be processed in one operation.

If a selected chunk belongs to a different owner, the entire area claim is
cancelled without changing any chunks. Chunks already owned by the selected
target are left unchanged. The target player must have joined the server before.
The operation is also cancelled if its new chunks would put a player above the
configured ownership limit. Server-owned claims are exempt from the player limit.

/claims remove
Removes the claim in which the player is standing when they own it.

/claims remove confirm
Confirms an operator's attempt to remove another player's claim. Confirmation
must be completed within 30 seconds.

/claims trust <username> trustlevel <1|2|3>
Sets the named player's trust level for all claims owned by the command sender.
The target must have joined the server previously.

/claims untrust <username>
Removes the named player's trust from all claims owned by the command sender.

TRUST LEVELS

Universal access - Untrusted players and trust levels 1, 2, and 3

Every player may attack hostile mobs inside a claim and may activate, open, and
travel through blocks from the optional Waystones mod. These permissions do not
increase the player's trust level. Untrusted players still cannot attack passive
animals, villagers, pets, or other protected entities, and cannot break a
Waystone, place blocks against it, or use unrelated protected blocks.

Level 1 - View-only containers

In addition to the universal hostile-mob and Waystones permissions, level 1 may
only open supported item containers and view their contents. Level 1 cannot move
items, open doors or gates, use buttons or levers, trigger protected pressure
plates or tripwires, build, break blocks, or interact with protected entities.

Level 2 - Containers and entrances

Includes the universal hostile-mob and Waystones permissions. Level 2 may view
and modify supported containers, open and close doors, fence gates, and trapdoors,
and use buttons, levers, pressure plates, and tripwires. It does not grant general
building, breaking, or other entity access.

Level 3 - Full access

Includes the universal hostile-mob and Waystones permissions. Level 3 may build,
break blocks, use containers and protected blocks, and interact with or attack
other protected entities.

The claim owner always has full access. Trust is global per owner, so a player's
level applies to every claim owned by that owner in every dimension.
Server operators have full access to claims owned by the server.

The configured limit applies to ordinary claims and to areas assigned by an
operator. Existing claims are not automatically removed when loading an older
world in which a player already exceeds the limit, but no additional chunks may
be claimed for that player until their total is below it.

SERVER CONFIGURATION

The server creates config/chunk_claims.properties on first startup. Configure the
per-player limit with:

max-player-claims=15

Valid values are integers from 1 through 1,000,000. The value counts all claims a
player owns across every dimension. Restart the dedicated or integrated server
after changing it. Missing or invalid values use the default limit of 15 and are
reported in the server log.

CLAIM PROTECTION

Players without sufficient trust cannot directly break or place blocks, use
protected blocks or containers, or interact with or attack protected entities.
All players may freely walk through claimed chunks.

The universal hostile-mob and Waystones exceptions listed under TRUST LEVELS
apply in every claim.

Only the owner may normally unclaim a chunk. Operators may remove another
player's claim only after receiving this warning and confirming the action:

"This chunk is owned by <username>. Are you sure you want to unclaim their chunk?"

XAERO COMPATIBILITY

To use Xaero integration, install Chunk Claims, Fabric API, Xaero's Minimap, and
Xaero's World Map on the client. The server must have Chunk Claims and Fabric API.

For one chunk:

1. Open Xaero's fullscreen World Map.
2. Select exactly one chunk with Xaero's map selection control.
3. Open the right-click options and choose the claim or unclaim action.

For an operator multi-selection:

1. Select a rectangular area containing more than one chunk.
2. Open the selection's right-click options.
3. Choose to claim the area for yourself, for the server, or for another player.
   The other-player option opens a username screen and preserves the dimension
   currently displayed in Xaero.
4. To remove claims, choose the bulk unclaim action. Review the affected claim
   count and owners, then explicitly confirm the removal.

Bulk claiming and unclaiming are operator-only and limited to 65,536 chunks per
operation. The server rechecks the operator, dimension, size, ownership, and
confirmation. Claims changed after a removal warning are not removed by that
pending confirmation.

The player's own claims are highlighted green. Claims belonging to other players
or the server are highlighted red. Highlights refresh after server synchronization.

TERRITORY TITLES

Entering claimed land displays:

Entering <username>'s Claim

Entering unclaimed land displays:

Entering Unclaimed Territory

CURRENT PROTECTION SCOPE

This version protects direct player block actions, supported containers, door and
redstone access controls, and entity interactions. Environmental and automated
changes such as explosions, fire, fluid flow, pistons, hoppers, and mob griefing
are not currently claim-filtered. Hostile-mob attacks and Waystones use are
intentional exceptions to claim protection.