{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/12/2016 4:30:54 PM
4
I never really understood the issue people had with maps made in forge. If they weren't made in forge they would still have the exact same layout. The only real issue was the limited color pallets got old in the past, but now that is no longer an issue.
The current forge is barely any different from the tools that 343 uses to make regular maps. The major difference being that you can't import more assets into forge, only use what is there (which is a LOT).
The issue is not that the maps are made in forge. That's not an issue in the slightest. The only issue is that the maps are poorly balanced to begin with, and they would be whether they were forged or not.
English
-
Forge itself has an inherent ugliness to it simply because of how blocky you have to make everything. 343 themselves didn't even create the maps. And, in all ways it does show a complete laziness. Besides handing off map development to non 343 staff, non of the assets used are original. Having them be included in the "18 free map" DLC is idiotic, as anyone could make those maps just as easily.
-
I don't even see it as lazy. Forging a map takes a considerable amount of effort. People have been known to work for several months perfecting one map. This was especially true in halo 3 and reach, where you could only do so much in forge and it took an extreme amount of effort to build a decent map in forge. I will agree that community maps should not count as DLC. But the current forge maps made by 343 are fine. The maps would have been exactly the same and taken almost the same effort to make if made in their standard engine.
