Capital Games TeamI sincerely hope "resolving the issue" means you completely undo it. Either that or give us like 1000 reroll mats. I don't have a single datacron above level 5 from that set now.
Let's be real here: The only way to solve such an epic F-up is a complete rollback. Nothing else is going to replace weeks worth of time and resource investment. Weeks of buying 100 and 200 crystal refreshes in Conquest and farming nothing but shards for characters we've already maxed just to have enough shard shop currency for reroll mats.
The longer you wait the more painful it'll be to sort out things like purchases after the rollback point. So better hurry up. And of course something like this can't EVER happen again. Either you'll start thoroughly testing things like datacrons before rolling them out, or you live with the screwups and wait for the crons to expire no matter how loudly some whales are complaining that Rey suddenly beats their shiny relic 10 Hondo.
You also need to open a line of communication to the player base and discuss matters with us the next time you feel you have to undo something. We know you're not playing your own game, as this disaster has once again proved, so you need to talk to us and find out how something like this can be resolved in the least painful way possible. Don't just speed ahead with a half-baked plan and try to implement a quick fix before the holidays. Your customers who spend considerable amounts of money on this game deserve better.
Last but not least, there needs to be a change at the top. Whoever is currently running the show at CG either doesn't know what they're doing or they aren't really in charge and in the loop. This wouldn't have happened in Carrie's days. You might not fully realize this yet, but this is by far your most epic mess in GoH history. You've completely skewed the balance by putting casual players with little investment in DCs on even footing with highly invested players us who had 8 or 10 or 15 maxed DCs with near-perfect stats after tons of rerolls. We did this work expecting to reap the benefits until mid-March. Once more emphasis: This cannot be fixed without a database rollback. Better jump to it.
