Now lets all face the fact, when we heard the Bungie had an awesome contest where user-made maps would actually get into matchmaking, we were all excited. Many professional forgers as well as complete forge amateurs submitted their hard work for the contest, and there were many people who actually got their maps into matchmaking.
Those people were happy.
Yet suddenly, many were upset, and for a few reasons.
All the maps looked the same. There were already multiple forge maps that shipped on the disc, and whenever people would go into team slayer, practically every match would be on a map that looked just like the last.
The maps just… weren’t fun. It seemed like the people who submitted the maps were only focused on making maps which would win, instead of maps that the players would actually enjoy playing on. The maps were structured fairly well, but it became apparent very quickly that there wasn’t enough playtesting for them.
The maps went into playlists that people had become used to such as Team Slayer, where they really weren’t wanted. A seperate playlist, community slayer, was perfect for them, but it just disappeared after a few weeks and the maps went straight into matchmaking.
What I’m trying to get to is that… well… for Halo 4, we should leave the map making up to the professionals who get payed hundreds of thousands of dollars to make maps that people will enjoy. Sure, feel free to give feedback, but please don’t ask for another forgetacular. I understand that you all want to become a part of Halo 4, but you don’t need to just make a greedy attempt to make your name go down in halo history which hurts the experience of the other players.
Just keep on making threads telling 343 what YOU want, and if it’s reasonable, I’m sure they’ll be willing to make it happen. Just don’t ask for your work to go directly into matchmaking. If you want your maps to go into matchmaking, then go work for 343. Unless a map is incredible, plays out in a fun way and competitive way and also looks amazing, there is no reason that it should be put into the game. From what I’ve seen so far, only 343 is capable of doing that at this point, so don’t beg them to get your maps into the game, just enjoy what they give you and make the most out of it.
I agree to some extent. They should have a small limit to the amounts of variants each map has in matchmaking, so about one or two community map per playlist would still be OK.
Bungie included many maps in Reach that they had Forged themselves so they wouldn’t have to actually make them and because of the creativeness that Forge 2.0 brought to the table. I’m pretty sure Bungie wanted people to make maps and hold a contest for the best to be incorporated into matchmaking after the release. My point being that Bungie opened up this option to many people instead of the community complaining about wanting forge maps in the first place. Bungie wasn’t forced to include them in any way, they just wanted the community to be more involved.
> they just wanted the community to be more involved.
Yeah,
I mean it was a cool concept and it did work a few times in terms of a good, popular map but for the most part it was just a technique Bungie used to keep people playing Reach and keep the community going.
> > they just wanted the community to be more involved.
>
> Yeah,
>
> I mean it was a cool concept and it did work a few times in terms of a good, popular map but for the most part it was just a technique Bungie used to keep people playing Reach and keep the community going.
well it didn’t really work. All it did was motivate tons of little kids to make very weak maps and many long-time fans to leave the series for years.
> > > they just wanted the community to be more involved.
> >
> > Yeah,
> >
> > I mean it was a cool concept and it did work a few times in terms of a good, popular map but for the most part it was just a technique Bungie used to keep people playing Reach and keep the community going.
>
> well it didn’t really work. All it did was motivate tons of little kids to make very weak maps and many long-time fans to leave the series for years.
I had some fun on some of the BTB maps with a full party. It’s a bit different if your playing competitively on slayer for example as it gives you something to blame.
I agree with you
Give forgers they own Playlist. Its so annoying to play reach. Every playlist has Forge maps as a vote options. Even all 3 vote options are some forge maps i didnt even know lol
> > > > they just wanted the community to be more involved.
> > >
> > > Yeah,
> > >
> > > I mean it was a cool concept and it did work a few times in terms of a good, popular map but for the most part it was just a technique Bungie used to keep people playing Reach and keep the community going.
> >
> > well it didn’t really work. All it did was motivate tons of little kids to make very weak maps and many long-time fans to leave the series for years.
>
> I had some fun on some of the BTB maps with a full party. It’s a bit different if your playing competitively on slayer for example as it gives you something to blame.
>
> Edit: Depends what you classify as ‘works’.
well I mean it just did more harm than it did good. They should have just stayed in one playlist, but they didn’t. This caused a lot of people to not want to play anymore because the one playlist that many liked the most (Team Slayer) suddenly had a lot of maps they didn’t enjoy.
> I agree with you
> Give forgers they own Playlist. Its so annoying to play reach. Every playlist has Forge maps as a vote options. Even all 3 vote options are some forge maps i didnt even know lol
A lot of people complained about how bad the maps that shipped with the game were, but I think that in comparison to a lot of the community maps, the maps that were shipped were awesome. Haha the Forge Maps in playlists with other map options just… don’t make the game more fun IMO if someone wants to play on forge maps, they can just do it in Forge or Customs.
> > I agree with you
> > Give forgers they own Playlist. Its so annoying to play reach. Every playlist has Forge maps as a vote options. Even all 3 vote options are some forge maps i didnt even know lol
>
> A lot of people complained about how bad the maps that shipped with the game were, but I think that in comparison to a lot of the community maps, the maps that were shipped were awesome. Haha the Forge Maps in playlists with other map options just… don’t make the game more fun IMO if someone wants to play on forge maps, they can just do it in Forge or Customs.
yeah or this^^ u r right.
I could accept the changes in halo4 if im not forced to play on Forge maps in Team slayer or other playlists.
> > I had some fun on some of the BTB maps with a full party. It’s a bit different if your playing competitively on slayer for example as it gives you something to blame.
> >
> > Edit: Depends what you classify as ‘works’.
>
> well I mean it just did more harm than it did good. They should have just stayed in one playlist, but they didn’t. This caused a lot of people to not want to play anymore because the one playlist that many liked the most (Team Slayer) suddenly had a lot of maps they didn’t enjoy.
Yeah I agree with you on that.
For the more competitive and ‘focused’ playlists if you like such as Slayer and Objective then only the official and Bungie created maps should have been there.
The casual playlists like BTB however made it more enjoyable as the competitiveness didn’t have to be as focused and it also gave a variety and new taste every now and then instead of the playing the same maps over and over. For the sake of map packs on Bungie’s side I know they didn’t meet any sort of quality or standard that they would ship but it was effectively free and easy for these types of playlists.
> > they just wanted the community to be more involved.
>
> Yeah,
>
> I mean it was a cool concept and it did work a few times in terms of a good, popular map but for the most part it was just a technique Bungie used to keep people playing Reach and keep the community going.
I think it was more of a technique bungie used to be lazy and have an excuse for not making any good maps.
> > > they just wanted the community to be more involved.
> >
> > Yeah,
> >
> > I mean it was a cool concept and it did work a few times in terms of a good, popular map but for the most part it was just a technique Bungie used to keep people playing Reach and keep the community going.
>
> I think it was more of a technique bungie used to be lazy and have an excuse for not making any good maps.
I wanted to say that haha… but I didn’t want to disrespect Bungie -___-
> > > > they just wanted the community to be more involved.
> > >
> > > Yeah,
> > >
> > > I mean it was a cool concept and it did work a few times in terms of a good, popular map but for the most part it was just a technique Bungie used to keep people playing Reach and keep the community going.
> >
> > I think it was more of a technique bungie used to be lazy and have an excuse for not making any good maps.
>
> I wanted to say that haha… but I didn’t want to disrespect Bungie -___-
hahaha well there’s nothing wrong with being brutally honest…
Agreed with MajorNoobOwnage, by the way love your youtube channel, man. I really hope that Halo 4 Team Slayer is not a cesspool littered with half rate Forge World maps with kindergarden names like Think Twice.
> Agreed with MajorNoobOwnage, by the way love your youtube channel, man. I really hope that Halo 4 Team Slayer is not a cesspool littered with half rate Forge World maps with kindergarden names like Think Twice.
thanks! I love seeing my subs outside of youtube <3
> 2. The maps just… weren’t fun. It seemed like the people who submitted the maps were only focused on making maps which would win, instead of maps that the players would actually enjoy playing on. The maps were structured fairly well, but it became apparent very quickly that there wasn’t enough playtesting for them.
A 3 legged goats’ maps were amazing! Think Twice is an awesome map.
Anyways on to the topic at hand. I think community maps should be limited to 1 or 2 per playlist, and there should be no default forge maps in on Launch. The problem with Reach is the game launched with a ton of forge maps, only to have a ton more added.
So much Grey!
> > 2. The maps just… weren’t fun. It seemed like the people who submitted the maps were only focused on making maps which would win, instead of maps that the players would actually enjoy playing on. The maps were structured fairly well, but it became apparent very quickly that there wasn’t enough playtesting for them.
>
> A 3 legged goats’ maps were amazing! Think Twice is an awesome map.
> Anyways on to the topic at hand. I think community maps should be limited to 1 or 2 per playlist, and there should be no default forge maps in on Launch. The problem with Reach is the game launched with a ton of forge maps, only to have a ton more added.
> So much Grey!
I agree, up to an extent. I think that user submitted maps should still be implemented into matchmaking from time to time, but I also think that 343 and the community need to be more strict on the maps that could potentially go into matchmaking.
First, 343 should make more than one Forge World. I know that’s a drastic request, but it would solve the problem with having the same scenery. Second, community submitted maps should enter a community vote on whether or not it should be implemented into matchmaking. After a week or so of actually seeing the map in action, the map should then go into another vote on whether to keep it or not.
I love seeing my subs outside of youtube <3