Hello,

I've been trying to set up a command block that teleports a player to another dimension. It's running a simple command like this for example:

execute in minecraft:the_end run tp @p 0 68 0

If I run this command manually, it works fine and teleports me as expected. When I run this via a command block and trigger it, the client gets into a weird state where I'm frozen, the world is unloaded, and Y keeps flickering back and forth (as if I'm falling but the game keeps bringing me back to a previous position). The only way to get out of this state is to run a teleport command manually again.

I've tested this on vanilla 1.18.1 without any issues, but on the most recent Forge version (39.0.1), I am able to consistently reproduce this both on single player and on a multiplayer forge server running the same version.

When this happens on a server, these logs show up in the console over and over until I teleport elsewhere or disconnect:

[Server] Server thread/INFO Skipping update from removed player 'ServerPlayer['nabtz'/91310, l='ServerLevel[world]', x=-84.39, y=64.00, z=-1098.59, removed=DISCARDED]'

I've also tried using /forceload in the dimension I'm teleporting to in case this was an unloaded chunk issue, but this didn't seem to work either.

Is this an issue with the current forge version? And if it is, does anyone know the cause / is it something I can circumvent somehow?

Edited January 7, 20223 yr by nabtz
more information

post debug log

Here are the logs (now on 39.0.14)

debug.log

latest.log

I also took a screenshot of what it looks like after teleporting via command block

Edit:

After taking a look at the GH issues for forge, it looks like this has already been reported there and confirmed as a bug: https://github.com/MinecraftForge/MinecraftForge/issues/8262

Edited January 9, 20223 yr by nabtz