GriefPrevention3D v18.3.5 — Fabric 1.21.11 (experimental alpha)

Wiki: https://github.com/castledking/GriefPrevention3D/wiki

Roadmap: platforms/fabric-1.21.11/ROADMAP.md — current target 1.21.11, next stop Minecraft 26.1.2 (first unobfuscated release; Loom swap, Java 25, mixin risk assessment inside).

Still an alpha, dedicated-server-only build. Not feature complete, not a drop-in replacement for the Paper plugin. Back up GriefPreventionData before running it. Requires Fabric API; LuckPerms optional but recommended.

Overview

This build retires the monolithic /gp3d command root in favor of the same standalone command surface Paper players already know, and ports GP3D's alias.yml command-customization system to Fabric so both platforms read one configuration. The same development cycle also delivered player-facing denial feedback and messages.yml support, which are summarized below.

/gp3d subcommands become standalone commands

Every player-facing action that used to live under the single /gp3d Brigadier literal is now a top-level command:

Old	New
/gp3d claim create ...	/createclaim
/gp3d claim trust <target> <type>	/trust <target> <type>
/gp3d claim untrust <target>	/untrust <target>
/gp3d claims list	/claimslist
/gp3d claim abandon	/abandonclaim
/gp3d blocks	/claimblocks
/gp3d claim here	/claimhere
/gp3d claim pvp on|off	/claimpvp on|off

/gpstatus and /gpreload keep their names — they were already top-level.

The old /gp3d ... spellings are gone rather than deprecated; this is an alpha and the rename is the point. Anything scripted against /gp3d (test harnesses, command blocks) needs updating once. The manual migration checklist in the platform README uses the new names throughout.

alias.yml is now shared with Paper

The command alias system moved from the Bukkit plugin into gp3d-core, and Fabric reads the same alias.yml shape Paper does:

• commands: lists map a canonical subcommand onto alternate literals;
• standalone: lists control which top-level commands exist at all;
• arguments: blocks drive Brigadier suggestion types (player, integers, fixed option lists);
• per-subcommand and per-root enable: false removes them from the tree.

A new registrar builds the Brigadier command tree directly from this merged configuration instead of hand-written registrations, so a server operator can disable or rename commands once and both platforms follow. Fabric honors the global standalone: switch: when standalone commands are disabled, only the root trees remain registered.

Because Brigadier trees are built at registration time, command changes apply on /gpreload through re-registration and the client's next command-tree sync.

Denial feedback and messages.yml

Shipped alongside the command work in the same cycle (see the platform README for the full checklist):

• Refused block breaks, block uses, entity attacks, and entity interactions reply in red chat with the same message keys Paper uses (NoBuildPermission, NoContainersPermission, NoAccessPermission), resolving {0} to the owner's name — subdivisions name the parent's owner, admin claims say "an administrator".
• Protection denials are rate limited to one message per player per ten seconds, matching Bukkit's sendRateLimitedErrorMessage; cooldowns drop on disconnect.
• Player-facing text is read from messages.yml, accepting both the plain-key and legacy <Key>.Text shapes, translating &/$ codes, &#RRGGBB hex, and \n before placeholder substitution, falling back to shipped defaults for missing keys, and treating a blanked message as disabled. Unknown addon keys survive read-modify-write cycles.

Combat trust note

Paper's v18.3.5 adds opt-in PvP/PvE combat trust (see v18.3.5.md). The shared claim codec already persists both trust sets, so Fabric claim files round-trip them today; wiring Fabric enforcement and /trust type arguments to those sets is tracked in the roadmap rather than this alpha.

Also in this release

• Neighbor trust persistence hardening shared with Paper, including allowAllNeighbors.
• Upstream merge: interacting with an untamed horse no longer clears its equipment (#2624).