[quote] If I’m reading this correctly, that means people can sign up as “ReeseMcBlox_” and “_ReeseMcBlox” in the future?
And that would count as a separate username from “ReeseMcBlox”?
I don’t think I’m ready for the numerous username impersonators. :emo-angst: [/quote]
Only one underscore in the middle.
[quote] If I’m reading this correctly, that means people can sign up as “ReeseMcBlox_” and “_ReeseMcBlox” in the future?
And that would count as a separate username from “ReeseMcBlox”?
I don’t think I’m ready for the numerous username impersonators. :emo-angst: [/quote]
Only one underscore in the middle.
[quote] If I’m reading this correctly, that means people can sign up as “ReeseMcBlox_” and “_ReeseMcBlox” in the future?
And that would count as a separate username from “ReeseMcBlox”?
I don’t think I’m ready for the numerous username impersonators. :emo-angst: [/quote]
When we discussed it yesterday, the following was brought up. Disclaimer: this wasn’t my argument but one that after sitting with it for a while convinced me impersonation won’t be a huge issue. Also a huge paraphrase.
While I do agree that it makes impersonators jobs easier, the difference won’t be noticeable. Someone could be doing it right now and I agree with the sentiment that underscores don’t make it that much easier to impersonate.
[quote] If I’m reading this correctly, that means people can sign up as “ReeseMcBlox_” and “_ReeseMcBlox” in the future?
And that would count as a separate username from “ReeseMcBlox”?
I don’t think I’m ready for the numerous username impersonators. :emo-angst: [/quote]
Only one underscore in the middle.[/quote]
Anywhere that’s not at the start or end.
[quote]
Edit: Forgot to mention… One underscore is allowed, but not as the first or last character. [/quote]
The following won’t work
hello_
_hello
But these will
h_ello
he_llo
hel_lo
hell_o
Make that 1296 more three-character usernames then.
Indeed, I’m wanting to change my username, but it’s taken by some account that hasn’t been used in 3 years.
Soon TM. But not this week.
A dash would be cool.
It could also break scripts. Underscore won’t.
local player = game.Players.ghost-leader – Error
@ghostleader Not an issue, you would never write something concrete with the player’s name in your code.
e.g. local character = workspace[plr.Name] which still works fine.
Yeah, anybody who writes them in that format is doing it wrong
local player=game.Players.1waffle1 will error.
I personally wouldn’t, but pretty sure some people would do it.
There’s a lot of conversation about breaking scripts with spaces or dashes, but honestly, when does anyone ever use a player’s actual name in a non-command line script?
I mean, basically never, right?
Its not proper to do so, so I assume never. People keep bringing this point up, and @1waffle1 keeps reminding them if is already an issue, and one that really doesn’t matter.
Nobody should ever directly index a player by their username. This goes for the player and the character. It isn’t realistic at all.
Personally, I don’t understand why people keep saying “oh we shouldn’t be able to have more characters in our usernames because you can’t do game.Players.some-guy”. If you MUST have something like that in your code, use game.Players[“some-guy”].
I was using underscores in my game for models in workspace players were WaitForChild’ing. No way could flag_model_1 be mistaken for a player name! But now it can, haha. Quenty was setting his up with an exclamation mark prefix so it was more future-proof, like !ship_model
You should be doing:
game.Players[PlayerName].CharacterAssuming that’s valid. Add any needed checks.
Actually the better thing to do in this place would be
local player = game.Players:FindFirstChild("PlayerName")
if player then
--do stuff with player
end
What if the player’s name is “CharacterAutoLoads”?