EverGrims WerksTHE CROSSPLAY WERKSHOP

EverGrims Werks

EGW Fantasy Pack

Public testing 0.10.0 · Admin guide · Paper 26.3

The elemental weapons and armour sets, the Dozer and Paladin frames and the Cthulhu set. Works on its own; BladeFX adds the visuals.

Minecraft 26.3. Needs Paper 26.3 and Geyser 2.12.0 or newer. The Java pack is resource pack format 97 to 97.1, for 26.3 only. For Minecraft 26.2 use 0.9.0, the last 26.2 build: it is in the 26.2 archive (EGWFantasyPack-Complete-0.9.0.zip).

Use Packforge 0.2.0 or newer as the content host. BladeFX adds the configured effects and requires Packforge.

GrimsBladeFX 1.0.0 or newer (its 26.3 build) for the weapons' on-hit effects, the Cthulhu set bonus and the R'lyeh Feelerblade's madness (Install, the GrimsBladeFX step). The file is 0.9.0's, unchanged, and loads on GrimsBladeFX 1.0.0 with 0 problems. On 26.2 it was checked on GrimsBladeFX 0.7.1 to 0.9.0.

Upgrading from 0.9.0

Use Paper 26.3, Geyser 2.12.0 or newer and Packforge 0.2.0 or newer. Add GrimsBladeFX 1.0.0 or newer for the configured effects. Item IDs stay the same across this update. Then:

  1. Stop the server.
  2. From plugins/Geyser-Spigot/packs/ delete EGWFantasyPack-Models-Bedrock-0.9.0.mcpack. The 0.10.0 one is the

same Bedrock pack (same UUID) in a newer version: left there, the two would clash.

  1. Install 0.10.0 as below, starting with the server stopped: each Install list says when to start it. The

content folder, the mapping and the GrimsBladeFX file have not changed, so an edited plugins/GrimsBladeFX/effects/egw_fantasy.yml can stay as it is.

  1. Bedrock clients download the new pack version on their next join.

For older releases, put the current content folder, Bedrock pack and mappings through drop/, /pf move and /pf zip. Remove only the old namespaces named below from Packforge’s content and item folders so duplicate definitions do not remain.

Upgrading from 0.8.0

Items already handed out keep working: the IDs are the same. Replace the pack's files:

  1. Stop the server.
  2. Delete plugins/Packforge/contents/egw_fantasy/, then copy in the new egw_fantasy/ (Install,

Use the manual installation steps below.

  1. From plugins/Geyser-Spigot/packs/ delete EGWFantasyPack-Models-Bedrock-0.8.0.mcpack, then copy in the

Use the current 0.10.0 Bedrock pack. Remove the previous copy with the same UUID so clients receive the updated pack.

  1. Copy the new Geyser/custom_mappings/*.json over the old ones (Install, manual installation step 3).
  2. Copy the new GrimsBladeFX/effects/egw_fantasy.yml over the old one (Install, manual installation step 4). If you had

edited the old one, redo those edits in the new file: it is the 0.8.0 file plus the Cthulhu entries.

  1. Start the server, run /pf zip, then restart it. Bedrock clients download the new pack version on their next join.
  2. Give the new items: /pf give <player> egw_fantasy:cthulhu_hide (and _visage, _leggings, _boots,

egw_fantasy:cthulhu_feelerblade).

Upgrading from 0.7.0

0.8.0 renamed the pack: the EGW Armored Pack is now the EGW Fantasy Pack, and its namespace egw_armored is now egw_fantasy. Every egw_armored:<id> is now egw_fantasy:<id>, the same names after the colon (for example egw_armored:emberforge_greatsword is now egw_fantasy:emberforge_greatsword). Nothing was public, so only two things on this server used the old IDs: items already handed out (step 5) and the EGW Custom Shops for GrimsShop (step 6).

  1. Stop the server.
  2. Remove the obsolete egw_armored namespace from Packforge before installing its replacement, so old definitions do not remain.

items next to the new ones.

  1. From plugins/Geyser-Spigot/packs/ delete EGWArmoredPack-Models-Bedrock-0.7.0.mcpack (and any other

EGWArmoredPack-Models-Bedrock-*.mcpack). The new Bedrock pack is a different pack (new name, new UUID), so it does not replace the old one: left there, both would load.

  1. From plugins/Geyser-Spigot/custom_mappings/ delete egw_armored_models.json.
  2. Old items are not converted. An egw_armored item already handed out keeps its netherite stats but loses its

look, and GrimsBladeFX's own plugins/GrimsBladeFX/effects/egw_armored.yml still gives an old weapon its particles and its strike, on a 15 s wait apart from the new weapons' (an old and a new weapon make two strikes per 15 s). Take old items back. Deleting that file does not last: GrimsBladeFX writes it again. To switch it off, set enabled: false under its info: on GrimsBladeFX 0.8.1 or newer, which keeps an edited file (edited on 0.8.0 or older, it makes 0.8.1 and newer log an effects.upgrade_skipped warning at every start).

  1. GrimsShop: the EGW Custom Shops set built for the 0.7.0 pack lists the Emberforge, Rimecoil, Viperglass and

Livewire items as egw_armored IDs, so after this upgrade those 20 items stay hidden, with one warning each, until you install a Custom Shops set built for the EGW Fantasy Pack (it lists egw_fantasy IDs). The 0.7.0 set has none of the mecha items either.

  1. Install 0.10.0 as below, including the GrimsBladeFX file (manual installation step 4, Packforge step 3).
  2. Give the new items: /pf give <player> egw_fantasy:<id>.

Upgrading from 0.6.0 or older (EGW Elemental Blades, or the Knight)

Do the steps above, and also: delete plugins/Packforge/contents/egw_blades/ if it is there, every EGWElementalBlades-Models-Bedrock-.mcpack in plugins/Geyser-Spigot/packs/, and egw_blades_models.json in plugins/Geyser-Spigot/custom_mappings/. The Knight set (0.6.0) is in the EGW Armory Pack now, as egw_armory:knight_. If plugins/GrimsBladeFX/config.yml still lists egw_blades item models (a GrimsBladeFX older than 0.6.0), delete it so GrimsBladeFX writes a fresh one.

Install

Unpack the Complete zip anywhere (its folders are at the zip root).

On Packforge (0.2.0 or newer):

  1. Copy the zip's egw_fantasy/ folder, Geyser/packs/EGWFantasyPack-Models-Bedrock-0.10.0.mcpack

and Geyser/custom_mappings/*.json into plugins/Packforge/drop/ (the server can be stopped or running).

  1. Start the server if it is stopped, then 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_fantasy/), then /pf zip.

  1. Copy GrimsBladeFX/effects/egw_fantasy.yml into plugins/GrimsBladeFX/effects/ (GrimsBladeFX 1.0.0 or newer;

The effects file is installed separately in GrimsBladeFX’s effects/ folder.

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

For manual installation in Packforge:

  1. egw_fantasy/ -> plugins/Packforge/contents/egw_fantasy/
  2. Geyser/packs/EGWFantasyPack-Models-Bedrock-0.10.0.mcpack -> plugins/Geyser-Spigot/packs/
  3. Geyser/custom_mappings/*.json -> plugins/Geyser-Spigot/custom_mappings/
  4. GrimsBladeFX/effects/egw_fantasy.yml -> plugins/GrimsBladeFX/effects/ (GrimsBladeFX 1.0.0 or newer): every

weapon's on-hit element, on charged swings only, then one shared 15 s wait per player; the Cthulhu set bonus and the R'lyeh Feelerblade's madness (players only, its own 15 s wait). GrimsBladeFX up to 1.0.0 never writes this file. A later GrimsBladeFX that bundles it upgrades only an unedited copy (keeping a .bak) and never overwrites an edited one. To change a value, edit it and run /gbladefx reload (/gbladefx validate checks it first).

  1. Start the server, run /pf zip, then restart it (Geyser reads packs and mappings at start).

Give items with /pf give <player> egw_fantasy:<id>.

On a fresh install Bedrock clients download the pack on first join. Upgrading from 0.9.0 or 0.8.0, it is the same pack (same UUID) in a newer version, so they download it again on their next join.

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