> > That’s a poor judgement, they are two completely different engines, stop making things sound so simple, trust me, when it comes to Halo, it isn’t.
>
> Im stating the fact’s. I can almost guarantee if the developer put some effort into it Elite’s could very well be DLC on Halo’s engine.
>
> The engine has evolved substantially with each new iteration, Halo 3-Reach and Reach-Halo 4 being the most substantial engine overhauls. However this video proves the developer has the capability to add damn well anything into the multiplayer space since Halo 3 at least.
>
> Yes I know that was done in-house at Bungie. But if they really wanted to for whatever reason a Title Update could have updated Rat’s Nest with all those model’s for everyone.
>
> Here’s another link for you. We see here a man bored with his developer kit at home. I cant speak for how long this took him. But he managed to add the default Plasma Rifle, the Elite model. Marine model’s. etc into the ODST Crater map, a map that was designed with only the ODST and enemy Covenant models in it’s files.
>
> It was never a question of impossible/possible. But why/why not.
For the first one, that was done on a dev kit, like you said, it wasn’t on a retail console, it would have required a large title update which updated the .map files to add the AIs, which as Bungie confirmed shortly after that video came out that it is to large of an update to do, think about it, redownloading ALL the maps for Halo 4, that’s a big chunk of the space, well over a few GBs, it would take people a long time to download such an update.
And once again, for the second video, he took files from different parts of the game and modded them into Firefight, using a dev kit, which is once again not on retail, it would require a title update to redownload the .map files once again, just like Halo 3.
Scratch that, Halo 3: ODST stuck purely with the Halo 3 Campaign engine for both Campaign & Firefight, which allows for simple model swaps like a Brute and making the player play as one, although in that video it doesn’t show it, the view in first person would still have the player with the ODST hands with the same HUD as an ODST which would look extremely unprofessional, it would require even more extensive work for a new HUD to have Elite hands and individual weapon stances on the first person display for the Elites.
There are actually mod tools out there for Reach, ODST & Halo 3 that allows you to swap who you are in the single player, because the biped is already there and simple to swap, you can do it with a USB, never mind a dev kit, but those bipeds are not designed to work properly in first person in Campaign barely, hence the ODST arms in the first person display, let alone copying them over to Multiplayer entirely which would require a working HUD for Elite models, the Elite models to have hit boxes that are balanced and work properly and some sort of built in visual indication for overshields, camo and other armour abilities that we will see in Halo 4.
The work for it extremely huge for something that isn’t that big of a deal, along with the Elites models they would need to add in, they would need to change the UI in the menu’s to support Elites, allow you to change your Elite armour as such.
All that would still require a redownloading of the .map files for Halo 4, and before you try and pull a ‘oh,343 had plans to do it in Reach but didn’t because of time constraints’, they planned on adding Armour DLC yes, which had no effect on your first person display, your HUD always looked the same regardless, they didn’t have to change your hands which you will have to for Elites as well as the HUD to match whatever the Elites will have.
It is always the question of impossible/possible, in this case, with the updates required to make such a thing happen, it is impossible.
I seriously hope you can understand that this sort of change for Halo 4 is impossible.