🛡️ ClaimShift

ClaimShift changes how protected player regions behave based on active owner presence.

It does not replace your claim plugin. Instead, it works on top of supported region systems and decides when selected claims should be OPEN, in GRACE, or PROTECTED.

PROTECTED state — ClaimShift informs the player when the current territory is protected.

Built for dynamic survival and raid servers: keep old administrative regions safe, let new player claims become dynamic automatically, and control exactly when protection changes.

⚙️ How it works

ClaimShift provides two presence policies:

• offline-open — active owners keep the region protected. After the last active owner disappears, the region stays protected for the configured delay and then becomes raidable. This is the default for fresh installations.
• online-open — active owners make the region raidable, while the region returns to protection after no active owners remain and the configured delay expires.

Fresh-install defaults use offline-open with:

• ⏳ 1 hour before an inactive/offline claim becomes OPEN
• 🛡️ 5 minutes before protection returns after an active owner comes back to a claim that is already OPEN

Both delays are configurable. Use 0 or 0s for an immediate transition.

🧠 Smart Presence

Being connected does not always mean being active.

ClaimShift can use Smart Presence to reduce simple AFK protection abuse:

• idle/meaningful-activity tracking
• repeated activity-pattern detection for simple timed AFK macros
• optional CMI AFK integration
• optional EssentialsX AFK integration
• separate connected-owner and active-owner information in /claimshift inspect

Smart Presence is deliberately conservative: it does not ban, kick, or label players as bots or cheaters.

🌍 WorldGuard integration

WorldGuard is the primary full dynamic integration.

ClaimShift uses a safe region lifecycle by default:

• 🧱 WorldGuard regions that already exist when ClaimShift first sees a world are recorded as a legacy/static baseline
• ⚡ Player-owned regions created after that baseline become dynamic automatically
• 🏷️ Normal /rg claim / /rg define workflows are picked up automatically; no extra ClaimShift flag is required for new eligible player regions
• 🔐 Old regions are not retroactively converted into raidable claims
• 🏛️ Ownerless administrative regions are ignored

The automatic behavior can be overridden at any time.

Keep a region static:

/rg flag <region> claimshift-dynamic deny

Explicitly enable an older/static region:

/rg flag <region> claimshift-dynamic allow

This makes it easy to keep spawn, shops, event areas, staff regions and other administrative zones on normal WorldGuard protection while new player claims use ClaimShift automatically.

Additional per-region controls are available:

claimshift-policy
claimshift-active-delay
claimshift-inactive-delay
claimshift-raids

⚔️ Raid Sessions

Optional Raid Sessions can prevent protection from suddenly returning in the middle of an active raid.

When enabled, qualifying activity against an already OPEN claim can keep a temporary raid session active until its inactivity timeout or hard maximum duration is reached.

Raid Sessions are disabled by default.

🔒 Protection rules

Protection can be configured independently for:

• block breaking and placing
• containers and inventories
• explosions
• entity damage and interaction
• hanging entities
• pistons
• fluids
• fire and fire spread
• hoppers and other container automation

ClaimShift also tries to preserve normal automation inside the same protected claim while blocking behavior across protected boundaries.

🧪 Dry-run safety

A brand-new installation starts in dry-run mode.

While dry-run is enabled, ClaimShift calculates and reports what it would do but does not modify WorldGuard state and does not enforce ClaimShift protection rules. Normal WorldGuard protection continues to work as usual.

🧪 Recommended first step: use /claimshift inspect on a few player and administrative regions before disabling dry-run.

Use:

/claimshift inspect
/claimshift dryrun status
/claimshift dryrun off

Existing installations are not automatically switched back into dry-run when updating.

🌐 Localization

ClaimShift includes built-in support for:

• English
• Russian
• German
• Spanish
• French
• Polish
• Brazilian Portuguese
• Ukrainian
• Simplified Chinese

Configuration comments and messages can use separate locales. Custom message overrides are preserved when changing language.

Command names and subcommands are intentionally language-independent. Localization changes descriptions, messages and configuration comments without translating executable command syntax.

Messages use Adventure MiniMessage and support customizable formatting and HEX colors.

🛟 Safety and recovery

• temporary WorldGuard passthrough changes are tracked and restored safely
• crash-recovery metadata protects against interrupted runtime changes
• safe reload validates new configuration before replacing the current working configuration
• invalid durations, locales or MiniMessage strings do not leave the plugin partially reloaded
• the persistent WorldGuard region registry keeps legacy/static and automatically dynamic classifications stable across restarts

💻 Commands and permissions

Command	Description	Permission
/claimshift help	Shows available ClaimShift commands	—
/claimshift info	Shows runtime and provider information	claimshift.info
/claimshift inspect	Inspects the current claim and its state	claimshift.inspect
/claimshift sync	Requests immediate provider synchronization	claimshift.sync
/claimshift reload	Safely validates and reloads configuration	claimshift.reload
/claimshift language	Changes configuration/message locale	claimshift.language
/claimshift dryrun	Controls dry-run diagnostics	claimshift.dryrun

Alias: /cshift

claimshift.admin grants the administration commands but intentionally does not grant claimshift.bypass, allowing administrators to test real protection behavior.

🧩 Compatibility

• Minecraft: 26.2+
• Java: 25+
• Platforms: Paper, Purpur, Leaf, Folia
• Primary region engine: WorldGuard

Spigot is intentionally unsupported.

Lands is available as an optional overlay integration; it is not currently equivalent to WorldGuard's full dynamic-open implementation.

📊 Anonymous metrics

ClaimShift can send anonymous usage statistics through bStats when metrics are enabled.

Custom ClaimShift charts contain only coarse configuration information such as presence policy, provider, WorldGuard mode, locale, Smart Presence settings and the global Raid Sessions setting.

ClaimShift custom charts do not send player names, UUIDs, claim names, chat content, world content or server addresses. Metrics can be disabled by the server owner, and the global bStats opt-out is respected.

---

💬 Found an edge case? ClaimShift is still evolving. If you encounter a problem with WorldGuard regions, overlapping claims, Smart Presence or protection rules, please report it on GitHub with /claimshift info, /claimshift inspect and enough information to reproduce the issue.