Area Ward

Quickstart

Area Ward is a server-side protection mod. There are no items to craft — everything is managed through commands.

1. Make sure you are a server operator (op).
2. Stand near the area you want to protect and note two opposite corner coordinates.
3. Run: /areaward create myregion <x1 y1 z1> <x2 y2 z2>
4. The ward is active immediately. Non-op players can no longer break, place, or right-click blocks inside it.
5. Use /areaward list to see all active wards, or /areaward here to check if your current position is protected.

Overview

Area Ward lets server operators define named cuboid regions — called wards — where non-operator players cannot modify blocks. Wards persist through server restarts and cover breaking, placing, and right-click interactions (such as opening blocks or placing items against a surface). Operators bypass all protections automatically.

What It Adds

• Wards — named, axis-aligned box regions that block non-op players from editing blocks inside them.
• A full command suite under /areaward for creating, removing, and inspecting wards.
• In-game notifications sent to any player who attempts to modify a protected area.

How To Use

For Server Operators

Positions follow standard Minecraft block coordinate syntax, including relative (~) coordinates. The two corners (<from> and <to>) can be any two opposite corners of the box — the mod automatically figures out the minimum and maximum bounds.

Ward names are case-insensitive and trimmed to lowercase when stored. Each name must be unique.

For Regular Players

Non-op players cannot create or remove wards, but can use /areaward list, /areaward here, and /areaward check <pos> to inspect which areas are protected. If a player tries to break or place a block — or right-click — inside a ward, they receive a chat notification naming the ward that blocked the action.

Abilities And Mechanics

• Block breaking protection — any attempt to break a block inside a ward is cancelled for non-op players.
• Block placing protection — right-click interactions that would place a block on or inside a ward boundary are blocked.
• Right-click editing protection — general block interactions (e.g., opening chests, using buttons, placing items against blocks) are also blocked if either the clicked block or the placement target falls within a ward.
• Operator bypass — players with server operator status ignore all ward restrictions and can edit freely.
• Dimension-aware — each ward is tied to the dimension it was created in; a ward in the Overworld does not protect the same coordinates in the Nether or the End.
• Persistent storage — wards are saved to the world's data storage and survive server restarts.

Progression And Strategy

• Define wards around spawn towns, admin builds, or event arenas to keep them intact during open-world play.
• Use /areaward here while exploring your build to quickly confirm coverage before opening the server to players.
• Use /areaward check <pos> to verify specific block coordinates are protected — useful for double-checking borders.
• Ward names are a single word; choose descriptive names (e.g., spawn, market, arena_north) to keep your /areaward list readable.
• There is no limit on the number of wards, so you can carve out as many protected zones as needed across all dimensions.