Character Teleporting Issues

[RomeoEDD]

– ok ill come now #30characters

[ShadowOfCrimson]

Between teleporting player1 and player2, I went against the forum I was referencing and added a wait() and now it teleports both player 1 and 2 successfully… I have no idea how to explain this other than a bug in Roblox’s system. Can anyone else replicate my bug using this code?

local p1 = game.Players:FindFirstChild("Player1") or game.Players.PlayerAdded:Wait()

local p2 = game.Players:FindFirstChild("Player2") or game.Players.PlayerAdded:Wait()

local Character1 = p1.Character or p1.CharacterAdded:Wait()

local Character2 = p2.Character or p2.CharacterAdded:Wait()

Character1:SetPrimaryPartCFrame( workspace.A.CFrame)

--wait() --Try with the wait off and with it on to see what I am trying to explain.

Character2:SetPrimaryPartCFrame( workspace.B.CFrame)

The only resources you need:
-A place
-Two parts in workspace: “A” and “B”
-My script sample
-Run the studio in 2 player server mode and watch the results

[ShadowOfCrimson]

Solution per the reply to my bug request:

@XAXA

According to a post by an engineer, this is the sequence in which events/etc. happen when the character is spawned:

    Current Ordering

1.  Call LoadCharacter 
2.  Player.Character is set 
3.  CharacterAdded fires -- You're teleporting the character after this...
4.  Player.Character changed
5.  Character appearance is initialized
6.  CharacterAppearanceLoaded fires  
7.  Character parented to DataModel -- But it doesn't get parented until this point!
8.  Character rig built/character scaled
9.  Character is cframed to spawn location -- The CFrame is set at this point, which will override whatever you previously set it to.
10. LoadCharacter returns

The new ordering, which hasn’t been implemented, would change the ordering around like so. This new order would have eliminated your issues.:

    New Ordering

1.  Call LoadCharacter 
2.  Character appearance is initialized 
3.  Character rig built/character scaled
4.  Character is cframed to spawn location   
5.  Player.Character is set
6.  Player.Character changed event  
7.  Character parented to DataModel -- The character is parented here...
8.  CharacterAdded fires  -- And CharacterAdded fires here. Your script would have worked in this case!
9.  CharacterAppearanceLoaded fires 
10. LoadCharacter returns 

It’s evident that engineers are at least aware that parenting the Character before CharacterAdded fires is a bit problematic.

For now, the best solution would be to hold off on teleporting characters until after they’re parented to the DataModel.