Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Obviously, if this interpretation of New Mombasa had made it into Halo 2 it would have been a fully functional mission. This is a sequence of scripted events. Bungie had to get something ready for E3 and didn't need to do more than what was necessary for a few minutes of gameplay.
I'm not sure why Bungie decided against the original New Mombasa but I'd guess after they had to scrap the original engine and all they made for it, by the time they got to New Mombasa in the story, they simply thought a daytime approach would be better. Maybe that's something to do with the Scarab, who knows.
Regardless, Halo 2 was rushed and we ended up getting a half-finished and unbalanced sequel.