PlayerAdded event does not fire for LocalScripts

[MerelyRBLX]

Reproduction steps:

Create a localscript in StarterGui with the following code:

game:GetService("Players").PlayerAdded:connect(function(player)
    print("PlayerAdded fired for " .. player.Name)
end)

game:GetService("Players").ChildAdded:connect(function(player)
    print("ChildAdded fired for " .. player.Name)
end)

1. Join an online game
2. Have another player join the game
3. Open up the developer console and notice that the ChildAdded event fired, but not PlayerAdded.

[Anaminus]

This has to do with how PlayerAdded is actually fired. It does not fire because a Player object was added to Players, but as a result of a client connecting to the server. The reason it doesn't fire on the client is simply because the procedure of receiving client connections and creating Player objects doesn't make sense on it. PlayerAdded is meant to be a server-only API in the same way Players.LocalPlayer is meant to be a client-only API.

So, this is really a question of the conditions under which PlayerAdded is fired. It's definitely not a bug, but whether you want the behavior changed as an enhancement is up to you. Whether it makes any difference is up for debate.

[matthewdean]

This has to do with how PlayerAdded is actually fired. It does not fire because a Player object was added to Players, but as a result of a client connecting to the server.

If this is the case, connecting to PlayerAdded from the client should emit a warning.

[The0neThe0nly]

This should be an enhancement.

[CoffeeFlux]

Add this as an enhancement, please!

[matthewdean]

It's probably worth noting that PlayerRemoving also doesn't fire on the client.

[matthewdean]

Now both events fire on the client.

[SNCPlay42]

Why was this reopened?

[magiccube3]

Unsure, the events do fire on the client now, no?