issue with players going from nether to overworld

[trigg-er]

I am having an issue where whenever someone without operator permissions tries to exit the nether or end back to the overworld through any means (other than dying) there is an error message (inside the game but nothing in the console) "You don't have access to world name." I have tried everything i can, I set world-teleport-permission to false, essentials.worlds.*, or essentials.worlds.name, essentials.worlds.name_nether or essentials.worlds.name_the_nether. i do not have anything like the mv plugin nor do i have any plugin blocking access to any dimensions. does anyone know what i need to do to fix this error?

[DYNOSuprovo]

The error message "You don't have access to <world name>" is not generated by EssentialsX.

In EssentialsX:

• The internal world permission message is worded differently: "You do not have permission to teleport to that world." (teleportWorldDenied).
• Furthermore, world-teleport-permissions in config.yml only applies to Essentials commands (/tp, /back, /world, /tpa), and never intercepts vanilla Nether/End portal transitions.

Because you are seeing this message during portal travel and only for non-OP players, another plugin on your server is canceling the PlayerPortalEvent or PlayerTeleportEvent.

---

How to Find the Exact Plugin & Permission Instantly

If you use LuckPerms (or any modern permissions manager), you can use the real-time verbose logger to catch the exact permission node and plugin responsible:

1. In game (or from console), run:

   /lp verbose on <player_username>
   

2. Have that non-OP player step into the Nether/End portal to trigger the "You don't have access to..." message.
3. Check the console or chat output. LuckPerms will log every single permission check in real-time, showing:
   • The exact permission node being evaluated (e.g. multiverse.access.<world>, worldguard.entry.<world>, etc.)
   • The plugin making the check
   • Whether the check evaluated to true or false
4. Once you see the permission node, run:

   /lp verbose off
   

---

Common Culprits to Check

If you aren't using LuckPerms verbose:

• Multiverse / MultiWorld / MyWorlds: If any world management plugin is installed (or built into your server jar), portal travel checks multiverse.access.<world> or <plugin>.access.<world>.
• WorldGuard: Check if a __global__ region or portal region has an entry or passthrough flag set to deny.
• Server Spigot/Paper bukkit.yml: Ensure world names in bukkit.yml under world-settings match your folder names.
• BungeeCord / Velocity / Dimension synchronization plugins: If running a proxy network, server-switching or dimensional forwarding plugins often enforce dimension travel permissions.

Running /lp verbose on while the player steps through the portal will tell you the exact plugin in seconds!

---

If this helps you track down the responsible plugin, please feel free to mark this as the accepted answer so others managing Spigot/Paper servers can find the troubleshooting steps!

[trigg-er]

It worked, thank you so much for the help!