EverGrims WerksTHE CROSSPLAY WERKSHOP

EverGrims Werks

EGW Armory Pack

Public testing 1.1.0 · Admin guide · Paper 26.3

Seven armour sets with skirt variants and ten weapons, including the netherite-block Knight set.

Requires Paper 26.3 with Packforge 0.2.0 or newer, plus Geyser 2.12.0 or newer for Bedrock players. This pack does not require BladeFX.

A Minecraft 26.2 server keeps the 26.2 build, 1.0.2 (EGWArmoryPack-Complete-1.0.2.zip), which is in the 26.2 archive: this release's Java pack declares 26.3 only.

Unpack the Complete ZIP. Locate the named content namespace folder, the Geyser/ and Java/ folders, and the included instructions. Packs with effects also include a GrimsBladeFX/ folder.

Coming from the EGW Armored Pack 0.6.0: the Knight moved here

The Knight's armour, sword, halberd and shield moved from the EGW Armored Pack to this pack, with NEW IDs: egw_armored:knight_* became egw_armory:knight_*. The Armored Pack kept only the elementals (0.7.0) and is now the EGW Fantasy Pack (renamed at 0.8.0, namespace egw_fantasy), the one to run alongside this pack. Never run this pack with the Armored Pack 0.6.0 (it still has the old Knight and its iron-block recipes). If the server has the Armored Pack 0.6.0:

  1. Stop the server.
  2. Move to the EGW Fantasy Pack as its own INSTALL.md says ("Upgrading from 0.6.0 or older"), and make sure

the old Knight files go:

  • Packforge: check that plugins/Packforge/items/egw_armored/knight_recipes.yml is gone (delete it if not).

If you copied 0.6.0 straight into Packforge's contents/, delete plugins/Packforge/contents/egw_armored/.

  • Packforge: delete the whole plugins/Packforge/contents/egw_armored/ folder; left there, it keeps 0.6.0's

configs/knight_recipes.yml and Knight art.

  • Delete EGWArmoredPack-Models-Bedrock-0.6.0.mcpack from plugins/Geyser-Spigot/packs/.
  • Install this pack (below).
  • Knight items already handed out under the old egw_armored:knight_* IDs are not converted: they stop working

(they lose their look). Hand out the new ones, for example /pf give <player> egw_armory:knight_helmet.

  1. Change anything else that names the old IDs (a shop, a kit, a crate) to egw_armory:knight_*.

Install on Packforge (Minecraft 26.3: use this)

  1. Copy the zip's egw_armory/ folder, Geyser/packs/EGWArmoryPack-Models-Bedrock-1.1.0.mcpack and

Geyser/custom_mappings/egw_armory_models.json into plugins/Packforge/drop/.

  1. Run /pf validate (a dry run), then /pf move (the .mcpack and the mapping go to Geyser's folders, the

configs to plugins/Packforge/items/egw_armory/), then /pf zip.

  1. Restart the server (Geyser reads packs and mappings at start).

Alternative: copy the content manually

Unpack the Complete zip anywhere, then copy its folders into the plugin folders:

  1. egw_armory/ -> plugins/Packforge/contents/egw_armory/
  2. Geyser/packs/EGWArmoryPack-Models-Bedrock-1.1.0.mcpack -> plugins/Geyser-Spigot/packs/
  3. Geyser/custom_mappings/egw_armory_models.json -> plugins/Geyser-Spigot/custom_mappings/
  4. Start the server, run /pf zip, then restart it (Geyser reads packs and mappings at start).

Who can craft the Knight

Only the Knight's armour, sword, halberd and shield have recipes (in netherite blocks), and each needs the recipe permission armory: give your players' group pf.recipe.armory on Packforge (LuckPerms). Without it only ops can craft them. Everything else, the Knight's Plate Skirt included, is admin give only. The README's "Crafting" has the recipes and how to switch one off.

Dreadplate Regalia on the same server: use only a Dreadplate release made for Minecraft 26.3 (0.3.0 or newer). Dreadplate 0.2.3 is a 26.2 release and breaks on a 26.3 server, so never install 0.2.3 next to this release. Since 0.2.3, Dreadplate's armour recipes each take a soul sand, so they do not share the Knight's four armour grids. The Knight's recipes share their grid with no other EGW pack or vanilla recipe.

Updating

  • Delete the older EGWArmoryPack-Models-Bedrock-*.mcpack from plugins/Geyser-Spigot/packs/ first (an old pack

left behind can win over the new one). Bedrock caches packs by UUID + version + size.

  • Packforge: replace plugins/Packforge/contents/egw_armory/ whole (delete the old folder first). That also

replaces configs/knight_recipes.yml, so switch off again any recipe you had switched off. Packforge: put the new release through drop/ and /pf move as above; it takes back what the old release placed and the new one no longer ships.

  • From 1.0.2 (Minecraft 26.2): 1.1.0 is the same pack moved to Minecraft 26.3. Every ID, look, stat, recipe and

name is the same. The Java pack now declares 26.3 only (format 97.1), the Geyser mapping is the same file as 1.0.2's, and the Bedrock pack differs only in its version number (same UUIDs). Move the server to Paper 26.3, Geyser 2.12.0 or newer and Packforge 0.2.0 or newer first, then put 1.1.0 in as above and swap in the 1.1.0 .mcpack. Pieces and weapons already handed out keep their IDs; whether they come through Minecraft's 26.3 world upgrade unchanged is not tested yet.

  • From 1.0.1: the Knight's seven recipes take netherite blocks instead of iron blocks, in the same

Knight armour and weapons use whole netherite blocks in their documented recipes. Install the current knight_recipes.yml and reapply any recipes you disabled. Existing items keep working; Packforge can refresh their configured lore on join or container opening when items.auto-update is enabled.

  • From 1.0.0: only names changed. The Ranger and Pirate pieces got their final names (for example

egw_armory:ranger_hood_forest is now "Ranger's Shadow Hood (Forest)", egw_armory:pirateskirt_skirt the "Corsair Skirt"); every ID, look and stat is the same. Update all three parts as above (the Bedrock pack and the Geyser mapping carry the names too). Pieces already handed out keep working: Packforge renames them the next time their holder joins or opens the container (items.auto-update).

  • From the 0.1.0 test scaffold: the 60 armour IDs did not change, so pieces already handed out keep their IDs

and take the new look.

Java/ holds a standalone resource pack for a single-player look (Minecraft 26.3); the server does not need it.

Glow: the small glow accents glow on Bedrock. On Java the helmet's accents glow (light_emission, vanilla); the body's accents glow only for players running the Entity Texture Features mod (the _e layers), and show as plain paint otherwise.