{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
originally posted in:Halo Archive
2/3/2015 9:08:08 PM
1
We did get a forge map in the Beta, Pegasus and then we got Orion as well at the end. Never got a chance to play the third week, but they have a Halo 4-esque vibe in terms of appearance.
English
-
Let me rephrase that. The map those two were built on was very much incomplete.
-
Well, that may have been the point. To show us what we can do. Motivation.
-
That might have been their intention, but it ended up just looking lazy. When they first added Pegasus to the beta, there weren't any death barriers, so people could get out of the map. In doing so, we found that all the "trees" were just 2D low-resolution images, the ground would suddenly stop being solid and you'd fall to your death, and the water wasn't even implemented in yet. The water didn't make any noise and didn't react to the player in any way. But by far the worst offense was an entire side of the map looked like it had carved out in a straight line.
-
Well. What about Orion?
-
Orion was built on the exact same map, and thus had the same issues.
-
Perhaps Forge mode itself was still in Beta within 343, such as the actual maps were developed first.
-
Oh, that is such a bad idea from a game design standpoint. You want to have a completed forge base map first, then build custom maps on it. No offense to 343i, but Halo 5's forge maps looked hideous from anywhere outside the play space. This is because they made very limited use of the existing map, and thus the base map and the custom map weren't blended together. By comparison, Reach's custom maps looked great, both inside and outside the play space, because Bungie created the base map first, and then built the custom maps around it.
