Blog Post
So, despite the fact that the Jar Jar event hasn't come back around yet, there's now a 'fix' for the bug where the shield gen would work with a non-Gungan 5th?
The question is, as always, 'why now' - it seems (and has for years seemed) that anything that even marginally benefits a player gets more prioritized for a fix; while something like the immortal Grievous bug takes an unreasonable amount of time to fix.
Why not hold this until Jar Jar was back on the holotable?
Note: I know this is, in fact, a bug. But it's been one for near as long as these toons have been around; and it's strange now that it's widespread / people know about it and are Jar Jar ready that it's a problem.
You make it seem like this bug has been around for years. No biggie.
- ImmortalAzazel6 months agoSeasoned Adventurer
No but it's been around for months.
It's just the weird optics (and poor communication around) issues like this.
I.e. it's been a bug for months. Players find comps that work in TW around this bug in June (and make use of otherwise unusable Datacrons in that mode). The raid drops in early July, 4-man Gungan comps with random 5ths are found for use in the raid.... and the bug is 'resolved' before Jar Jar is back on the table, making players that are now Jar Jar ready more frustrated.
The raid is already overtuned and more F2P players have bad feelings around it; taking away a possible team for raid use (or diminishing it) won't make them happy.
If CG wanted to sell FOMO around Jar Jar, tell us he's not coming back until August the first time he drops (and let us know the raid is coming in July - especially since last communication was "Featured Raids last 8-9 months", indicating an August raid changeover, too).
And just as importantly, it's not communicating back on things that players care about that would be positives for them. I.e. there still being no ETA on Grievous fix so that we can start getting Zetas from Dathomir again. Heck, did we ever even get the third round of gear fixes that were promised 2++ years ago?