This is most likely a bug. Can't phantom this being a serious change from Blizzard.
I've just logged in, and haven't updated my addons since yesterday right as the servers came back online. I still have the nice friendly nameplates without bars, at least out in the world. Could this be an addon update?edit: i haven't attempted to disable/reenable, as that might get rid of them.
raiders nowadays can't function without 50 weak auras telling them exactly what to do and how to play, disrespectful
This is some Microsoft design decision level. Hoping it's just an error.
I hope it's just an error since I can see those getting in somebody's way pretty easily.
Unfortunately, default player names (non-nameplate) are simply illegible on modern screens. Even using the new accessibility option to increase the font size, the transparency and lack of shadow makes them nearly useless for quick identification of which party or raid member you're looking at. Using this CVar was the workaround - it was in use by a large % of top raiders for a reason. I really hope this was a mistake, or the change was made in advance of an incoming system to properly customize friendly nameplates in instances without addons.
The default nameplates are among the weakest features of the Blizz UI and they need to be completely overhauled. I can't imagine playing without Plater, this CVar was extremely useful and I hope it returns but after how they handled the FoV CVar I have little faith in them making the right decision.
Rather annoying.
Don't know if this still works after the 10.0.5 changes but the addon SmallFriendlyPlates allows you to have friendly health bars ON in dungeons while they are scaled down by like 50% to make them tiny enough to be manageable.
This is 100% terrible. Making terrible-looking stock nameplates, and then making them unable to be altered by players......and now unable to even be hidden....Genius!
i really like this change, ive been trying for weeks to get my plater to show nameplates, and nothing worked, till this update and it fixed everrything for me. i hope they DONT change this.
I'm sorry to say that this is likely not a bug :/they've removed all code that handles and supports this CVar (see the code diff)they did make it easy for themselves to add it back, but well..