GriefPrevention3D v18.4.3

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

Overview

• Protection fix: container trust was enough to break a claim's minecarts and boats. It now takes build trust.
• Locale fix: the bundled Czech translation was registered nowhere, so cs_CZ could not be selected at all.

Breaking a claimed vehicle now needs build trust

Vehicle damage was checked against container trust — the same level that opening a chest minecart takes. Any claim that grants container trust broadly, such as a public shop or a warp handing out trial loot, therefore let visitors break its minecarts and boats and walk off with the drops.

Breaking a vehicle destroys it, so it is now checked against build trust. Nothing else about vehicles changed:

• Riding a boat still takes access trust.
• Opening a chest or hopper minecart still takes container trust.
• Non-player damage — creepers, withers, TNT — is still blocked outright inside claims.

The only players who lose anything are those who were never trusted to build in the first place.

This is not a Minecraft 26.2 regression, despite when it started being reported. Minecraft 26.3 still routes vehicle damage through VehicleDamageEvent before VehicleDestroyEvent, exactly as earlier versions did, so the events GriefPrevention listens for never stopped arriving — the trust level being asked for was simply the wrong one.

Czech locale was never registered

Czech translations shipped in the jar, but the locale was never registered. messages_cs_CZ.yml was only known to nothing — neither the list of bundled locale files nor the list of supported locale codes — so it was never extracted to the Lang/ folder and could not be selected by anything. Locale: cs_CZ in config.yml fell back to English, and a Czech client was silently ignored on servers running per-player locales.

Two missing registrations

The locale system keeps two lists, and cs_CZ was in neither:

• BUNDLED_LOCALE_FILES — the files unpacked from the jar into Lang/ on first start. An unlisted file stays bundled, unreachable no matter what the configuration asks for.
• SUPPORTED_LOCALE_CODES — the codes accepted by Locale: in config.yml and matched against a client's language for the per-player locale feature.

messages_cs_CZ.yml is now registered in both. Server admins can set Locale: cs_CZ, and Czech clients get their language automatically when PerPlayerLocale is left enabled, falling back to English where a message has no Czech translation yet.

README: the language situation is now documented

The README previously claimed only Spanish and Portuguese clients were served their own language. A new Supported Languages section lists all fourteen bundled locales — English, Czech, German, Spanish, French, Japanese, Malay, Polish, Portuguese (Brazil), Russian, Turkish, Ukrainian, Chinese (Simplified) and Pirate Speak — and clarifies how the per-player locale feature actually behaves. The section links to the Locale guide for customising or adding languages.

The same pass tidied the README's feature lists: /scrollresize is now covered under Key Features, and the v18.4.2 rate limiting under Subtle Changes. Documentation only; no plugin behaviour changed.

Also merged: the upstream raid-location fix

The raid trigger check upstream shipped this cycle now looks up the claim at the raid's location rather than the player's. GP3D has done the same since the handler was pulled into its own class — and it additionally falls back to the player's location when no claim is at the raid site — so the merge kept GP3D's version unchanged.

Upgrade notes

Players holding only container trust can no longer break vehicles in a claim. If your server relies on visitors breaking carts — a public minecart station where riders pick their cart back up, for instance — those players need build trust, or the carts need to sit outside the claim.

No configuration or storage changes. Run the new jar once and the Czech translation is extracted to Lang/; it is then selectable as Locale: cs_CZ or served to Czech clients automatically. Drop-in replacement for v18.4.2.