The Bug:
Using the "/spectate" command across dimensions teleports spectators to the target's position without actually spectating them.
When spectating another player via /spectate <target> <player> the results are very inconsistent and sometimes the player in spectator mode gets stuck. Other times it works just fine.
What I expected to happen was...:
It should spectate smoothly and view what the other player is doing
What actually happened was...:
The view of the spectator get "stuck" at the original position of the player and it doesnt follow the view. Its easier to reproduce if they are in two different dimensions but it also happens within the same dimension.
Steps to Reproduce:
1. Have one player in the nether
2. Have a second player in the overworld in spectator mode
3. Run the command /spectate <player in 1> <player in 2>
4. Spectator gets stuck in the original position of the player in 1
Linked issues
Attachments
Comments 3
@Avoma this also happens within the same dimension, but its very inconsistent, but reproduceable if you try it about 10 times.
This is confirmed in 1.20.4, and I did some math to figure out exactly how this issue is reproduced.
It appears that any distance greater than or equal to 32 blocks plus your render distance, shown with the equation 16x + 32 will produce this issue. (Where x is your render distance in chunks). An exception to this is in cross dimensional cases, in which the issue will appear every time. In regards to @RealBaconEater 's comment, there doesn't seem to be any random chance in my testing.
Furthermore, maybe related, the /spectate commands seems to not function entirely, at any distance, when placed in a command block. Example shown below. The UUID provided here is the UUID of a cow.
/execute as Loudbook run spectate 0e669c75-4912-48e3-80c6-0df59556d632
Confirmed. I've provided a narrated video of this problem for a better understanding of the issue here, and have adjusted this report's title to more be fitting.
[media]