Words matter! A Studio rendering problem

I was helping someone troubleshoot a Bricklink Studio custom color and ran across this oddity...bug(?).

 

I created a metallic red custom color and named it METAL-RED (duh!). It produced the render in the upper left.

 

I then changed the name to METAL-DEEP_RED (and that's ALL I did). It produced the render in the upper right and gave the error, "Material 'METAL-RED' is not predefined. A fallback shader is used instead." But wait, the name is METAL-DEEP_RED...

 

Next, the name was changed to METAL-GREEN, even though the custom color is still the metallic red, and got the render in the lower left...the metallic red as expected.

 

Last, the custom color was given the name METAL-DEEP_GREEN, which produced the render in the lower right. It rendered...gold?

 

Wait...what?

 

[sarcasm]This is brilliant[/sarcasm]

 

In Studio, metal colors can only have a single name, METAL-COLOR.

 

If you use a two word name, METAL-PREFIX_COLOR, Studio drops the first word prefix and only looks at the second word. Studio thinks that METAL-PREFIX_COLOR is actually METAL-COLOR.

 

So, if you name a material METAL-PISTOLPIPE_COPPER, Studio will use the already existing METAL-COPPER.

 

It was pointed out to me that I was incorrect. It **IS** the metallic green, not metallic gold. It is my error for not taking the extra step of looking at the renders on a calibrated monitor last night.

Done