I think I speak for every developer here when I say I’m really tired of only being able to use 64 different colors, it’s not a very versatile range and there are a lot of shades missing for certain atmospheres. Frankly I would like to be able to set a brick color to just an RGB, I think that would probably be the easiest way to implement it, and just get rid of the classic brickcolor chooser and the limitations you’re imposing on developers with the 64-color system.
This has already been discussed, and has been discussed at BloxCon. The reason why there aren’t more is for bandwidth.
What if we were allowed to define our own brickcolors and overwrite existing ones? There’s like twenty light blues that no one ever uses. I’d love to be able to overwrite those with something like gold or turquoise.
There’d be no difference in the amount of data that needs to be sent, aside from the one Color3 at the very start that tells the client what the brickcolor is referring to.
Bandwidth, what? RGB takes 3 bytes. BrickColor already takes more than 1 byte just to look up the colors.
So you literally only have to send like 1 more byte.
Also, what about GUIs?
1 Like
[quote] Bandwidth, what? RGB takes 3 bytes. BrickColor already takes more than 1 byte just to look up the colors.
So you literally only have to send like 1 more byte.
Also, what about GUIs? [/quote]
Um, 64 colors is like 6 bits?
If 2 extra bytes is too much for them, they could always make that 6 bits be a byte and give us 192 (???) moar colors to work with which ought to be enough. Someones going to have to name them all tho. o,o
[quote] Bandwidth, what? RGB takes 3 bytes. BrickColor already takes more than 1 byte just to look up the colors.
So you literally only have to send like 1 more byte.
Also, what about GUIs? [/quote]
Um, 64 colors is like 6 bits?
If 2 extra bytes is too much for them, they could always make that 6 bits be a byte and give us 192 (???) moar colors to work with which ought to be enough. Someones going to have to name them all tho. o,o[/quote]
There are actually more than 64: Documentation - Roblox Creator Hub
So I suppose 144 colors → 1 byte; although, that just means they could at the very least give us another 112 colors, not counting all of the crossed out ones.
"What if we were allowed to define our own brickcolors and overwrite existing ones? "
That only works well until you’re no longer one single person developing a place from scratch. It would be an unacceptable solution for most of the usage on Roblox where various models would contend over space in the color pallet.
I really hope there’s a good solution to this, I need more colors. ;A;
Also, there’s this thread Documentation - Roblox Creator Hub