As a developer, I find it quite frustrating at times when creating teams for my games and having to base the spawn systems and teams by their BrickColor value. I feel as if this method has been neglected fixing, despite the fact it should have been deprecated years ago.
I am proposing a new solution for a game-based setting that would allow developers to utilize Color3 values for their teams, especially for games that work with large amounts of them, whether for obby spawning simplicity or otherwise.
I will note that BrickColor Teams should absolutely NOT be removed from the current game engine. This would lead to hundreds of thousands of older, outdated and unmaintained experiences to be unplayable. I however do believe that a creator should be able to select if they wish to utilize BrickColor or Color3 for their team systems, in a format selectable through the properties page.
This issue, although it is not critical by any means, could vastly help newer developers and allow for games that utilize level based progression to properly adjust their color scaling, and allow for the development of unique, customizable teams. This would especially benefit from games that have a “create team” command, allowing players to fully customize how they wish their team to be depicted.
I would like to also propose possible additions to the leaderboard system, especially with the UI structuring, to allow creators to add badges and images to the leaderboard without having to custom design their own. I think the ability to add an icon to certain teams or players, like the Premium badge, could allow further, easier, and simpler advancements in leaderboard scripting and configuration. This could be utilized for developer flair, badge display, and numerous other examples.
Team Identifier : string
Team DisplayName : string (can be the same on different teams)
Team Color : Color3
(the name of team instance isnt the team name or identifier it can be anything)
and if u put a uigradient inside a team the team color will be the gradient
seems simple enough to implement tho it all lies in the hands of roblox staff
ah yes what a wonderful idea, next we should deprecate decals too, maybe baseparts and models while we are at it? who even needs players deprecate that too!
What do Teams do? They are a legacy feature, designed for a bygone time. All of their problems, like their identifiers being BrickColors, were core to their use when they were made on Roblox. It cannot be changed without causing backwards compatibility issues.
Right now, teams are used for 2 reasons:
They are quick to use
They are the only way to control playerlist coregui
By deprecating Teams, we acknowledge that they are outdated relics. When we release that baggage, and can focus on feature requests specifically aligned with our current needs.
but still teams are enough