Multiverse for Fabric: Create, Clone, and Manage Dimensions

Multiverse gives operators a /multiverse command tree for creating, teleporting to, cloning, and deleting dimensions at runtime. It is designed for Fabric servers and singleplayer worlds; the current creator metadata marks the server as required and the client as unsupported.

Current Multiverse release

The creator sources were checked on August 24, 2026. The broad project page lists several Minecraft branches, so match your server to a specific release page.

Prepare before changing dimensions

• Stop experimental work on the live world and make a restorable backup of the entire server directory.
• Record the exact Minecraft, Fabric Loader, Multiverse, Fabric API, and Fabric Language Kotlin versions.
• Run /save-all before a clone; the creator explicitly recommends this step.
• Test create, teleport, clone, restart, and delete behavior on a staging copy first.

A copied folder is not a verified backup until you have restored it and confirmed that the server starts with the same mod set.

Create a dimension

/multiverse create from <dimension-type> <dimension-id> <seed?> <has-custom-gamerules?> <has-custom-tickrate?>
/multiverse create vanilla <overworld> <nether> <end> <seed?>

The creator documents built-in dimension types including multiverse:void and multiverse:white_glass. Use namespaced IDs such as minebrush:test_void so ownership and storage paths remain clear. The vanilla route creates a linked overworld, Nether, and End set rather than one isolated dimension.

Teleport and command access

/multiverse teleport <dimension> <position?> <rotation?>

Operators can use the command tree by default. With a compatible permission mod, the creator documents separate nodes for the base command plus create, clone, delete, and teleport. Give destructive permissions only to staff who also have access to backups and the change log.

Clone without freezing the production server

/multiverse clone <from-dimension> <to-dimension> <has-custom-tickrate?> <region-from?> <region-to?>

Run /save-all first. The creator warns that cloning a whole dimension copies all region files and can hang the server. For a large world, schedule downtime and test the region-limited form on staging before attempting a full clone.

Delete only with a tested restore path

/multiverse delete <dimension>

The normal command requires confirmation. A force option bypasses that protection, so it should not appear in routine runbooks. Treat deletion as irreversible from inside the mod: take a backup, confirm that no players are inside the target dimension, record its namespaced ID, and verify the destination before approving the prompt.

Where Multiverse stores data

The creator documents generated dimensions under world/dimensions/<namespace>/<path>. Custom Multiverse definitions use data/<namespace>/multiverse/dimension/<path>.json, while dimension types use data/<namespace>/dimension_type/<path>.json. Preserve those namespaced paths in backups and datapacks; changing an ID changes where operators expect to find its data.

Creator sources and version selection

Open Multiverse versions on Modrinth. Choose the release whose Minecraft version matches the server, then read its dependency list before scheduling the change. MineBrush does not mirror or redistribute the JAR in this article.

• Multiverse project and command documentation
• Multiverse 0.5.1+26.2 release page
• Creator source repository