Why won't players spawn on only one spawn and not their team spawns?

I’ve been going insane trying to fix this, and this is my last option. I have been trying to get teams to spawn at their spawns instead of one single spawn. All the teams and spawn team colors are set properly yet still doesn’t work, however when you reset, you get sent to your spawn. Can anyone tell me how to solve it?

The place where I spawn
Script

My team color
Script2

My spawn color
script3

3 Likes

Are you sure that you have your teams set up completely in the “Teams” service?
If not, run the code game:GetService('Teams') in your command line to spawn it into the explorer and add your teams to it.

image

As shown here, it works for me:

I tried it, still doesn’t seem to work.

Do you have a neutral spawner somewhere? If so, you should remove that.

1 Like

I just checked, I have no neutral spawners.

1 Like

and your spawn team colors match up with your team colors in Teams?

1 Like

Yes, I have a picture of my team and spawn on the post.

1 Like

Actually, your post shows that you have a different color for your team service teams.

1 Like

I have a picture of my team and where I should spawn, but I end up spawning where the white team should spawn.

It might help just to start over and make sure everything is 100% correct.
Remove all spawners and teams and try again.
Make sure no spawners are set to neutral and make sure that no scripts are overriding any of this. I’m not really sure what else to tell you as this works just fine for me.

1 Like

Ok, thanks, I appreciate you trying to help me.

1 Like

You need to make sure your teams are in the Teams Service Folder and that the colour of the team is the exact same colour as the spawn. You would also need to respawn if its not auto assignable.

Example of assigning:

game.Players.PlayerAdded:Connect(function(player)
    player.Team = game.Teams["Team Name Case Sensitive"]
    player:LoadCharacter()
1 Like

I have the same problem
Is my spawn not configured correctly?

2 Likes

Good time to bump this, but exact same bug.