Adding a pack

Unzip a content pack into plugins/EmberForge/packs/, one folder per pack, then:

/emberforge rebuild

No restart. Ember Forge detects the format by folder shape, so you never tell it what a pack is.

packs/
  my_furniture_pack/
    configs/*.yml            <- ItemsAdder
    resourcepack/...
  another_pack/
    items/*.yml              <- Oraxen or Nexo
    pack/...

Your own items live separately, in content/ — see Items.

Both asset layouts work

Content packs ship in two different shapes and Ember Forge reads both:

<pack>/resourcepack/assets/<namespace>/models/...
<pack>/resourcepack/<namespace>/models/...

Roughly a third of real packs use the second form. Reading only the first is a common bug: the items register fine, then render as a plain base item because their assets were never copied.

Check the result

Every build prints what it took and what it refused:

[EmberForge] Scanned .../packs: 1307 item(s).
[EmberForge] Merged 1369 atlas source(s) into 1 atlas file(s).
[EmberForge] Pruned 82 unrenderable item entr(ies); 1622 entries verified renderable.
[EmberForge] Bedrock export: 742 item(s), 587 without a flat icon.

If anything was pruned, diagnose it.