1. Well, this one's true.
2. Halo 6 cannot possibly be on 343i's radar outside of writing.
3. 343i is handling the patches, since most of the fixes involve UI and Networking.
4. Yeah, that's what he said. He's blaming MICROSOFT (the publisher) not 343i (the developer).
5. I really don't think you understand the difference between developer and publisher, with all due respect. The publisher worries about the money, the developer worries about shipping code.
2: What do you think conceptualization means? That IS a part of development, btw. Once conceptualization is nearly completed, they are able to determine need for hire. Guess what? They're starting advertise positions for hire.
3: Just curious - What makes you believe this. Seriously, not arguing; just asking. If you wouldn't mind sharing, I'd appreciate it very much.
4&5: I know what he said. And I do understand the difference between dev/pub. 343i is essentially "Microsoft, game department". . . The people who MANAGE 343i were literally cherry-picked out from other areas/departments within Microsoft. Go look it up if you wish to confirm it for yourself. This is important because unlike Bungie who existed prior to their deal with Microsoft, 343 is not only funded by MS, they're entirely managed by MICROSOFT. Their every decision and move is MICROSOFT's decision and move because they are the SAME.
The developers were hired to be employees of Microsoft (find a 343i job that isn't posted through MS). The publisher is the developer, the developer is the publisher in this case. 343 Developers - Hired by MS The funding - MS. Planning - MS. Marketing - MS. Platform - MS's. License to Halo Rights - MS. 343 is a name, and nothing more. The developers are MS employees. You can say this makes no difference, but it absolutely does. This is not two separate entities which are working together, as was the case with Bungie and MS. This is one entity and that entities name for one department. Pointing fingers at one/blaming the other vice-versa...is POINTLESS!