PROTECT WHAT YOU BUILD

Minecraft Base Protection Guide for Survival Servers

Cube Survival combines protected shared areas, auditable block history, backups, and community rules. Self-service player land claims are not currently enabled, so this guide states exactly what the server protects and what players should do.

What is protected automatically?

WorldGuard and CubeSurvivalSpawnGuard protect shared spawn and its critical interactions. Prism records relevant block and inventory activity so authorized staff can investigate reports and perform a targeted rollback. Automated world backups provide disaster recovery, but they are not an instant per-player undo button.

What is not currently enabled?

Cube Survival does not currently provide self-service personal land claims. A private base does not gain an automatic plugin boundary simply because it was built. Griefing and theft remain prohibited by the community rules, and staff can use audit evidence when a report is made.

A practical first-base strategy

1. Leave the crowded arrival area.Choose a responsible location with clear distance from existing builds, roads, and community infrastructure.
2. Start compactly.Keep important blocks and storage easy to inspect while learning the area.
3. Use your Ender Chest.Keep irreplaceable or highest-value items in player-bound storage.
4. Record shared ownership.Agree in chat on who owns a collaborative build and who may change it.
5. Report incidents promptly.Provide coordinates, an approximate time, and a concise description so staff can query Prism efficiently.

Build without creating disputes

• Do not build onto another player's project without permission.
• Leave enough room for existing farms, roads, portals, and redstone.
• Do not share account codes or temporary website-link commands.
• Never give valuables to a stranger on the promise that staff will reverse a voluntary trade.
• For a town, document common areas and private storage before construction begins.

How a grief report works

Capture the coordinates and avoid changing the affected area more than necessary. Contact staff with the location, estimated incident window, affected blocks or containers, and involved player names if known. Staff review Prism history and the surrounding context; rollback is evidence-based and scoped to avoid overwriting legitimate changes.

Why the old claim URL remains

This page keeps its established URL so saved links and search results do not break, but the content reflects the current running server. If an Owner later enables a player-claim system, the guide and dashboard catalog should be updated in the same release.