Skip to content

Migrating from ItemsAdder

Ember Forge is designed to take over from ItemsAdder without reissuing items players already own.

Keep existing items rendering

An item's appearance comes from its custom-model-data number. If those numbers change, every item already in a chest or an ender chest turns into something else. Point Ember Forge at ItemsAdder's id cache and it adopts the existing assignments:

import-itemsadder-ids: "/home/container/plugins/ItemsAdder/storage/items_ids_cache.yml"
model-data-start: 20000
reserved-model-data:
  - "1000-4999"

On startup you will see:

[EmberForge] Adopted 2662 ItemsAdder id assignment(s), so legacy items keep rendering.

model-data-start is where new ids begin, chosen to sit above the imported range. reserved-model-data blocks out ranges you use elsewhere — GUI icons, another plugin — so Ember Forge never hands one out.

You can uninstall ItemsAdder

Ember Forge reads contents/, not the plugin. Once ids are imported you can remove the ItemsAdder jar and keep the folder.

Do not keep ItemsAdder's generated.zip as a base pack

A leftover output/generated.zip is a frozen snapshot. If it was built while ItemsAdder's short_texture_references was on, its models point at an ia:NNN texture namespace that only exists when texture protection is enabled. With ItemsAdder gone nothing regenerates it, and those references are dead forever.

Ember Forge prunes such entries rather than shipping them, but you lose the items. Read the content folder instead — it has real textures:

include-packs:
  - "include/icons.zip"      # your own additions
scan-paths:
  - "/home/container/plugins/ItemsAdder/contents"

Checklist

  • [x] import-itemsadder-ids set before the first build
  • [x] scan-paths points at contents/
  • [x] generated.zip not in include-packs
  • [x] Pruned 0 unrenderable in the log, or you know why not