https://sourceforge.net/p/griefprevention3d/wiki/Migration/Recent changes to MigrationenThu, 02 Jul 2026 13:04:30 -0000https://sourceforge.net/p/griefprevention3d/wiki/Migration/<div class="markdown_content"><pre>--- v1 +++ v2 @@ -14,6 +14,7 @@ | Area | What | Default | |------|------|---------| | 3D Subdivisions | `/3dsubdivideclaims` — subclaims with real Y-level bounds | Available always | +| 3D Admin Claims | `/3dadminclaims` — free, height-bounded admin claims with exact Y bounds. Also `/aclaim mode admin3d`. | Permission-gated (`griefprevention.adminclaims`) | | Shaped Claims | `/shapedclaims`, `/shapedclaim` — orthogonal polygon parent claims | **Off** (`AllowShapedClaims: false`) | | Nested Subclaims | Subdivisions inside subdivisions | **Off** (`AllowNestedSubClaims: false`) | | Visualization Glow | Glowing claim borders (1.19.3+) | **Off** (`VisualizationGlow: false`) | </pre> </div>Jack KorteThu, 02 Jul 2026 13:04:30 -0000https://sourceforge.net623591bbe7f352a70da68636a8eb6a07c10defd3https://sourceforge.net/p/griefprevention3d/wiki/Migration/<div class="markdown_content"><h1 id="h-migration-from-upstream-griefprevention">Migration from Upstream GriefPrevention</h1> <p>This page summarizes what is <strong>new, different, or worth double-checking</strong> when moving from the original GriefPrevention (RoboMWM) to GriefPrevention3D. It is intentionally short — the goal is to help server owners recognize what has changed without reading the whole wiki.</p> <h2 id="h-tldr">TL;DR</h2> <ul> <li>Claims are <strong>backwards compatible</strong>. Existing rectangle claims load without modification.</li> <li>Most <strong>commands and permissions are identical</strong> to upstream. GP3D adds a few new ones.</li> <li>Several features are <strong>off by default</strong> and must be opted into in <code>config.yml</code>.</li> <li>There is now a <strong>unified <code>/claim &lt;subcommand&gt;</code></strong> surface on top of the existing standalone commands.</li> </ul> <h2 id="h-whats-new">What's New</h2> <table> <thead> <tr> <th>Area</th> <th>What</th> <th>Default</th> </tr> </thead> <tbody> <tr> <td>3D Subdivisions</td> <td><code>/3dsubdivideclaims</code> — subclaims with real Y-level bounds</td> <td>Available always</td> </tr> <tr> <td>Shaped Claims</td> <td><code>/shapedclaims</code>, <code>/shapedclaim</code> — orthogonal polygon parent claims</td> <td><strong>Off</strong> (<code>AllowShapedClaims: false</code>)</td> </tr> <tr> <td>Nested Subclaims</td> <td>Subdivisions inside subdivisions</td> <td><strong>Off</strong> (<code>AllowNestedSubClaims: false</code>)</td> </tr> <tr> <td>Visualization Glow</td> <td>Glowing claim borders (1.19.3+)</td> <td><strong>Off</strong> (<code>VisualizationGlow: false</code>)</td> </tr> <tr> <td>Unified <code>/claim</code></td> <td><code>/claim create</code>, <code>/claim trust</code>, <code>/claim abandon</code>, etc.</td> <td><strong>On</strong> in <code>alias.yml</code></td> </tr> <tr> <td><code>/makeadmin</code> / <code>/makebasic</code></td> <td>Convert claims to/from admin</td> <td>Permission-gated (<code>griefprevention.adminclaims.convert</code>)</td> </tr> <tr> <td><code>/witherexplosions</code></td> <td>Per-claim wither explosion toggle</td> <td>Permission-gated (<code>griefprevention.witherexplosions</code>, default <code>true</code>)</td> </tr> <tr> <td>Boundary Violation Alerts</td> <td>Warn claim owners when pistons/liquids are blocked at their border</td> <td>On (smart deduplication + burst detection)</td> </tr> </tbody> </table> <h2 id="h-whats-changed">What's Changed</h2> <h3 id="h-claim-selection-after-resize">Claim Selection After Resize</h3> <p>When a player <strong>resizes a claim</strong>, that claim becomes the "selected claim" for their session. Commands like <code>/trust</code>, <code>/untrust</code>, <code>/trustlist</code>, <code>/abandonclaim</code>, <code>/claimexplosions</code>, and <code>/witherexplosions</code> then run against the selected claim even if the player is no longer standing inside it. This removes the old "stand in the claim, then type the command" dance for common admin flows.</p> <h3 id="h-restrictsubclaim-from-a-parent-claim"><code>/restrictsubclaim</code> from a Parent Claim</h3> <p>Running <code>/restrictsubclaim</code> while standing in a <strong>top-level claim</strong> (not inside a subdivision) now instantly restricts <strong>all</strong> subdivisions inside that claim in one go. Previously this had to be done per-subclaim.</p> <h3 id="h-trustlist-shows-inheritance"><code>/trustlist</code> Shows Inheritance</h3> <p><code>/trustlist</code> now displays <strong>inherited permissions</strong> from the parent claim, not just explicit trusts on the current (sub)claim. This makes it obvious why a player has access somewhere.</p> <h3 id="h-eavesdrop-permissions-split">Eavesdrop Permissions Split</h3> <p>The single <code>griefprevention.eavesdrop</code> permission has been split for finer control:</p> <ul> <li><code>griefprevention.eavesdrop.pm</code> — see <code>/tell</code>-style private messages.</li> <li><code>griefprevention.eavesdrop.softmute</code> — see soft-muted messages.</li> <li><code>griefprevention.eavesdrop.signs</code> — see sign placements as chat messages (already existed upstream).</li> <li><code>griefprevention.eavesdrop.immune</code> — exempt from being eavesdropped.</li> <li><code>griefprevention.eavesdrop</code> still exists as a blanket/legacy permission.</li> </ul> <p>If you previously granted <code>griefprevention.eavesdrop</code> to staff, they will keep the same behavior. If you want only PM eavesdropping or only softmute eavesdropping, use the narrower nodes.</p> <h3 id="h-boundary-violation-alerts-new">Boundary Violation Alerts (New)</h3> <p>Pistons and liquids that get blocked at a claim boundary now send a <strong>chat message to the claim owner</strong> (if they're online) explaining where the violation occurred. This covers:</p> <ul> <li>Piston pushing a block <strong>into</strong> a claim.</li> <li>Piston pushing a block <strong>out of</strong> the owner's own claim into someone else's.</li> <li>Water or lava trying to flow <strong>into</strong> or <strong>out of</strong> a claim.</li> </ul> <p>Messages are deduplicated per-location, with spatial buffers (8 blocks for water, 5 blocks for lava in overworld/end, 8 for lava in the nether). Rapid sequential violations are burst-condensed into a single summary line. See <a href="./Administrator-Guide#boundary-violation-alerts">Administrator's Guide › Boundary Violation Alerts</a>.</p> <blockquote> <p><strong>Note</strong>: this is a <strong>feedback-only</strong> system. The goal is helping players understand where flow is being blocked, not adding new protection switches.</p> </blockquote> <h2 id="h-upgrading-steps">Upgrading Steps</h2> <ol> <li><strong>Backup</strong> your <code>plugins/GriefPreventionData/</code> folder.</li> <li>Replace the plugin jar with the GP3D build.</li> <li>Start the server and watch the console for migration-related log messages.</li> <li>Review <code>config.yml</code> — the new toggles (<code>AllowShapedClaims</code>, <code>AllowNestedSubClaims</code>, <code>VisualizationGlow</code>) will be appended if missing.</li> <li>Review <code>alias.yml</code> for the unified command handler settings.</li> <li>Restart once more, or run <code>/gpreload</code> if you only changed config values.</li> </ol> <p>Existing claims, trust data, and claim block totals are preserved. Rectangle claims continue to work exactly as before; shaped polygon claims are only created when a player explicitly enters shaped mode (and only if <code>AllowShapedClaims: true</code>).</p> <h2 id="h-rollback">Rollback</h2> <p>The data format is forward-compatible for rectangle claims, so going back to upstream GP will usually work, <strong>but</strong>:</p> <ul> <li>Any <strong>shaped (polygon) claims</strong> created with GP3D will not round-trip back to upstream GP. Upstream does not understand polygon footprints and will reject or truncate the data.</li> <li>Any <strong>3D subclaims</strong> with Y-level bounds will not round-trip back to upstream GP either.</li> </ul> <p>If you know you might roll back, keep <code>AllowShapedClaims: false</code>. Or, more simply, take a full backup of <code>GriefPreventionData/</code> before enabling those features.</p></div>Jack KorteThu, 02 Jul 2026 13:04:28 -0000https://sourceforge.net775cfdd06843e6c506993172ad9acbf07fbfa666