Type of bug

Exploit, Other unexpected behaviour

/ess dump all output

https://essentialsx.net/dump.html?id=df7aad484d8c4fe2b2ac9fc21395c9df

Error log (if applicable)

No response

Bug description

when the player is in the"world1" and wants this tp in the"world2" using the command
/execute in minecraft:world2 run tp @s 0 90 0
or even with /minecraft:execute in minecraft:world2 run tp @s 0 90 0
he teleports to the correct coordinates, but every time in the “world1” instead of “world2”

Steps to reproduce

1. Be in a world
2. try to teleport to another world using execute in minecraft:world2 run tp @s 0 90 0
   3.cry because it didn't work

Expected behaviour

1. Be in a world
2. use the command execute in minecraft:world2 run tp @s 0 90 0
3. being teleported to the world2 at 0 90 0

Actual behaviour

the player is teleported to the correct coordinates, but still in the world in which he is already

Additional Information

i tried to remove others plugin and even multiverse core, but that happen only if essential is in the plugins folder.
i was using the same config on paper 1.20.4 last week and i didn't have this issue at all

Have you tried using /execute in minecraft:world2 run minecraft:tp @s 0 90 0 ? It seems like when you use tp instead of minecraft:tp, it is using Essentials tp command which ignores where it is executed instead of Minecraft's.

As the above user pointed out, either format the tp command to work with Essentials' tp command or prefix the tp command with minecraft: to use the built in tp command.

i have to precise i'm using this inside the config.yml of essentials :

disabled-commands:
  - tp

So normally, I don’t need to use minecraft:tp with my config, but for version 1.21+, Essentials seems to conflict with the vanilla Minecraft tp command.

I might need to rename this issue. The command /execute in minecraft:world2 run minecraft:tp @s 0 90 0 works, but with tp in the disabled commands, it theoretically shouldn’t require the minecraft: prefix. However, in practice, it does.

As the above user pointed out, either format the tp command to work with Essentials' tp command or prefix the tp command with minecraft: to use the built in tp command.

Same problem. Until I updated, tp in /execute worked without having to attribute minecraft:. I think it was the correct behavior before - because of the shortcut F3+C.
Edit: disabling the tp command works for me. purpur 1.20.6, latest essentials.

That sounds like an issue in Spigot or Paper - commands that are removed from the command map should resolve the same way in /execute as they do in the chat bar.