Import content from ItemsAdder, Oraxen, Nexo and CraftEngine
The Studio Importers workspace can inspect compatible source folders or ZIPs and create supported YAML definitions and pack assets. This is a conservative offline conversion, not the full set of Java importer behaviors installed on a Minecraft server.
Guided import
- Create or open a destination Studio project. For assets, make sure the project has its pack/source tree.
- Choose Importers → Choose folder or Choose ZIP. Review the detected Source plugin; Oraxen and Nexo layouts may be ambiguous. Correct the choice manually if necessary.
- Choose a safe destination namespace. The inspector lists converted YAML definitions, pack assets, warnings and blocked targets.
- Filter resources by category/ID and inspect the proposed YAML. Select only the entries you want to import. Available model/texture dependencies are selected when recognized; inspect Missing and Required but unselected notices.
- If a resource is marked Partial, review the unsupported mechanics and choose deliberately whether to proceed. A missing model is not replaced with a fabricated texture.
- Confirm Import selected files. The destination uses create-only semantics: existing YAML or assets are not overwritten.
- Reopen imported definitions, run Project Health, audit assets, export a project ZIP if needed and test on an Obsidrel Core staging server.
Supported providers and boundaries
- ItemsAdder: supported items, basic furniture and pack assets; check generated model JSON, textures and recipe references.
- Oraxen: supported item/furniture/equipment definitions; verify transforms, seats, models and unknown mechanics; incomplete families stay partial.
- Nexo: supported definitions and assets; doors and storage/container behaviors can require the server-side importer or manual review.
- CraftEngine: supported blocks, items, simple states, recipes, models and referenced furniture; advanced placement, physics, events or storage cannot be assumed equivalent.
- Blockbench: handled in the Assets workspace through a static .bbmodel preview/conversion, not as a fifth full YAML provider in this Importers selector.
When source inspection fails
Empty 0-byte files may be skipped and reported. Unsafe paths, duplicate destinations, corrupt archives, oversized uploads and file-count limits can block import. A folder and its ZIP can behave differently when a provider embeds resource packs in nested archives. Use the on-screen warnings rather than renaming unrelated providers to force success.
No external plugin is run in the browser. Neither source import nor its preview proves equivalent Minecraft behavior; compare with the appropriate Java importer or test in Core for advanced mechanics.
See Troubleshooting importer reports, Assets and Blockbench and Project Health.