If you specifie the coordinates of an execute command, these are ignored.
So, Let's say:
The Player's current position is at 100 150 200.
A command block runs the following command:
"/execute Player 500 200 -500 spawnpoint Player"
It should be setting the spawnpoint at 500 200 -500, but it's setting it at 100 150 200.
By the way, "/execute Player ~ ~ ~ spawnpoint" does not work at all.
Linked issues
duplicates 1
Comments 3
Are you sure, it's a duplicate?
The core point is that when you specifie the coordinates by saying where to execute and not where to set the spawnpoint, it does not work as it's supposed to be.
/execute <Player> <absolute coordinates> spawnpoint ~ ~ ~
sets the spawn point at <Player>'s current position.
Either this ticket is a duplicate or invalid, because not a bug
You've described it already:
/execute <Player> <absolute coordinates> spawnpoint ~ ~ ~
sets the spawn point at <Player>'s current position.
That's the expected behaviour of spawnpoint without arguments.
Use
/execute Player ~ ~ ~ spawnpoint Player 500 200 -500Remember that the coordinates of execute are only reference coordinates for relative coordinates in the executed command. Without giving coordinates in the executed command the coordinates of the execute command are not used.
That
/execute Player ~ ~ ~ spawnpoint Player 500 200 -500is the same as
/execute Player 500 200 -500 spawnpoint Player ~ ~ ~and the same as
/execute Player 400 100 -600 spawnpoint Player ~100 ~100 ~100
Dupe of MC-51613