Can we have legacy force field back? I don’t want to remove the new force field or make the old one default, I just want the retro look and ability to make entire models immune to explodes.
like the glowy outline thingy? I want that option too.
Didn’t they just use SelectionBoxes? Or are those too big?
Edit: Here’s what it looked like for those who never got to see it
It looks like you could do that with SelectionBoxes, except that SelectionBoxes use BrickColor instead of Color3, so you wouldn’t be able to tween the color like that :c
They’re the same size, but selection boxes have to use brickcolor.
ForceField are one of the things I really liked and was upset they changed 
The other is the badge chat notification COUGH COUGH
I dont see why SelectionBoxes dont use Color3 like all other UI elements.
But I dont see them bringing this feature back, unfortunately.
[quote] I dont see why SelectionBoxes dont use Color3 like all other UI elements.
But I dont see them bringing this feature back, unfortunately. [/quote]
Pretty much all 3D guis do. Surface selections, lassos, floorwires, handles, archandles. It really should be changed.
[quote] I dont see why SelectionBoxes dont use Color3 like all other UI elements.
But I dont see them bringing this feature back, unfortunately. [/quote]
Pretty much all 3D guis do. Surface selections, lassos, floorwires, handles, archandles. It really should be changed.[/quote]
I think it’d be smarter to move the BrickColor system forward into a Color3 system, keeping the original BrickColor.new() palette system, but linking them to Color3’s stored in a table, then giving us the ability to set them to a Color3 as well.
Speaking of forcefields, why is there just one look for it
Why is it always blue; can’t it be that team’s color or maybe even customizable? (Fitting the entirety of the model size so it scales)
[quote] Speaking of forcefields, why is there just one look for it
Why is it always blue; can’t it be that team’s color or maybe even customizable? (Fitting the entirety of the model size so it scales) [/quote]
A forcefield is a pretty important element of the game - it means the other player is invulnerable. Recognizing that your enemy can’t take damage should happen as quickly as possible, and if forcefields all look the same then you can very easily and quickly see that.
[quote]
I think it’d be smarter to move the BrickColor system forward into a Color3 system, keeping the original BrickColor.new() palette system, but linking them to Color3’s stored in a table, then giving us the ability to set them to a Color3 as well. [/quote]
There is a thread somewhere talking about how allowing bricks to be color3 instead of a brickcolor would introduce a huge amount of stress on the current networking as BrickColor is significantly less data than color3.
[quote]
I think it’d be smarter to move the BrickColor system forward into a Color3 system, keeping the original BrickColor.new() palette system, but linking them to Color3’s stored in a table, then giving us the ability to set them to a Color3 as well. [/quote]
There is a thread somewhere talking about how allowing bricks to be color3 instead of a brickcolor would introduce a huge amount of stress on the current networking as BrickColor is significantly less data than color3.[/quote]
Cant they just send a regular integer (00RRGGBB) over the network?
[quote] [quote=“woot3” post=95073]
I think it’d be smarter to move the BrickColor system forward into a Color3 system, keeping the original BrickColor.new() palette system, but linking them to Color3’s stored in a table, then giving us the ability to set them to a Color3 as well. [/quote]
There is a thread somewhere talking about how allowing bricks to be color3 instead of a brickcolor would introduce a huge amount of stress on the current networking as BrickColor is significantly less data than color3.[/quote]
Cant they just send a regular integer (00RRGGBB) over the network?[/quote]
They don’t want to send one for every part when they can use BrickColors to send significantly less data over the network.