How to Restrict Access to Specific Worlds with Permissions

Why Restrict Worlds

On a public server you often want some worlds private, staff-only, or locked behind a rank. Multiverse-Core integrates with your permissions plugin so you can gate teleports and world access per group. The key permission nodes follow the pattern multiverse.access.<worldname> for entering a world and multiverse.teleport.self.<worldname> for teleporting yourself there. Denying multiverse.access.<worldname> blocks entry even if a player tries a portal or command.

Setting It Up

In your permissions plugin, grant multiverse.access.* to admins and only specific world nodes to regular players. For a staff-only world called admin, give the staff group multiverse.access.admin and leave it off the default group. Players without the node will be refused when they run /mv tp admin or step through a linked portal.

Test by switching to a test account in the restricted group and attempting the teleport; you should see a permission-denied message. Combine this with /mv modify <world> set enforceaccess true so Multiverse actively checks access on entry rather than only on command use. This keeps hidden builds and event worlds sealed off without needing separate servers.