Installation¶

Drop EmberForge-<version>.jar into plugins/.
Start the server once. Ember Forge writes plugins/EmberForge/config.yml and builds a pack from whatever it can find.
Check the startup log:

[EmberForge] Scanned /home/container/plugins/ItemsAdder/contents: 1307 item(s).
[EmberForge] Merged base pack icons.zip (410 item entries).
[EmberForge] Pruned 41 unrenderable item entr(ies) and 0 vanilla model override(s);
             1302 entries verified renderable.
[EmberForge] Pack built: 1327 items, 2904 files, 5.3 MB, sha1 579d39e3...
[EmberForge] Ember Forge enabled — 1327 item(s) from ItemsAdder, Oraxen and Nexo packs.

That Pruned line is worth reading every time. It is the plugin telling you exactly how many entries it could not render, so a broken pack is a number in your log rather than a player report three days later.

Pointing it at your content¶

Ember Forge does not guess. Set scan-paths to the folders that hold your content packs:

scan-paths:
  - "/home/container/plugins/ItemsAdder/contents"

Then /emberforge rebuild — no restart needed.

Keeping existing items working

If you are migrating from ItemsAdder, set import-itemsadder-ids before the first build. See Migrating.