@AndyCovell wrote:
It’s the same damn thing. Timing is key. You say you do t work for CG but boy this is a situation where it sure feels like it.
This toon has been out for over 6 months. Likely people were scrambling to get her because she was so good. The problem is if players knew it was a problem on release we would have stayed away. But we spent money on her to make her better. Gear, Zetas, and 6 dot mods. You don’t get to make us feel bad for another CG error and say it’s WAI. 
Nest's protection bonus plays exactly the same as it did before - except in situations where her max health is drastically reduced (which right now is only vs Revan).  Nest is still a very powerful character in many aspects of the game, and just has some reduced usefulness when fighting Revan.  If you choose to mod her for high tenacity (which allows her to resist the max health reduction), then she will retain the same functionality she had pre-patch.  
I know lots of players who have Revan (including myself), and don't know anyone who had trouble beating Nest.  My GMY could one-shot a Nest with full health and protection - she never got a chance to stack bonus protection anyway.  Occam's razor indicates that the situation exists as it was presented - this bug was identified after Revan's release, it was slated for fix, and it was fixed.  It should have never behaved this way to begin with, but the developers (who are human) accidentally coded the bonus protection to calculate based on character's initial max health instead of the current max health.  Now they have fixed it.  
I am not trying to make anyone feel bad.  I am trying to have a conversation.  SBCrumb has made it clear that this change was intentional.  You can think that it's a grand conspiracy, and that CG has changed their stance on this skill.  But I doubt that to be the case, because CG making this part of a conspiracy to "appease whales" would be illogical.