DD_74 wrote...
Just because there is a no refund buyer beware policy does not obsolve the company from a faulty product. If that were the case then there would be no tort cases for products from companies that knowingly placed products on the market that were defective and possibly caused damage.
In this case a product was released with known bugs and those bugs affected other content in the actual game. If the download simply sucked then I would have no issues. But to take my money and cause a loss of something I actually worked for is noththing short of theft in my opinion. If the cost were higher then there would probably be even more outrage.
I do not know if you read it but from Victor Watcher from
http://social.biowar...dex/655509&lf=8To those 360 players affected by the Title Update issue this week, our sincere apologies.
The situation is something we are taking very seriously and the team is continuing to work around the clock to rectify.
When testing any large endeavor like that, we depend on selectively targeting systems related to the changes being made, prioritized by order of perceived risk.
Unfortunately we did not foresee the changes being made to impact the systems it did, which is how something seemingly so visible still managed to avoid the dev team, and multiple test cycles of seasoned QA all through our internal teams, and EA & MS cert teams, and ultimately ended up out to the public.
To help us avoid similar problems in the future, we're updating all our test plans across all platforms to take additional edge cases into account, as well as committing to more detailed test passes that will also prevent something like this happening again.
In the meantime, there is good news - a fix is already in test for the 360 issue and looking very good, we hope to have a new update out as soon as possible and will update you as best as we can. If successful through the updated test plans, it will still deliver the expected fixes as well as restore the game saves for anyone affected by this week's title update. For now, we do not have a timeframe for when the fix will pass approval and certification, but we will keep you updated.
_____________________________________________________________________________________
I cut out some parts to leave the more relative parts in here. A apology, an explanation of how it made it thru several teams of testers and that they have something in the works to fix it.
If you do not want to accept it or believe they are lieing then that is your prerogative.