EpicRandy said:
Shaunodon said:
Where does this 'damned if they do, damned if they don't' angle come from? It'd be one thing if they felt like they had no choice but to release the game out of pressure. But they didn't just stop there. They also made it the centre of their first developer showcase for the year; made it the only AAA exclusive for the first half of the year, the first since Halo Infinite; and even chose it as the first game they'd price at $70. How can you put this much backing behind a project without knowing the disastrous state it's in, and expect to not be blamed when you're the parent company? I'm all for them taking a hands-off approach when it comes to letting the developers and studios have full creative freedom, but to not have accurate and up-to-date information on those projects and what you're planning to put out to market, just makes them look negligent. Phil can try his hardest to clean up this PR disaster, but his job will continue to be impossible if he doesn't make sure he's getting the right information when he needs it, rather than after the damage is done. |
@bold: But that's the job of the publisher, if MS starts to distrust Bethesda so much that it overrules them then MS just need to merge Bethesda publishing into Xbox. |
Pretty much this. Its a fine line when Bethesda as the publisher of this game was not giving enough warning signs that this game was not up to snuff to release because at the end of the day, MS has to trust that Bethesda to know where their projects are at without having to nurse them like a child. This probably undermined Bethesda more than anything else which as I stated now puts MS in a position where communication between the 2 companies are probably going to change so something like this does not happen again. Remember the statement from Phil where he stated a user test of the game put it around the 80s. Who did that test, was it Bethesda and if so, was it doctored. There is definitely missing information we do not have concerning the whole issue.
