π¦ItemsAdder β Nexo
Compared to migrating from Oraxen, ItemsAdder requires a few more manual steps. Nexo automates all it can but due to weird choices in ItemsAdder, some things wont be possible Nexo will convert all items, glyphs/font-images & resourcepacks where possible
This is unlikely to be a flawless process so do make sure you take backups and try it on a test-server first
This is a converter for ItemsAdder v4 ItemsAdder v3.x has not been tested yet and might convert with some issues Recommended to use ItemsAdder internal updating process before converting to Nexo
Put Nexo JAR in your Server/plugins
folder
Copy plugins/ItemsAdder
-> plugins/Nexo/converter/ItemsAdder
The converter
-folder does not exist by default. Simply make the new folder
Nexo will convert the content from this folder and delete it after
Any future packs you might get can then be put in here and it will all be converted again
Take a backup of all your worlds
Whilst migration should be flawless, it is still recommended to make a backup of your world-folders before swapping to Nexo There might be small oversights leading to minor loss of furniture/custom blocks
Remove ItemsAdder & LoneLibs JAR-files
Keep plugins/ItemsAdder
as this is what Nexo will convert from.
Also good to keep it as a backup in-case you need to migrate again in the future.
Start your server
Check console for conversion issues and test out items/glyphs
ResourcePack content from ItemsAdder is all bundled into Nexo/pack/external_packs/ItemsAdder/namespace/...
Items are moved into Nexo/items/itemsadder/...
Glyphs/Font Images are moved in Nexo/glyphs/itemsadder/namespace/...
Known issues
Nexo wont be able to migrate it 100% as there will be some things that is not doable across plugins. The biggest issue most will face is that furniture placed in your world that is not using Display Entities, will not be automatically converted. Nexo will try and convert configs to its format and should mean new furniture placed will look the same.
Last updated