ClaimShift

ClaimShift 1.3.1

WorldGuard region lifecycle

• Existing WorldGuard regions are now kept static by default when ClaimShift first establishes its baseline.
• New eligible player-owned regions created while ClaimShift is running become dynamic automatically.
• New /rg claim / /rg define regions no longer require an extra claimshift-dynamic allow flag.
• Common /rg / /region mutation commands now request a near-immediate ClaimShift reconciliation.
• Automatic/legacy region classification persists across restarts in the internal region-registry.yml.
• Regions first discovered while a world was unavailable are handled conservatively as pre-existing/static.
• Deleted region classifications are pruned so a region recreated later can be treated as new.
• Explicit claimshift-dynamic allow/deny, include/exclude selectors and manage-all-owned-regions remain available as administrator overrides.

Diagnostics and inspect

• /claimshift inspect now explains why a region is dynamic or static.
• Management source can identify automatic new regions, legacy/static regions, manual overrides, selectors and manage-all behavior.
• Regions intentionally skipped because they already had administrator-owned passthrough: ALLOW are now explained instead of appearing contradictory.
• First-install dry-run notices now clearly state that ClaimShift is preview-only while normal WorldGuard protection continues to work.
• The dry-run notice tells administrators to inspect a test player region before enabling real ClaimShift enforcement.

Documentation

• Updated configuration comments, README, compatibility notes and manual tests for the old-static/new-dynamic lifecycle.
• Updated the public EN/RU website and Wiki.
• Website language selection now uses Russian automatically for Russian browser locales and English for every other locale, with manual EN/RU selection remembered locally.