Disclosure: This is still a beta version, we will be releasing updates frecuently with new content and region fixes.

Area Protection

Area Protection lets you mark regions of your world and decide, one by one, what players can do inside them, yes, just like WorldGuard!

You pick the corners with a wand, name the region, and then open an in-game editor to say which blocks can be broken or placed, which items work, which mobs can be hit, and a long list of switches like PvP, fire, explosions or mob spawning.

It has to be installed on the server and on every client.

Selecting an area

Run /ap wand for the Area Wand. A golden axe works too, but only for admins.

Change the shape with /ap shape box|cylinder|polygon. While you hold the wand your selection is drawn in the world, and /ap show also outlines existing zones.

• Shift + left click clears the selection.
• Shift + right click asks for a name and creates the zone. It works while aiming at the sky too.

Zones made from a selection cover the full height of the world, so two points on the ground still protect everything above and below. If you want the exact heights you marked, set fullHeightZones to false in the config.

What a zone controls

Five lists, each with a mode (allow all, deny all, whitelist or blacklist) and a group they apply to (non-members, members or everyone):

• Break
• Place
• Interact (doors, chests, buttons and so on)
• Items (buckets, ender pearls, tools)
• Entities (attacking or using them)

Entries can be a single block, item or entity, a tag like #minecraft:logs, or modid:* for everything from a mod, so modded content is covered without extra work. The picker in the editor has a search box and shows icons.

Flags can be turned on or off per zone: PvP, damage from mobs, explosions, fire spread, fluid flow, hostile and passive spawns, farmland trampling, crop growth, leaf decay, snow and ice melting, pistons, hoppers, ender pearls, chorus fruit, entering, leaving, elytra, vehicles, picking up and dropping items, and hunger. The ones that depend on a player can be limited to non-members, members or everyone.

Something you SHOULD know:

• Overlapping zones are resolved by priority first, then by size, so the smaller one wins a tie.
• Each rule and flag can have its own "denied" message, and zones can show a message when you enter or leave.
• Zones can be box, cylinder, polygon, or global (a whole dimension).
• Presets (spawn, shop, plot), copying settings between zones, and export and import to share setups.
• Zones are per dimension.

The editor

Press I, or use /ap gui. The editor has tabs for general settings, flags, and one for each rule list. Only admins can open it, and for everyone else the key is hidden from the controls screen.

Owners and members

Each zone can have owners and members. Owners can change the rules, flags and members of their own zone without being operators. Members count as the members group for rules that apply to non-members only.

Player plots

Off by default. Turn on plotsEnabled in the config and players can claim their own box with /plot. You set the limits: plots per player, maximum volume and maximum width. Plots can never overlap another zone.

Commands

/ap is short for /areaprotection.

Permissions

Admin means operator level 2 by default. You can change the level with adminPermissionLevel in the config.

If you install fabric-permissions-api (optional), the node areaprotection.admin decides who is an admin, so you can hand it out through LuckPerms or a similar mod.

Operators do not skip the rules. Zones apply to everyone, and an admin who wants to build in a protected area runs /ap bypass first. Fake players (automation mods) are checked like normal players unless you turn on fakePlayersBypass.

Configuration

config/areaprotection.json holds the global settings: admin level, fake player bypass, enter and leave messages, full height zones, the plot options and the default denied messages. Zones live in config/areaprotection/, one file each.

Not covered YET

Redstone power, command filtering and block drop control have no stable hook across versions, so they are not part of the mod. Fire that is started by something other than fire spread can still appear inside a protected zone.

Reporting problems

Open an issue on GitHub or get on my Discord, make sure to include your Minecraft version, the mod version and logs/latest.log.