Basic Usage
Multiverse-NetherPortals gives each Multiverse world its own vanilla-style Nether and End portal destinations. It can select those destinations automatically from world names, or you can explicitly link portals to any Multiverse world.
Quick start
Create the dimension worlds for your main world. For a world named
survival, run:/mv create survival_nether nether /mv create survival_the_end the_endtextBuild and light a normal Nether portal in
survival. It will automatically lead tosurvival_nether.Build portals normally in the linked worlds. Automatic links also work in reverse, so a Nether portal in
survival_netherleads back tosurvival.Run
/mvnp listto check the links NetherPortals will use.
Multiverse-NetherPortals does not create destination worlds when a portal is used. Create or import the worlds with Multiverse-Core first. If no explicit or automatic destination exists, the portal does nothing; with bounceback enabled, players are pushed out of an unusable Nether portal.
Automatic linking
When a portal has no explicit link, NetherPortals derives its destination from the world's name. With the default configuration:
| Portal used in | Portal type | Automatic destination |
|---|---|---|
X | Nether | X_nether |
X_nether | Nether | X |
X | End | X_the_end |
X_the_end | End | X |
The destination must exist and be known to Multiverse. You can change the default _nether and _the_end naming rules with portal-auto-link-when .
Customizing links
Use /mvnp link when a destination does not follow the automatic naming convention, or when you want a portal type to lead somewhere else entirely.
For example, this sends Nether portals in survival to resource_nether:
/mvnp link nether survival resource_netherExplicit links are directional. The command above changes portals in survival, but does not change portals in resource_nether. Add --bidirectional (or -b) to create both directions at once:
/mvnp link nether survival resource_nether --bidirectionalThe same commands work for End portals:
/mvnp link end survival events_end --bidirectionalLinks may connect worlds of any environment. Portal creation, coordinate scaling, and other NetherPortals behavior still apply based on the portal type and the source and destination worlds.
To remove an explicit link and return to automatic linking, run:
/mvnp unlink nether survivalIf the pair was linked in both directions, remove both links together:
/mvnp unlink nether survival --bidirectionalSee the command reference for all syntax and flag behavior.
Disabling portals in one world
Link a world to itself to disable one portal type in that world:
/mvnp link nether minigames minigamesRe-enable the portals by removing that self-link:
/mvnp unlink nether minigamesWorld scaling
World scaling controls how coordinates are converted when an entity travels between linked worlds. Each Multiverse world has a positive scale value. The destination coordinates are calculated as:
destination coordinate = source coordinate × (source scale / destination scale)For the standard Overworld-to-Nether relationship, the Overworld has a scale of 1 and the Nether has a scale of 8. Entering a Nether portal at X/Z 800 in the Overworld therefore targets X/Z 100 in the Nether:
800 × (1 / 8) = 100Travelling back reverses the calculation:
100 × (8 / 1) = 800Multiverse-Core assigns environment-appropriate defaults to newly managed worlds. To inspect or change a world's scale, use its scale world property :
/mv modify <world> set scale <value>Changing scale affects where portals search for or create their counterparts; it does not move existing portals or chunks.