One more proof that their QA-department and/or the communication between QA and Devs is seriously lacking.... or some bug is hiding some of the bug reports written by players. Which is sadly quite plausible after hearing "We can't find your bug report" so often.
Now at least they know of the real Voldi (at least of one of them I gave up counting).
About Aux helping shields... in case of doubt I say he was so shocked about Voldi that he confused some things he usually knows quite well.
with people that had a clue. A lot of what was vocalized was almost incoherent and all over the place. It would be nice to have people actually string coherent thoughts together. I am almost of the mindset that everyone should have the exploit because I feel cryptic knows it is not widely known and therefore they have time but if the whole community did it, it would do 2 things, make cryptic sit up and really look into it, actually bring balance to the game. of course all of this is my humble opinion.
Maybe its time for someone to start a PvP podcast that highlights such cheats and bugs in a public and vocal format that can't be ignored or silenced or overlooked?
You know, that's not a bad idea, Roach. Interview some of the PvP Fleet's leadership, talk maps, strategies, make announcements for player made PvP events. Maybe a blow by blow account of the action in Ker'rat .
It seems that the PvP community knows more about balance issues, bug issues, hacks etc than they do, and it showed.
It would be funny if it wasn't true
I am indeed glad that some light has finally been shone on this issue, but I am significantly more depressed as to how little they knew, and how much that says about how they value PvP community feedback.
I watched that segment and was apalled by his lack of prior understanding. The fact they spent a significant portion of an EXTERNAL, PLAYER-MADE broadcast to get a dev understand a bug which he admitted to not being totally well-informed, was insane. That dev should have been paying closer attention to his official sources, like bug reports and forum posts.
This is sad, and only publicizes the already well-known flaws of the QA department. Cryptic, get your poop in a group, and atleast make sure your devs don't make fools of themselves on a podcast... failing miserably at something is bad enough, letting a PR failure like this out? Only emphasizes the incompetence and unprofessionalism.