Player.Name is running as Player.DisplayName

Help and Feedback Scripting Support
,
#1

Hello, so I think something broke in this new studio Update. Is anyone else having this bug?

Any time I run a script in ServerScriptService off of a remote event, when I get the player’s name it just prints as their display name.

game.ReplicatedStorage.RemoteEvent.OnServerEvent:Connect(function(Player)
print(Player.Name.." "..Player.DisplayName)
end)
#2

Or maybe I am completely oblivious and doing something wrong here. It was working perfectly fine yesterday before the update.

#3

Sadly, You`re not doing anything wrong, Due to a Recent Update, Roblox Changed the Names of our Characters from The Username to Our DisplayNames

Screenshot (84)

#4

Why would they do that… It makes 0 sense. I can only imagine the hundreds of devs wondering why their script broke over this.

#5

Not Sure, i have no idea.

Same,
Check out #development-discussion
There are posts about it:

https://devforum.roblox.com/t/the-recent-display-name-update/2068311

https://devforum.roblox.com/t/horrible-news-for-lots-of-games/2068339

#6

I guess now the only way to get the original username is by userid.

1 Like
#7

Pretty much, People are hoping this is a Bug, but I doubt that.

As stated by some of the Posts and @Redluo , Use GetNameFromUserIdAsync

game.Players:GetNameFromUserIdAsync(Player.UserId)
1 Like
#8

I would say it’s most likely a bug since display name already exist as a property for the player instance so it doesn’t make any sense to make the username the same as the display name

2 Likes
#9

True, But the thing is: Roblox makes all sorts of Weird Updates, so, it’s only a possibility,

I guess its only a matter of time…

1 Like
#10

It is weird how in Studio on the player tab it still shows the proper name, but when you load into the game it breaks. I think it is more so a bug than a new thing because Roblox already has a Display.Name feature

2 Likes
#11

Here are 3 Possibilities I can think of:

  1. This is a Bug (Stated by: @black1shadow1048 and Other People from Other Posts)
    Maybe it was a accident?

  2. Privacy Concerns
    Maybe somebody complained to ROBLOX for threatened to sue them, this I Highly Doubt, but who knows.

  3. Horrible Update
    Very Likely, Only time will tell

#12

Thankfully this is a bug, no need to change anything in your game!

2 Likes
#13

This is a bug and was already reported. Logout and login back to studio to fix it.

#14