> For the complete documentation index, see [llms.txt](https://docs.mcgalaxy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mcgalaxy.co/server/protections.md).

# Protections

We focus on non-invasive methods of anti-grief measures. Check them out below!

## 🛡️ Protections

We use **non-invasive protection systems** designed to keep your builds and belongings safe without restricting the freedom of Survival.

Rather than requiring players to claim chunks or surround their builds with invisible borders, we automatically protect many important blocks and entities as you place them.

***

### Land & Building Protection

Our server **does not use a traditional land-claim system**.

We intentionally avoid dividing the Survival world into restrictive plots, chunks, or claim borders. Players are free to explore, settle, expand, and build naturally throughout the world without managing claim blocks or constantly expanding a protected region.

Instead, protection is focused on the things that matter most: **your containers, interactive blocks, decorative entities, and other player-owned objects.**

Many of these are automatically made private when you place them.

#### Where Can I Build?

You are generally free to build anywhere that is not already being actively used by another player.

When choosing somewhere to settle, use common sense and respect the space of other players.

* Avoid building directly beside, inside, or on top of another player's settlement or project.
* If an area clearly appears active or developed, give that player reasonable room to continue expanding.
* Roads, farms, decorations, infrastructure, storage areas, and partially completed builds may all indicate that an area is actively being used.
* If you're unsure whether an area has been abandoned or is available, contact the player or ask a staff member to check.
* If there are no reasonable signs that another player is using an area, you're generally free to build there.

> **Not sure?**
>
> Ask a staff member before building. We're happy to help determine whether an area is actively being used.

#### What If There Is a Dispute?

The absence of land claims does **not** mean that another player's builds or property are free to modify.

Staff can investigate disputes involving:

* Griefing
* Theft
* Building overlap
* Destruction or modification of another player's work
* Intentionally interfering with another player's settlement

When necessary, staff may use **server logs and rollback tools** to determine what happened and restore affected builds.

Intentionally griefing, stealing from, modifying, or deliberately crowding another player's established property may result in staff action.

Our goal is simple: **provide as much building freedom as possible without forcing every player to manage claims, borders, or complicated land-protection systems.**

***

## Automated Protection

Many blocks and entities on mcGalaxy are **automatically made private when placed or spawned by a player**.

The player who places the protected object becomes its owner and can manage who else is allowed to access it using the `/protect` commands documented below.

### Containers & Blocks

The following blocks are automatically protected when placed.

| Protected         | Protected            |
| ----------------- | -------------------- |
| Decorated Pots    | Furnaces             |
| Crafters          | Blast Furnaces       |
| Shulker Boxes     | Smokers              |
| Anvils            | Dispensers           |
| Cauldrons         | Droppers             |
| Ender Chests      | Barrels              |
| Standing Signs    | Brewing Stands       |
| Wall Signs        | Composters           |
| All Hanging Signs | Beacons              |
| All Doors         | Jukeboxes            |
| All Trapdoors     | Noteblocks           |
| Fence Gates       | Lecterns             |
| Banners           | Chiseled Bookshelves |
| Chests            | Hoppers              |
| Trapped Chests    |                      |

These protections can be modified by the owner to allow other players, groups, or supported access sources to use them.

***

### Entities

Many player-spawned or player-placed entities are also automatically protected.

| Protected           | Protected            |
| ------------------- | -------------------- |
| Armor Stands        | Dark Oak Chest Boats |
| Item Frames         | Jungle Chest Boats   |
| Glowing Item Frames | Mangrove Chest Boats |
| Paintings           | Oak Chest Boats      |
| Leash Knots         | Pale Oak Chest Boats |
| Acacia Chest Boats  | Spruce Chest Boats   |
| Bamboo Chest Rafts  | Chest Minecarts      |
| Birch Chest Boats   | Furnace Minecarts    |
| Cherry Chest Boats  | Hopper Minecarts     |

Like protected blocks, these entities can be managed by their owner using the protection system.

***

## Protection Commands

The `/protect` command allows you to inspect, lock, unlock, share, transfer, and otherwise manage protected blocks and entities.

### `/protect info`

View information about a protected container or entity.

Use this when you want to check the protection or ownership information for an object.

***

### `/protect lock`

Lock an unprotected container or entity.

***

### `/protect unlock`

Unlock a protected container or entity.

***

### `/protect modify [add|remove] [player|group|password] <sources...>`

Add or remove access sources from a protection.

This is an **advanced command** that allows you to manage players, groups, or passwords associated with a protection.

See **Access Levels** and **Sources** below for additional information.

***

### `/protect edit [add|remove] <player_name>`

Add or remove a player's access to a protection.

This provides a simpler way to directly share a protection with another player.

***

### `/protect trust [add|remove] [player|group|password]`

Manage your trusted access list.

Depending on how the command is used, it can prompt, list, or confirm changes to trusted protection access.

***

### `/protect password <password>`

Enter a password for a protection that uses a password-based access source.

***

### `/protect group (create|delete|add|remove|list) [player_names...]`

Create and manage groups of players that can be used with protections.

This command can be used to:

* Create a group
* Delete a group
* Add players
* Remove players
* List group information

Groups are useful when several players regularly need access to the same protections.

See `/protect modify` for information about applying groups to protections.

***

### `/protect transfer <player_name>`

Transfer ownership of a protection you own to another player.

> **Be careful when transferring ownership.**
>
> Once transferred, the other player becomes the owner of that protection.

***

## Command Options

Some advanced protection commands use **Access** and **Source** options.

These determine **what someone is allowed to do** and **who or what receives that access**.

***

### Access Levels

Available access options:

`normal` · `trusted` · `admin`

#### Normal

Basic interaction permissions.

**Interact**\
Allows interaction with a protection.

**Open**\
Allows opening a protected container.

***

#### Trusted

Additional usage permissions.

**Redstone**\
Allows redstone interaction with a protection.

**Deposit**\
Allows items to be placed inside a protected container.

**Withdraw**\
Allows items to be removed from a protected container.

**Mount**\
Allows the player to ride a protected entity.

***

#### Admin

Protection-management permissions.

**Edit**\
Allows access to use the modify command on the protection.

> **Only give elevated protection access to players you trust.**

***

## Sources

Available source options:

`player` · `group` · `password`

Sources determine **who or what is being granted access to a protection**.

#### Player

A specific Minecraft username.

Use this when you want to grant protection access directly to an individual player.

***

#### Group

A group that you have created or have Admin access to.

Groups are useful for shared bases, towns, teams, or other situations where several players should have access to the same protections.

***

#### Password

A defined password used to access supported containers or group features.

Passwords allow access to be granted without assigning it directly to a specific player.

***

### Need Help?

If you're unsure how to configure a protection, share something with another player, or determine whether an area is available to build in, **ask a staff member**.

We're happy to help before something becomes a problem.
