When you put the command "/setworldspawn" into a command block,
it shows "[*::*] You must specify which player you wish to perform this action on." instead of setting the world spawn.
When you perform this command as a player, it works.
Also putting "/setworldspawn ~ ~ ~" into a command block works.
Attachments
Comments 12
I don't really understand, what you mean, I attached some screenshots of it.
They show the situation before and after activating.
I just want to mention, that I am German.
As well I want to add, that the compass points onto the right block.
Edit: Oh, I saw, what you mean, I was about to write "command block" instead of "comparator", sorry.
Why "Awaiting response"?
The syntax for setworldspawn is "/setworldspawn [x] [y] [z]".
The bug is probably that you can use "/setworldspawn" to set the world spawn to your current position. But apparently when you perform this command in a command block, it thinks it needs a player instead of using its own coordinates
It's awaiting response because the original summary was
setworldspawn in comparator bug
and my question
What role plays the Comparator ?
was unanswered.
Anyway, this is no bug. See http://minecraft-de.gamepedia.com/Befehl/setworldspawn
... Im Befehlsblock müssen die Koordinaten immer angegeben werden. ...
setworldspawn without parameters set the worldspawn to the position of the current player.
A command block is no player.
If no coordinates are specified, it defaults to the coordinates of the object executing the command. It works perfectly well with setblock and summon, why not setworldspawn?
What role plays the Comparator ?