Player.RespawnLocation should be the end-all be-all for where a player spawns

[Kampfkarren (boyned)]

As a Roblox developer, it is currently too hard to use Player.RespawnLocation to customize spawn locations when arbitrary limitations are put in place.

Currently, when :LoadCharacter() is called (or a player just spawns normally), the following checks are made on RespawnLocation. If any fail, RespawnLocation will not be used.

• Is RespawnLocation a descendant of Workspace? (This one makes sense)
• Is RespawnLocation Enabled?
• Is RespawnLocation Neutral?
• If RespawnLocation is not Neutral, does it have the same TeamColor as the Player?

This behavior is shown here:

spawnlocation test.rbxl (18.6 KB)

The SpawnLocations are labeled what makes them unique. Click on the SpawnLocation to set that as your RespawnLocation, then use the LoadCharacter tool to reload. Ideally, every one of these should be able to be used as a RespawnLocation.

If Roblox is able to address your issue, how would it improve your game and/or your development experience? Please be as specific as possible.

It would make using SpawnLocations much easier. Currently, if I want to decide where a player spawns and I don’t want that SpawnLocation to be able to be used by someone else, I have to use a script to :MoveTo or :SetPrimaryPartCFrame the Character above the SpawnLocation. If these restrictions were removed, I could just set .RespawnLocation and be done with it.

And we would hopefully not get threads like these:

Setting Player.RespawnLocation and then calling Player:LoadCharacter() does not respect the RespawnLocation set

Setting Player.RespawnLocation and then calling Player:LoadCharacter() does not respect the RespawnLocation set. This is bad because then I have to manually teleport the player to the given spawn location, searching for a location to spawn, instead of letting Roblox handle it. Repo steps. Open up a new place Add a new SpawnLocation Position SpawnLocation away from origin. This is the default location to load a character. Make the SpawnLocation disabled (so we don’t auto-spawn there) Disable a…

Player.RespawnLocation woes?

Does Player.RespawnLocation even work? I have code that sets Player.RespawnLocation, I’ve verified that it’s setting the right spawn, I’ve verified it’s a valid SpawnLocation (they have the same TeamColor), but it still picks a random spawn. This is really frustrating. Does anyone have any luck in this department or is it my fault? EDIT: I’m just going to try setting the Enabled property. No clue why this doesn’t work.

[AlreadyPro (Logan)]

Just encountered this and didn’t want to make a new thread. It makes no sense that the SpawnLocation must have Neutral set to true in order to make it a valid RespawnLocation.

[orange451]

This one has bugged me for years. haha. Would be really cool if a better flow was introduced to customize respawn locations.

[ConnectNot_connect]

This would provide a lot more freedom with how we spawn the player.
Instead of spawning them and teleporting them as even teleporting on CharacterAdded can be faulty.
Making this function follow the rules of a SpawnLocation makes minimal sense and seems like an arbritrary rule.

[ultra_2033]

Again it’s just insane how Roblox ignores this for 6 years. It makes no sense how the “RespawnLocation” property of a player is arbitrated by a Roblox script out of our control. Also RespawnLocationshould be a Vector3 and not a SpawnLocation, it’s not “RespawnSpawnLocation”.

[ConnectNot_connect]

I like the idea of RespawnLocation being a Vector3, allows much more freedom than a SpawnLocation that has to be set to Neutral.

[2jammers]

there’s not much that can be done here since it’s already hardcoded into systems
it’s simply a design flaw of the legacy teams system. the next best thing is RespawnLocationVector3