Safety and Protection

Quick start

1. Use the shared spawn as the safe meeting and starting area.
2. Leave spawn before claiming a permanent base.
3. Protect your build with /lands claim and inspect it with /lands view.
4. Trust only people you want sharing access.
5. Report damage with the place, approximate time, and what changed.

Spawn sanctuary

The shared spawn region is configured as a full-height 501×501-block sanctuary. Inside it:

• Player-versus-player combat is denied.
• Mob spawning is denied.
• New Lands claims are denied.

You may explore and meet there, but choose a base outside the sanctuary. If /lands claim is rejected near spawn, travel farther out before trying again.

Personal build protection

Each regular player can protect one side-connected four-chunk base in the Overworld. Claim protection is tied to the chunk borders, not to the visible shape of a house or fence.

Use /lands view before building near an edge. Use /lands trust PlayerName only when that person should share normal access, and /lands untrust PlayerName when they should no longer have it.

The detailed behavior for containers, doors, redstone, animals, and other Land role flags is still being tested. Until then, treat trust as meaningful access rather than assuming it grants only block placement.

Regular-player permission boundary

Regular players receive the narrow claim and travel commands documented in Player Commands. They do not receive protection bypasses, broad teleports, world-editing tools, rollback commands, or other administrator access.

If a protected block appears editable when it should not be, stop interacting with it and report the exact location.

Report damage or a protection problem

Send the server owner:

• The place or coordinates.
• The approximate time it happened.
• What blocks, containers, or items changed.
• The exact command or Minecraft message involved, if any.

Do not attempt an administrator command or repeatedly test someone else's protection. The owner can investigate server records and backups without granting those tools to regular players.

Privacy and connection details

• Keep the server address and ports private.
• Do not post screenshots that reveal connection details.
• Use exact in-game names only when a command requires them.
• The website exposes only sanitized server status, never hosting credentials, IP addresses, UUIDs, or private account data.