--- title: "WorldGuard and WorldEdit: The Basics That Protect a Server | ZCS" description: "Region protection stops the single most common cause of a server's first real disaster: someone griefing spawn before protection existed." url: "https://www.zcraftstudios.com/blog/worldguard-worldedit-basics-setup" updated: "2026-10-20T07:15:13.005688+00:00" source: "ZCraft Studios" --- > Site index for AI agents: https://www.zcraftstudios.com/llms.txt (full reference: https://www.zcraftstudios.com/llms-full.txt). Every page is available as Markdown by adding `.md` to its URL or sending `Accept: text/markdown`. 1. [Home](https://www.zcraftstudios.com/) 2. [Blog](https://www.zcraftstudios.com/blog) 3. WorldGuard and WorldEdit: The Basics That Protect a Server [ All posts](https://www.zcraftstudios.com/blog) # WorldGuard and WorldEdit: The Basics That Protect a Server ZCraft StudiosOct 3, 2026Updated Oct 20, 2026 Region protection stops the single most common cause of a server's first real disaster: someone griefing spawn before protection existed. ## In this guide - [Install Both Plugins](#install-both-plugins) - [Creating Your First Region (Spawn Protection)](#creating-your-first-region-spawn-protection) - [Setting Region Flags](#setting-region-flags) - [Giving Players Build Access](#giving-players-build-access) - [Useful WorldEdit Commands Beyond Selection](#useful-worldedit-commands-beyond-selection) - [Checking What Region You're Standing In](#checking-what-region-youre-standing-in) - [Common Setup Mistakes](#common-setup-mistakes) - [Protection boundary testing](#protection-boundary-testing) - [Keep region editing and world editing separate](#keep-region-editing-and-world-editing-separate) - [Official documentation and links](#official-documentation-and-links) - [Region priority and overlapping protections](#region-priority-and-overlapping-protections) ## WorldGuard and WorldEdit: The Basics That Protect a Server _Most servers install this pair on day one and still get it wrong, usually by protecting spawn and forgetting everything else._ WorldEdit handles building and terrain editing. WorldGuard handles protection: who can build, break, or interact where. They're built to work together, and most servers need both. ## Install Both Plugins [WorldEditA Minecraft Map Editor... that runs in-game! With selections, schematics, copy and paste, brushes, and scripting. Use it in creative, or use it temporarily in survival.On Modrinth ](https://modrinth.com/plugin/worldedit) [WorldGuardWorldGuard lets you and players guard areas of land against griefers and undesirables as well as tweak and disable various gameplay features of Minecraft.On Modrinth ](https://modrinth.com/plugin/worldguard) Choose compatible builds from the official listings. Stop the server, install WorldEdit and WorldGuard together, and check that both load without dependency errors after restarting. Drop `WorldEdit.jar` and `WorldGuard.jar` into `plugins/` and restart. WorldGuard depends on WorldEdit, so both need to be present or WorldGuard won't load. ## Creating Your First Region (Spawn Protection) Select an area with WorldEdit's wand (given by `//wand`, or just hold the default selection tool): left-click one corner, right-click the opposite corner. Then: ``` /region define spawn ``` This creates a region named `spawn` covering the selected area, owned by whoever ran the command. ## Setting Region Flags Flags control what's allowed inside a region: ``` /region flag spawn build deny /region flag spawn pvp deny /region flag spawn mob-spawning deny ``` `build deny` blocks all building and breaking inside the region for anyone without a bypass permission. This is what actually stops griefing, not just a sign that says "don't build here." ## Giving Players Build Access For a region where specific players (not everyone) should be able to build, such as a player's claimed plot: ``` /region addmember ``` With default region protection, members can build and non-members cannot. An explicit `build deny` can also block members; review the flag and region-group settings before testing access. ## Useful WorldEdit Commands Beyond Selection ``` //set stone fill the current selection with a block //copy copy the selection //paste paste the last copy //undo undo the last WorldEdit operation ``` The double-slash is intentional; it's how WorldEdit commands are distinguished from normal single-slash commands. ## Checking What Region You're Standing In ``` /region info ``` run with no arguments reports the region at your current location. It's useful for debugging overlapping regions or confirming a flag actually applied where expected. ## Common Setup Mistakes - **No global region fallback.** Anything outside a defined region falls back to the world's default rules. If build should be restricted everywhere by default, a region covering the entire world (or the `__global__` region) needs the deny flag too, not just specific protected areas. - **Overlapping regions with conflicting flags.** WorldGuard resolves conflicts by region priority, so set priorities explicitly (`/region setpriority `) instead of leaving it to defaults when regions overlap. - **Forgetting PvP-specific regions.** A combat arena needs `pvp allow` even if PvP is globally denied, since region flags override the global setting for that one area. ## Protection boundary testing Create a small test region and use a non-operator account to attempt the actions you intend to block. Verify interaction with other claim plugins, world-specific flags and region priority. Back up the world before using large WorldEdit operations, and test a restore procedure on a copy. ## Keep region editing and world editing separate Protection configuration and terrain editing solve different problems. Before using a WorldEdit command, inspect the selection and the scale of the intended change. Try the operation on a copy if it affects an important build. Before changing a WorldGuard flag, inspect membership, priority and overlaps. Do not treat a successful command response as proof that the right area was selected. Visit the boundary with a regular account and test the actual action. Keep broad deny rules rare and explain why they exist. Default membership protection may already cover the intended building restriction, while an explicit build deny can change member behavior. If a member cannot interact, review flags rather than granting a blanket bypass permission. Record staff changes to shared regions so the next administrator knows which behavior is deliberate. For major edits, retain a verified world backup; an undo history is not a complete disaster recovery plan. ### Troubleshooting paths - Wrong area changes: inspect the selection before repeating the command. - Member is blocked: check explicit flags, groups and higher-priority regions. - Spawn remains editable: retest as a non-member without bypass access. ## Official documentation and links - [WorldGuard region flags documentation](https://worldguard.enginehub.org/en/latest/regions/flags/) - [Setting Up GriefPrevention for Player Land Claims](https://www.zcraftstudios.com/blog/griefprevention-claims-setup) ## Region priority and overlapping protections When an action is allowed in one region but denied in another, inspect overlapping regions, priorities and parent inheritance before changing global flags. Test with a normal account standing at the exact affected coordinates. Keep a documented list of spawn regions, event regions and protected staff areas. Avoid setting broad global permissions just to resolve one local conflict. ## Continue reading - [Minecraft Chunk Corruption: Protect Builds, Then Recover](https://www.zcraftstudios.com/blog/minecraft-server-chunk-corruption-recovery) - [WorldGuard vs GriefPrevention: Land Protection Compared](https://www.zcraftstudios.com/blog/worldguard-vs-griefprevention-comparison) [ Previous guide A Minecraft Server Backup Script You Can Actually Set Up Today](https://www.zcraftstudios.com/blog/minecraft-server-backup-script-guide)[ Next guide Linking Vault to an Economy Plugin: The Full Setup](https://www.zcraftstudios.com/blog/vault-economy-plugin-setup)