mojira.dev
MC-25130

/spawnpoint not working

i'm making a adventure map and i have a command block that is supposed to set ur spawnpoint at the location u get teleported to.. there r 3 command blocks that activate.. first the one that teleports u followed by a repeater for a .1 second delay and then redstone.. on the one side of the redstone is a repeater with a .4 second delay and to the /spawnpoint command block and the other side goes to a command block with a /say command.. the one that goes to the /spawnpoint command block isn't working for some reason since the 1.6.2 update.. when that section of the map was done in 1.6.1 it was working when we were doing tests.. on the block i have /spawnpoint @a x y z.. i have the @a so all players spawns will be set.. but when u teleport into the area and die it doesn't spawn in that same area as desired... i hope this isn't too confusing.. i've looked online and did research and nothing i've tried works

Linked issues

Attachments

Comments 10

This ticket is very difficult to comprehend, please attach screenshots of the command blocks you use and of the complete setup.

first picture is how i have it set up.. command block in the back is the one that teleports the playerand a repeater set to .1 seconds.. the one on the left is the one that has "/spawnpoint @a" set to it and has a repeater set to .4 seconds.. i've tried it with cords but it doesn't seem to make a difference the one on the right is just a /saw command that tells the player the objective.. the bottom picture is just what the top pictures left command block has in it

Can you take a screenshot of the place you are teleporting them to before setting their spawn? Does MC-141 describe your issue?

this is the area.. the diamond block is where they spawn at.. and that article is close to how i have it.. they don't drop on a pressure plate or tripwire.. my idea was the spawnpoint command block would trigger after the teleport one thinking that once they r spawned in then the spawnpoint one would trigger setting it.. and in 1.6.1 it did work and we tested it multiple times.. the idea for the whole thing was when u get teleported to the area if u die there u keep respawning there until u complete the level

see.. it's weird explaining it without giving a walkthrough of it.. the level is set up where when u teleport in it starts a timer that after about every 30 seconds a new wave of enemies spawn in and u need to get a item and place it into a hopper setup to spawn back and it also stops the timer and the spawns and it resets ur spawn to the main area again instead of the level.. and it worked great in 1.6.1 but when we tested it the other night our spawn is stuck in the main area and won't change.. and i've checked all the redstone and repeaters and everything is facing right.. there's no possible way the other command block that has /spawnpoint on it can trigger from teleporting into the level

so i was messing with this today and i made a strange discovery.. so with the setup i had with the 3 command blocks i destroyed the spawnpoint one and put it down again.. but this time when i put the /spawnpoint @a command in i was facing the side and clicked on the same side as the redstone signal was going into it.. and now it works.. originally when i put the block down and the command in i was facing towards the wall.. i did some other testing with that theory this way with just a redstone current with buttons on all 4 sides with the same /spawnpoint @a command and all 4 sides work.. so i don't know if the bug comes from the combination of stuff i had where it had to be a specific side where it would activate or if it was just being strange.. but something is weird with the command blocks with the direction u place them and activate them that i think needs a closer look

correction.. it's not working again.. it works whenever it feels like it.. the command seems to be unstable

Read the comments in MC-29354:

  • Do not use decimals at the coordinates

  • Use /spawnpoint before /tp

Is this still a concern in the latest Minecraft version 13w48b? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

It still affects. Whenever I use "/spawnpoint @p ~ ~-5 ~" with a command block and I die, it drops out a message - "Your bed was missing or obstructed"

Chris Forry

(Unassigned)

Unconfirmed

Minecraft 1.6.2

Retrieved