Development preview: 0.2.2 has open Bedrock rendering and performance issues. These pictures show offline asset previews, not verified results on every client. Test in a backup world before using this experimental pack.

Dreadplate Regalia — admin notes

Quick reference for EGW Dreadplate 0.3.0, namespace egw_showcase. Use Paper 26.3 with Packforge; add Geyser and Floodgate for Bedrock players.

The full step-by-step install is INSTALL.md in the release. This page is the map, not the manual — where things go, what to type, and the one test that matters.

Install order

Install the content folders in Packforge, then run /pf zip and confirm the build succeeds before testing the items.
Grant the recipe permissions (see below). There is no default grant — without this, players see no recipes and will tell you the set is broken.
Geyser second. Pack and mappings in, then a full server restart. /geyser reload does not pick up mapping changes.
Verify on a non-op account, Java first, then a Bedrock client.

Which files go where

File	Destination
The bundle’s `egw_showcase/` content folder	`plugins/Packforge/contents/egw_showcase/`
The bundle’s `egw_showcase_atlas/` folder	`plugins/Packforge/contents/egw_showcase_atlas/` — keep this passthrough root separate
`EGWDreadplate-Models-Bedrock-0.2.2.mcpack`	`plugins/Geyser-Spigot/packs/`
`egw_showcase_models.json`	`plugins/Geyser-Spigot/custom_mappings/`
`egw_showcase_wings_v1.json`	`plugins/Geyser-Spigot/custom_mappings/` — optional, see the Wings v1 switch
The standalone Java ZIP	For manual Java resource-pack hosting or visual checks
`EGWDreadplate-Complete-0.2.2.zip`	everything above plus the docs — unpack anywhere, then place the pieces

Four configs ship in contents/egw_showcase/configs/: dreadplate.yml, grims_scythe.yml, dreadplate_recipes.yml, dreadplate_retrim_lock.yml.

Geyser config needs force-resource-packs: true. After a mapping change, check latest.log for Error reading definition(s).

Permissions

pf.recipe.egw_showcase.dreadplate
pf.recipe.egw_showcase.grims_scythe

Grant these two permissions to players. Avoid a blanket recipe wildcard for Dreadplate: it also grants egw_retrim_lock, which can consume a trim template without changing the item. Test with a non-op account.

Handing out items

/pf give <player> egw_showcase:dreadplate_helmet
/pf give <player> egw_showcase:dreadplate_chestplate
/pf give <player> egw_showcase:dreadplate_leggings
/pf give <player> egw_showcase:dreadplate_boots
/pf give <player> egw_showcase:dreadplate_wings
/pf give <player> egw_showcase:dreadplate_wings_v2
/pf give <player> egw_showcase:grims_scythe

Note the id: Wings v1 is dreadplate_wings, not dreadplate_wings_v1. Only its display name carries the "v1".

Both Wings have no recipe and are /pf browse only. The other five craft from netherite blocks.

The Wings v1 switch: look or gliding

This is a decision, not an experiment. Both outcomes are already known — you pick one.

egw_showcase_wings_v1.json is a separate mapping file on purpose, so the switch is one file and a restart — no rebuild, no config edit.

File present (as shipped) → Bedrock sees the real Dreadplate Wings art and cannot glide with them. Any mapped custom item loses Bedrock gliding (GeyserMC #3299); the build calls it out as warning MG08.
File deleted, server restarted → v1 falls back to passthrough: Bedrock glides normally and sees a plain vanilla elytra named "Dreadplate Wings v1".

Java is unaffected either way; v1 glides on Java in both states. Make the call, then say which one, so the Wings entry can fold back into egw_showcase_models.json and the set ships one mapping file.

Wings v2 can never glide on Bedrock. It is mapped onto minecraft:netherite_chestplate, and a mapped custom item does not glide (GeyserMC #3299), so there is no switch for it. Not a failure — it is the look-only side of the comparison.

Re-trim lock

dreadplate_retrim_lock.yml blocks all 792 re-trim combinations at the smithing table. It exists because custom armor carrying a registry trim has crashed Bedrock clients on PS5 and Android.

A normal player gets an empty result slot and IA's no-permission message.
To disable it: rename to dreadplate_retrim_lock.yml.off, then /pf reload.
Do not /give registry-trimmed Dreadplate pieces, to yourself or anyone. If you want to test that path, do it on a Windows Bedrock client where a crash costs nothing.
Wings v2 is not covered by the lock. The 792 recipes are 18 patterns x 11 materials x the four armor pieces only. Wings v2 is a NETHERITE_CHESTPLATE, so a smithing table will trim it like any other chestplate — do not trim one and do not hand out a trimmed one.

Known warnings, not bugs

MG11 / elytra mapping — if another plugin maps custom_model_data onto minecraft:elytra, it can take Bedrock gliding away from the Wings. The log will say so.
Wisps, cloak, skirt panels, lantern and footsteps are Bedrock-only. Java players are not missing an install step; Java armor has no body geometry to hang them on. Java gets the rune trim, the visor and ETF glow instead.
A Bedrock player wearing their own cape will not see the 3D cloak. It yields deliberately.
Three low-priority wisp clearance warnings ship visible and unsuppressed. They are accepted.

If Bedrock goes wrong

The no-code containment is to pull the four armor definitions and the Wings v2 definition out of egw_showcase_models.json and restart. Bedrock players then see plain netherite armor with correct stats, and Java is untouched.