Answered by
5 years ago Edited 5 years ago
You seem to like using the method I showed you, haha
That's at least what I thought of like when I ad-lib.
REASON
Have you read the output? When you assign a value to a BrickColor property, the new value should be a BrickColor datatype, did you notice? It appears that you're trying to apply a String (text) value to the Handle's BrickColor at line 26.
That being said, the new value should be BrickColor.new(bucnhOfColor[val])
instead.
Now, to prevent further... unwanted events from occurring, you should not include those asset IDs for shirts in that script anymore. Also, I now doubt that you're trying your best to fix the issue on your own, so if you aren't, you should try harder before asking us! :)
Also, if the Handle of the accessory has a Mesh and a texture, the texture (with little to no transparency) may override the Handle's color. You should remove its texture if it has one, or just keep it if you think the texture synchronizes with the color of the Part.
time to fix stuff
As regards what I first mentioned above, here is an abbreviated illustration on how to fix it.
3 | if val > = #bucnhOfColor then |
4 | d.Handle.BrickColor = BrickColor.new(bucnhOfColor [ #bucnhOfColor ] ) |
6 | d.Handle.BrickColor = BrickColor.new(bucnhOfColor [ val ] ) |
Simple as that!
Tell me if you have more issues arriving after. Cheers!