Who will make Halo 3?

narcogen over at rampancy has an interesting take on the question of whether Bungie will be doing Halo 3. Based on the precedents that Bungie have already set with Marathon: Infinity and Myth 3, he raises the possibility that Bungie may not develop Halo 3 themselves, but that some other developers will continue the franchise.

Having read his piece, and mulled it over, it led me to think about this question – who exactly are Bungie, and what makes a game a Bungie game? For me personally, Bungie are the people that made Halo: Combat Evolved – that’s my first experience of their work. That Bungie is different from the Bungie that made Pathways Into Darkness, Marathon, and Myth. For a start, they had become part of Microsoft, but also they had grown in size, and some of the personnel had changed. And again, the Bungie that created Halo 2 was not the same as the Bungie I first experienced. The team assembled to create Halo 2 saw new faces join, and some old ones depart for pastures new. If you look at the credits pages in the Halo and Halo 2 manuals, you can see how many more people had become involved with Bungie in the creation of Halo 2.

But then, this is to be expected. Change is the only constant, nature is a Heraclitean fire. If Bungie hadn’t changed, there would be no Halo. And I expect Bungie to change again, and produce something new, and hopefully it will be at least as great as the Halo franchise.

But what about Halo 3? Does it actually matter if Bungie does not make it? Well, it depends on what you mean by make. For me, the key thing that has made Halo stand out is its story – and I’m not alone. Bungie has a history with Marathon and Halo of creating games and placing them in universes that are realized enough to support literally years of speculation.

The creative forces behind these stories are a big part of what Bungie is to me. And it is these forces that would be missing if Bungie do not make Halo 3. However, I believe that the story of Halo 3 is already created to some extent. There’s a shot from a video taken in the Bungie offices during the Halo 2 development that clearly makes reference to the Master Chief and the Arbiter at The Ark – something that does not appear in Halo 2, but would be likely to occur in Halo 3.

I think that when Bungie set out to create Halo 2, they had the full storyline in mind, and there wasn’t necessarily going to be a Halo 3. However, time constraints and other factors meant that they could only tell half the story – leaving us with the somewhat anti-climactic ending to Halo 2 that has enraged so many.

Now, conspiracy theorists may suggest that Microsoft knew that with the XBox 360 coming along, and with the PS3 as its main competitor, that they would need something big with which to fight off Sony. A console is only as good as its games, after all. So, having Halo 3 ready to release when the PS3 is released would be a good marketing strategy – Bill Gates has indicated in Time magazine that when the PS3 is released, it will run smack into Halo 3. Perhaps they “asked” Bungie to divide the game into two, leaving the final installment as not just a battle against the Covenant, but against Sony too. Personally, I don’t think this is what happened, but then I wouldn’t be surprised if this was a factor that was added to other reasons to divide the game.

So, given that the story for Halo 3 could already be written, and that the game engine and many of the artistic artifacts would already be in place, it would not be that hard for other developers to take over and finish the job, freeing up Bungie to work on something else – maybe the real PS3 killer 🙂 I can imagine the situation where in Jason Jones’ mind, his story of the Master Chief is told, even if the wider public haven’t heard the final installment yet. He may be feeling that it’s time for a new story, a new challenge.

The fly in the ointment in this scenario is that the story is not enough. Halo and Halo 2 are as good as they are because of the whole team at Bungie – artists, level designers, and very importantly, Marty O’Donnell. A Halo 3 without Marty’s music would be missing a vital component. And there are others about whom you could say the same.

Also, the multi-player aspect of Halo and Halo 2 is as important as the story. The only thing about this is that Halo 3’s mutli-player features may be no different to Halo 2. I can foresee a situation where Halo 3 players can take on Halo 2 players using XBox Live, playing the same levels, using the same match-making lists, etc. There is no need to have a different multi-player experience for Halo 3, and it would make a huge amount of sense in relation to the XBox 360 to allow Halo 3 and Halo 2 players play against one another.

In a way, the multi-player aspect of Halo has taken on a kind of separate existence. Now that the engine is in place (and can be tweaked via Autoupdate), new levels can be created at any time and released via XBox Live. There doesn’t need to be a Halo 3 for more levels to be created – as shown by the arrival of the new levels recently, with more to come in July. And it’s not likely that any new weapons or any of the game mechanics would be created for Halo 3, especially if that would prevent co-existence with Halo 2 players on Live.

So, from this perspective, Halo 3 is really about finishing the story, the single-player campaign. This story is probably already written. The engine is in place. Many artifacts are already created – they’re the same ones used in Halo 2. The levels may already have been sketched out, and storyboards for cutscenes created to some extent. It’s not beyond the bounds of possibility that someone else could come along and finish off the job.

So, would it matter if Bungie didn’t make Halo 3? I think that they have already made a some of it, and those pieces are some of the key pieces that would give the game that Bungie feeling. As long as whoever makes Halo 3 can kidnap Marty and anyone else that would be needed to ensure that it stays true to the Bungie Way, then I think we won’t be able to tell the difference.