WorldGuardFork (Paper/Folia) | Recommended for every modern server!

UNOFFICIAL FORK DISCLOSURE
This is an independent, unofficial fork of WorldGuard 7.0.17, based on the work of EngineHub and WorldGuard contributors. It is not affiliated with, endorsed by, or supported by EngineHub.
The goal is not to replace upstream WorldGuard in every environment. This fork targets modern Paper/Folia servers that want fully configurable localization, a smoother claiming workflow, stronger region-owner safeguards, and a smaller region-focused build without several legacy subsystems.
Support for this build is provided by the fork maintainer through hPlugin. Questions about upstream WorldGuard should be directed to its official documentation and community.
WHY USE THIS FORK?

• Complete Russian and English packs: configuration, player messages, and console log templates are localized
• Native Paper Brigadier commands with contextual suggestions for worlds, regions, players, flags, and values
• A better claiming workflow: group-based count and volume limits, real polygon volume, safe automatic expansion, and a particle preview of the final claim
• Per-world region templates through a dedicated regionDefaults.yml
• A different denial message for each blocked command, including subcommands
• A redesigned region query cache with a repeated-query fast path and explicit invalidation after mutations

The smaller artifact and redesigned cache are architectural facts, not a promise of a specific TPS or RAM improvement. Meaningful performance numbers require testing on your own workload.
COMPARISON WITH OFFICIAL WORLDGUARD 7.0.17
Choose this fork when your network runs Paper/Folia and values localization, modern claim UX, configurable templates, and a clean YAML workflow.
Choose official WorldGuard when you need plain Spigot/CraftBukkit, SQL region storage, the legacy blacklist, removed utility commands, or the widest compatibility with third-party WorldGuard extensions.
LOCALIZATION AND MESSAGE ENGINE
On first setup, select ru or en. Each language ships with its own templates:

• 318 message definitions per language
• 86 configurable console-log texts per language
• MiniMessage colors, gradients, click events, and hover events
• Per-entry delivery through message, actionbar, or title
• Per-entry cooldownMillis throttling
• Validation for unknown MiniMessage tags, invalid modes, cooldowns, and title line counts
• Validation for duplicate YAML keys, UUIDs, flags, values, command categories, and mismatched limit groups
• Default comments restored during safe configuration saves

Player feedback, command errors, and console output can be adapted to your network without editing the JAR.
CLAIMS, LIMITS, AND AUTOMATIC EXPANSION
Permission-group limits
Configure both of these values for each permission group:

• maximum number of regions owned by a player;
• maximum volume of a newly claimed region.

When a player belongs to several configured groups, the highest matching value is used. worldguard.region.unlimited bypasses these limits.
Cuboid and polygon claims
The fork accepts both cuboid and polygon selections for /rg claim. Polygon volume is calculated from its footprint and height, with self-intersection and overflow protection, so volume limits can be enforced consistently.
Safe automatic expansion
Claims can expand along any configured combination of -Y, +Y, -X, +X, -Z, and +Z. Downward and upward expansion are enabled by default.
Expansion stops at world bounds, the player's remaining volume allowance, or a foreign region. Overlap with regions already owned by the player is allowed. The maximum safe distance is calculated for each direction, and the particle preview displays the resulting shape before the claim is created.
claimOnlyInsideExistingRegions can additionally require new claims to remain inside existing regions.
SELECTION VISUALIZATION
Completed WorldEdit selections can be rendered as particle borders in the world. Cuboids and polygons are supported.

• Configurable RGB color, particle size, and point spacing
• Per-update particle budget
• Maximum display distance
• Configurable update period
• Player view-distance culling
• Preview of the final auto-expanded claim
• Selection cleanup after a successful claim/define/redefine — 30 seconds by default
• Maximum lifetime for an unchanged completed selection — 180 seconds by default
• Folia-aware global and entity scheduling

The default visualization color is #FDBE00.
PER-WORLD REGION TEMPLATES
regionDefaults.yml supports a wildcard * template and exact world entries.
New regions can receive predefined:

• priority and parent;
• owners and members by UUID or permission group;
• initial flags;
• blocked-command categories;
• a dedicated message for every command category.

The __global__ region can be created automatically and populated with defaults. clearFlags removes selected global values. Optional application to existing regions fills missing flags and a missing parent without overwriting manually configured values.
CUSTOM BLOCKED-COMMAND MESSAGES
The new blocked-cmds-messages map flag associates a command or subcommand with its own denial response.
Matching normalizes namespace prefixes, letter case, and extra whitespace. When there is no exact entry, the handler checks shorter command paths before falling back to the standard denial message. The technical map can be hidden from /rg info when required.
REGION MANAGEMENT SAFEGUARDS

• Adding an offline player as an owner or member requires repeating the exact command within 30 seconds
• preventLastOwnerRemoval prevents accidental removal of a region's final owner
• Overlap errors identify the conflicting region, inherited owners, and intersection coordinates
• Localized interactive elements in /rg info, /rg list, and the flags UI speed up common tasks
• The default list mode requires an explicit my or global scope; legacy behavior can be restored
• NPC and fake-player causes no longer receive a blanket build bypass
• Legacy owner names can be migrated to UUIDs during YAML loading with a one-time backup
• Region files use safe replacement to reduce the risk of a partially written YAML file

SCOPED WORLD MECHANICS
Many settings for block physics, fire and lava, TNT, explosions, and entity behavior support three scopes instead of one global boolean:
This can keep a mechanic active in a player's own claim while blocking it in someone else's, or protect only wilderness areas. Global and per-world configuration inheritance is validated on load.
COMMANDS AND SUGGESTIONS
Command roots:
Core region commands:
Brigadier suggests available worlds, region IDs, online players, flags, flag groups, and valid values. The parser supports quoted and escaped arguments, --, and packed short options.
PERMISSIONS
The standard WorldGuard model with operation- and region-specific permissions remains in use. Key nodes include:
Operations such as redefine, remove, select, info, teleport, domain management, and flag changes use WorldGuard's dynamic permissions for the target region and access level.
CONFIGURATION AND STORAGE

• locale.yml — first-start ru or en selection
• config.yml — global settings, limits, visualization, messages, and mechanics
• messages.yml — all player-facing messages
• logs.yml — configurable console output
• regionDefaults.yml — templates for new, existing, and global regions
• worlds/<world>/config.yml — per-world settings
• worlds/<world>/regions.yml — YAML region storage
• cache/profiles.sqlite — local player-profile cache

/wg reload reloads configurations, messages, logs, region templates, and world settings, then refreshes related caches and session state. A full restart is recommended when changing locale or scheduler intervals.
COMPATIBILITY AND INTENTIONAL TRADE-OFFS
This fork deliberately narrows WorldGuard to region protection on current Paper/Folia servers. The following upstream components are removed:

• the legacy blacklist system and its dedicated logging;
• SQL region storage, Flyway, and migratedb, migrateuuid, and migrateheights;
• bStats;
• sign chest protection and CommandBook integration;
• built-in report, profiler, and debug tooling;
• /god, /ungod, /heal, /slay, /locate, and /stack;
• /stopfire, /allowfire, /stoplag, and /halt-activity;
• legacy plain-Spigot/CraftBukkit and PaperLib compatibility layers;
• send-chat, receive-chat, notify-enter, and notify-leave flags.

The new blocked-cmds-messages flag is added. Region storage is YAML-only. Removed flag values found in an existing regions.yml are preserved as unknown flags, but their old behavior is no longer executed.
Some upstream internal classes and methods are also removed or changed. Core region and flag behavior remains, but universal binary compatibility with every third-party WorldGuard extension is not guaranteed. Test each add-on in a staging environment.
This build directly uses Paper APIs. Despite being listed on Spigot.org, plain Spigot/CraftBukkit is not supported.
REQUIREMENTS

• Paper or Folia 1.21.x
• Java 21
• WorldEdit — a build compatible with your server version

The fork keeps the plugin name WorldGuard, so it cannot run alongside the official JAR.
INSTALLATION AND UPSTREAM MIGRATION

1. Stop the server and make a complete backup of plugins/WorldGuard.
2. Remove the official WorldGuard JAR from plugins. Never load both builds together.
3. Install a compatible WorldEdit build and place this fork JAR in plugins.
4. Start the server once. The plugin creates locale.yml and disables its own runtime until a language is selected.
5. Set locale: ru or locale: en, then fully restart the server.
6. Generate fresh global and per-world configuration when migrating from official 7.0.17. This fork uses a different configuration schema and does not migrate the old config.yml.
7. Move worlds/<world>/regions.yml files on a staging server first. SQL-backed regions are not loaded by this fork.
8. Before opening the server, review group tables, command categories, and exact-world profiles in regionDefaults.yml, especially the bundled spawn profile.
9. Test third-party add-ons, cuboid and polygon claims, flags, automatic expansion, and reload behavior in staging.

LICENSE, SOURCE, AND ATTRIBUTION
Upstream project: WorldGuard by EngineHub and contributors, version 7.0.17. Official documentation: worldguard.enginehub.org.
This fork is distributed under the GNU Lesser General Public License v3.0 (LGPL-3.0-only).
Fork source code: 2twofactorauth3-star/WorldGuard-fork-hplugin: A high‑quality fork of the WorldGuard plugin. (by https://t.me/hplugin)
EngineHub and its contributors retain authorship of the upstream WorldGuard code. The fork author is responsible for the fork-specific changes and support.