I think the most important things to take from this are that CG needs to respond to things faster and track the worldwide stats more aggressively, at least with regards to world first stuff. Cats out of the bag now, can't really take a stance now.
Look, I know that NRAJ and other devs/cms get a lot of flak whenever they post on controversial issues. The problem is, these slower and hands off responses are leading to decisions due to the inability to back out. If we had a response on this sooner, especially a unified Dev Team response, this may have been mitigated or avoided (assuming this is an unintended consequence of a semi broken system). I feel bad for the level of scrutiny and flames they deal with, but for the cms that is their job. Avoiding stances or taking a hands off approach will lead to future abuses by players.
This is compounded by our lack of either a beta test program or the willingness of the devs to install artificial gates during investigations. If internal projections, or even optimal projections are saying one thing, but the community is able to do another, install temporary gates until you can sort things out. Halting people at 144 shards is a lot easier than telling them that the Han has to be taken back (as an example).
I'm surprised the patch for Han isn't pushed out sooner, however I think that is more due to time zones and the expected timing of the unlock (see: internal projections).
Edit: Appreciate the thread Wookie, and appreciate the attempts to have a civil discussion.
To the forums. Understand that, IMO, this entire debacle is an issue of the hands off approach of the dev team instead of the guilds who used it to their advantage. Personal feelings about guilds should be put aside, this is a systematic issue at the developer level for not addressing game issues in a timely fashion and with a unified approach.
What a way to start Memorial Day weekend .-.
