Updating from Older Versions

There are two kinds of update:

• From the old Cubees: the version that ran on MCPets, with the Cudex collection book. It is a different system, so you delete it completely, then install the current packs.
• From an earlier release of the current packs (the CUBEES-RE-* and FEA_CUBEES-* packs). You swap the files and keep all saved data.

Whichever you do, back up first: stop the server and copy the whole plugins/ folder, your LuckPerms storage and the world folders.

From the old Cubees

The old Cubees and the current packs share some folder and file names, such as plugins/Nexo/items/cubees/, plugins/ItemsAdder/contents/cubees/ and the cubee-<id>.bbmodel models. Copying the new packs over the old files leaves old items, icons and models loading next to the new ones, so delete everything below before you install.

Cubees

• MCPets: in plugins/MCPets/Pets/, the Cubee ... folders (such as Cubee Magical and Cubee OniSlayer) with their cubee-<id>.yml files; in plugins/MCPets/Categories/, every cubee-category-*.yml and cubosses.yml. If MCPets runs nothing but Cubees, remove the MCPets plugin instead.
• MythicMobs: in plugins/MythicMobs/packs/, every old Cubees pack: the folders whose names begin with Cubees or Cuboss (such as Cubees-Magical, Cubees_AnimeSaga-1, Cubees-MainConfig, Cubees_Extensions, Cuboss-Frosty) and CUBEES-Gui.
• ModelEngine: in plugins/ModelEngine/blueprints/, the old Cubees model folders, such as CUBEES/ and Anime Saga 1 to Anime Saga 5. Every cubee-*, vfx-cubee-*, cuboss-* and vfx-cuboss-* model outside the new Cubees-rework/ folder must go, or it clashes with the new model of the same name.
• ItemsAdder: the whole plugins/ItemsAdder/contents/cubees/ folder. The new ItemsAdder build uses the same folder, so it must be empty before you copy the new one in.

Cudex

The Cudex ran on the Codex and ConditionalEvents plugins, opened with /cudex. The current packs replace it with the Cubees List in /cubees.

• Codex: plugins/Codex/inventory-cudex.yml and every cudex_*.yml in plugins/Codex/categories/.
• ConditionalEvents: Cudex.yml and every Cudex-p*.yml in plugins/ConditionalEvents/events/.
• Nexo: the whole plugins/Nexo/items/cubees/ folder, plugins/Nexo/glyphs/cubees/, and in plugins/Nexo/pack/assets/ the cubees and cudex folders.
• Oraxen: plugins/Oraxen/items/cubees/, plugins/Oraxen/glyphs/cubees/, and the cubees and cudex folders in plugins/Oraxen/pack/assets/. The current packs do not support Oraxen.
• ItemsAdder: covered by the contents/cubees/ folder above, which also holds the Cudex icons.

If Codex or ConditionalEvents runs nothing else on your server, remove those plugins instead. Keep PlaceholderAPI and its expansions: the current packs need PlaceholderAPI too.

Then

1. Install the current packs as described in Installation, then run /meg reload, then /mm reload, then /nexo reload (on the ItemsAdder build, /iazip instead of /nexo reload).
2. Check the console for model import errors and duplicate item warnings. Either one means an old file is still in place.

Players who owned a Cubee before can keep it. The old Cubees gave a Cubee with the permission node mcpet.cubee-<id>; the current packs give cubee.pet.use.cubee-<id>. Every Cubee has an Allow MCPets Permission setting, on by default:

• On: a player who still holds the old mcpet.cubee-<id> owns that Cubee, exactly as if they held the new permission node. It shows in colour in My Collection and can be summoned and put in a combo.
• Off: only cubee.pet.use.cubee-<id> counts, so old owners have to earn the Cubee again.

Change it per Cubee in CUBEES Settings: Cubees one by one, the Cubee, then Ability & Cubit, next to Is Available (Cubee-<id>-AllowMCPetsPermission in its collection's placeholders.yml). Keep the old permission nodes in LuckPerms while it is on. A few Cubees had other old ids: Swamp was mcpet.cubee-swamps, Wicked Widow mcpet.cubee-wicked_widow and Witching Kitty mcpet.cubee-witching_kitty.

New grants from the shop, quests, Cubiks and /cubee_give always give the new permission node. A Cubik treats an old owner as already owning that Cubee.

From an earlier release of the current packs

Player progress, quests, shop products, Cubiks, placed habitats and CUBEES Settings values live in plugins/MythicMobs/data/ and plugins/MythicMobs/spawners/, never in the packs, so an update does not touch them (see Data, Backups & Variables). The server can keep running.

1. Note anything you changed inside the packs yourself: placeholders.yml edits, and presets you added to the Import skill files.
2. Delete the old CUBEES files. Copying over the top is not enough: a file the new release renamed or dropped would stay behind and keep loading.
3. • in plugins/MythicMobs/packs/, the CUBEES-RE-* and FEA_CUBEES-* folders;
   • plugins/ModelEngine/blueprints/Cubees-rework/;
   • Nexo build: plugins/Nexo/items/cubees/, plugins/Nexo/items/cubees-features/, plugins/Nexo/glyphs/cubees-gui/, plugins/Nexo/glyphs/cubees-icons/, and in plugins/Nexo/pack/assets/ the cubees-icons, cubees-remastered and cubiks folders and the sound folders whose names begin with cubees;
   • ItemsAdder build: plugins/ItemsAdder/contents/cubees/.
3. Copy the new Base System's plugins/ folder over your server's, then each extension you run.
4. Make your placeholders.yml edits again in the new files. Do not copy old files back: keys can move or be renamed between releases. Values set in CUBEES Settings need nothing.
5. Run /meg reload, then /mm reload, then /nexo reload (on the ItemsAdder build, /iazip instead of /nexo reload), only after every file has finished copying.
6. Check: open /cubees, summon a Cubee, use its Cubit, and open CUBEES Settings to see your overrides still set. A Cubee that was out during the reload keeps its old values until it is called back out.