Bug : I have tried this with and without plugins, and the result is still the same on my end.
When I try copy and pasting RGB / Hex codes into beams, the beam doesn’t take it as one color and just ignores it completely, unless you go into the actual beam editor and set it manually, this gets really infuriating especially when there is a lot of color sequences and you’re trying to get things done quickly.
For particle emitters, when you try copying and pasting the hex / RGB, the whole emitter clones itself, instead of the actual RGB.
Two Videos down below as proof / reproduction.
Expected behavior
The beam should be able to take the RGB / HEX
And the particle emitter same thing, however instead of copying and pasting itself it gets the actual value.
When you click the color3 property in a particle/beam (whatever instance where you can have the colour change over time), it doesn’t actually enter the text box on the first click, you have to click it again to actually start editing the text box.
Still, it’s an annoying quirk that ought to be fixed.
To add, ontop of that, shorthand autofilling don’t work on them.
For example, if you type 255 in color box in any other property, it will get translated into 255, 255, 255, but ColorSequence inputs will cancel this.
We’re working on rewriting the Properties pane into Lua in the same way we did for the Explorer and we’re going to make sure the new version has much better affordances for copy-pasting properties, including stuff like being able to copy-paste a whole ColorSequence.
The exact UX isn’t nailed down yet because we’re pretty early in development but at the very least we want to support the concept of “copying a (whole) property” rather than just a textual property value.