I'm sure we've all noticed that the ships of the Tholian Assembly have rather unique shield effects when hit. Similar to the Elachi, whose shields glow green when damaged, Tholian ship shields give off a distinctive red hue when stuck. When the visual effects for shield impacts were improved during a patch in late January 2016, it was mentioned that colored shield effects would be added to certain reputation shields. You can read these patch notes
HERE.
In case the link isn't working, I will quote the aforementioned note below:
"
All standard shield hit FX have been updated with new visuals.
Visuals for the Undine, Elachi, and Tholian Reputation shields have been upgraded with their colored versions of new FX."
Based on this statement, I'm assuming that the Undine shields refers to the 8472 Counter-Command shields, the Elachi shields refers to the shields used by Elachi NPCs, and the Tholian shields are both the Nukara shields and the shields used by the Tholian NPCs. The Counter-Command shields have retained their green hue, while the Elachi and Tholian NPC shields have also been updated with their colored shield effects. The Nukara shields, however, are still the standard white color instead of being red.
So, is the wording in this patch note just wonky and unrefined, or did something not get implemented properly? I mean to me and most others, "Tholian Reputation shields" refers to the Nukara shields, so why don't the Nukara shields have red effects? Before this update the Nukara shields had the standard white effects, but based on this patch note I had assumed that the Nukara shields were getting the red effects now to match Tholian NPC shields.
If it was not actually intended for the Nukara shields to be given the red shield effects, then I would just like to ask: why can't it be given red shield effects? I mean, the files are already in the game for Tholian NPC shields, and seeing as the Nukara space set is Tholian-themed, it would make perfect sense for them to be given red shield effects as well. Again I ask, was this just poor wording on the part of whoever wrote the patch notes, or was something not implemented properly, thus making the patch notes seem inaccurate?
Comments
But hey, I guess that's another issue for another thread...