Perhaps this isn't news and perhaps everyone is tired of ME3 griping and anti-griping griping, but as one might expect there are threads popping up on Bioware's forums positing that EA was more responsible for some of the more disappointing changes in ME3 than Bioware was and that this is endemic of EA's general ruination of the studios it acquires (something that was thought to have died with "old" EA).
Bioware have summarily been shutting down any of these threads, saying that EA's internal decisions are "no one else's business" (verbatim) - not even open to speculation.
I'm not sure how I feel about this. On one hand, yes there is a lot of griping without substantiation from people who are not qualified to speculate on how the game industry works. On the other hand, suggesting that people have no business engaging in that speculation, without offering any other meaningful defense, seems a bit, well, slimey. Would they say that Jeff's jar video's are inappropriate because he speculates on the inner workings of the developer/publisher relation (though obviously he's much more qualified to do so)?
See the following threads, which I have limited to the just the initial post and Bioware's response here. Remove "&lf=8" tag from the link to get the whole thread.
http://social.bioware.com/forum/1/topic/323/index/9822214&lf=8
http://social.bioware.com/forum/1/topic/323/index/9822736&lf=8
---Update---
To clarify what I was trying to get at (and hopefully make less people here hate me):
Yes, I could guess what those threads devolved into and no, strictly speaking, it didn't surprise me that they were closed, nor did I think it was entirely uncalled for since they're mostly ranting.
However, it's the nature of the closure response - that fans are basically not allowed to speculate on who had on creative control over the game, or how the industry works - that seemed a bit off to me and is what I wanted to call into question. Though, yes, I admit perhaps I'm reading too much into the diction used to close a largely pointless thread.
Log in to comment