No for many reasons. First there needs to be a stable base on the old engine to compare with when moving NH to 2.8.2. It would be good if this were a completed build 14 (or if that doesn't happen this time) at least a formalised point in coding development. Second the people active on modding NH are generally there because they want to add/change stuff. In the time I have been active this has always caused difficulties in keeping aspirational material away from breaking/bugging the current WIP. This has been eased a bit over the past year by @Grey Roger 's robust defence of a stable base. However I don't see the active community putting their personal efforts aside to help migrate and test the code, without that effort there can be no guarantee of when the migration would be "complete" and tested. I am not looking for the new year as per new moddb aspiration (except in the sense I would hope it complete WITHIN next year). Migrating to a new base may introduce unknown problems anywhere in the code, this is not like adding something which could (in theory) just be reverted so that bringing build 14 to a clear conclusion would be pushed into the future again. One clear area that is not currently equivalent is in particle effects. Although there is a proven approach conversion of NH particle effects is far from achieved (in fact production in XML format not even started yet). Migrating to a new base seems much more suited to a new build version than thrown in to the end of a long process of development. The new base would conceptually open up the whole COAS (and possibly TEHO) maps,islands,content to incorporation with NH (or vice versa) this just runs into the age old problem of too many tangents for people to run off along for a random community to manage. If it became the "official" version it has the potential to disrupt the status quo of minor tinkering and added story content that has allowed a stable mod to be maintained. Finally there would be some difficult political issues to be addressed - what relation if any does this have to NH remastered, what about maintaining compatibility with the other Storm games? Does an engine change required elsewhere in the family of games (and that includes ERAS) get maintained in NH. What about a 64bit version and @ChezJfrey 's thoughts about moving his Maelstrom 2.8.2 on from directx 9. I suspect these aspects would be harder to address than the technical ones proved for him.