So, I was playing the weekly heroic, with another friend in the room playing some crucible.. At one point he finished his match and got the 'pardon our dust' notice before being kicked to the title screen. He went to sign in, and was greeted with an update screen. It 'downloaded' (cut to 50%) 2.63 MB, and stopped. His ps3 was then unresponsive, and he was forced to forcibly shut down his ps3 midway through the update. Upon restarting his ps3, sending an error report, dealing with the usual 'this system did not shut down properly,...' message, and signing in to destiny, he got [b]Error Code: [u]Boar[/u][/b]. He was then forced to reinstall destiny onto his ps3 hard drive, in its entirety, because as you might expect, shutting down halfway through an update will leave you with some broken/inconsistent/corrupted files, and instead of taking time (possibly too much to be efficient) to do a file integrity test and repairing only the necessary files, it simply wiped the game off of the hard drive, and started reinstalling.. So, me being the bad person that I am, I chuckled at what seemed like a fluke of misfortune and continued playing my strike. Upon finishing the strike, I was run through the exact procedure. To the letter. 'Pardon our dust...', title, update, stuck at 50%, ps3 froze, 'a problem occurred...' (error report), 'system didn't shut down properly...', launch destiny, download update & re installing destiny. So... Uh.. What happened guys? You did test it before deployment right? And please, don't just give a 'we're working on it' PR response.. I'm not mad, or upset, just bewildered and curious, and a little frustrated at the production/development standards that seem to be in place.. Can we get an honest, straight, technical response as to what happened, why it happened, and how your going to avoid doing it in the future? Preferably from someone on the development team or at least with development experience... Thanks, One of your numerous lab rats. PS.. Why am I still playing?