WorldGuard Regions and Anticheat Exemptions: Scope Rules

Short answer

WorldGuard regions set flags for PvP, building, and other behavior. Whether an anticheat reads those flags depends on the anticheat and its version, so check its documentation before you assume a region switches a check off. A bypass tied to a region usually applies to everyone inside it, which can hide misuse in that area. Audit each exemption path, keep it narrow, and test the region borders on staging.

Check what the anticheat actually reads

Start by finding out whether your anticheat has any region-aware setting. Some anticheats read world names, permission nodes, or game modes. Others have no region setting at all. Look at the configuration and documentation for the version you run.

Do not infer from a flag's name. A PvP flag tells the server whether players can fight in a region. It does not tell you whether the anticheat changes its checks because of that flag. Confirm the link on your own staging server.

Find every bypass path

A bypass can come from a permission, a region, a world, or a game mode. Each one lets players skip some checks. Map them together, because a region exemption combined with a broad permission group grants more than either one alone. Permission groups often inherit from parent groups, so a group that looks narrow may carry extra permissions. Check inheritance in your permissions plugin before you count a path as closed.

Inventory regions on staging

Before you change anything, list each region with its owners and flags. The commands below use placeholder names. Replace them with your own region names on a staging copy.

/rg list
/rg info <region-name>
# Note each region's flags and owners.
# Compare the list with your anticheat's exemption settings.

Audit and narrow the exemptions

Work through the list in order. Remove anything that no longer matches a real activity, and keep only the exemptions you can justify in writing.

• Write down every region, its owner, and its flags on the staging copy.
• Write down every anticheat exemption path from the table above.
• Remove any exemption that is not tied to a real activity in that area.
• Narrow a region exemption to the one check that the activity needs, if your anticheat supports that.
• Give a staff test account the same bypass as the affected group, then confirm the bypass does what you expect and nothing more.
• Record which regions stay exempt, which check each one relaxes, and why.

Test the region borders

Players often behave differently at the edge of a region. Stand just inside and just outside each border and repeat a few actions: moving, breaking blocks, and hitting another player. Log which checks alert in each spot.

If a check goes quiet only inside the region, the exemption covers more than its name suggests. Also repeat one action that the anticheat should still catch, and confirm the log entry appears. That confirms the exemption did not switch off everything in the area.

Keep the border results in a small table with three columns: region, action, and whether the check alerted. Store it with the exemption list. When a region changes owner or flags, rerun only the border tests for that region instead of the full audit.

Set a review cadence for exemptions

Set a review date for every exemption. A quarterly pass is a reasonable default for many networks, and a network that changes its regions often may need a shorter cycle. At each pass, ask whether the activity still happens in that area, whether everyone in the group still needs the access, and whether new staff were added to the group without a review.

What we have not verified

We have not tested WorldGuard together with any anticheat. Region flags, plugin versions, and anticheat settings can interact in ways this page cannot predict. Confirm each behavior on your own staging copy before you apply it to a live network.