As a Roblox developer, it is currently too hard to have a deep orange team. The orange brick colors aren’t very orange and look more yellow to me. I want a “255, 85, 0” kind of orange, you know?
If Roblox is able to address this issue, it would improve my development experience because I could have more variety in team colors without having to write as much custom code.
A Player.TeamColor3 and Team.TeamColor3 would do the trick. Thanks for reading!
If Team.TeamColor3 is added (much like how BaseParts have BrickColor and Color3), then Player.TeamColor3 would be resolved, wouldn’t it? This technically already exists as the Color property of BrickColor. Seems a little unnecessary to also add it.
print(Player.TeamColor.Color)
I guess there’s a case that can be made for setting the Player’s TeamColor3 to get them on a specific team, but that doesn’t feel as valid a use case when the Team property exists and you can directly assign a user to a team instance.
I had originally posted on this topic, but after some more thorough testing I realized an issue. I had said that BrickColor.new takes a Color3, however due to the nature of BrickColor, it will “round” to the nearest BrickColor, so the 255, 85, 0 ended up getting me CGA brown. Parts have a similar behavior when you change their Color, however it’s a separate property, so the BrickColor has the same behavior of “rounding”, but it didn’t make the BrickColor a CGA brown.
I would even go as far as saying deprecate Player.TeamColor, Team.TeamColor (you can set Player.Team like you said, and you don’t have to assume the color of the teams in case you forget them), and just add Team.Color, and I would even say make it a ColorSequence, if there is even any use cases for say rainbow colored teams, although extra customization wouldn’t hurt, unless there is a significant performance cost for having diffrent-colored teams/name tags.
BrickColor.Color just returns the color3 of the brickcolor. Right now if you set the color3 of a part to say, the color I mentioned in my first post and then read its brickcolor.color you won’t get the same color back. You’ll get a brown so this wouldn’t work with teams either.
I approve of this suggestion, and would like to add that SpawnLocation.TeamColor should be deprecated and replaced with SpawnLocation.Team (which could be set to a Team object). TeamColor should not be an identifier for a team!
There are older feature requests in the same vein as this.
my b, though it is slightly frustrating that those topics are so old and yet nothings been done : P
Just encountered the need for TeamColor3, please add this Roblox or just deprecate Teams in general. Yabadabadooooeeeey weewaaawoooooooo screeching noises
I actually encountered a case where I want exactly this and was going to make a feature request, and before I even got a chance to search and see if this exists, I noticed it’s been bumped already.
over 2 years later this still isn’t resolved, has anyone found an alternative?
What I’ve been doing is placing a Color3Value object inside each team object and when I make a UI item that is meant to match the player’s team color, instead of having my scripts grab Team.TeamColor.Color, I have them grab Team.Color3Value.Value and use that.
This isn’t a good solution since it doesn’t do anything to Roblox’s default UIs and requires you to make custom UI to replace Roblox’s but it’s the best I’ve been able to come up with.
My solution (run this in the Command Bar):
game:GetService("Teams")["Team"].TeamColor = BrickColor.new(255, 85, 0)
fun fact: this was actually how teams originally worked before release, as shown on the roblox blog
This will create the closest looking BrickColor to the RGB input you gave. It won’t give a Color3.
BrickColor overall should just be deprecated because Color3 is much superior.