I can't find the thread, but I remember someone from bungie contacted a guy from modacity and asked him to get a bunch of custom maps together so they could take a look at them.
I think I realized why that was. We all thought it was about releasing modding tools and Halo 3 for PC, and thought they just wanted to see what the community was doing.
But then a few weeks ago I saw on the Epic Games youtube channel, that they released a new update for Unreal Tournament, with maps from the community, so it just dawned on me last night.
They were going to put custom maps on the Halo Master Chief Addition. But we, thinking they wanted to see what we could do, sent them all hugely customized maps, when they wanted to see well done, vanilla maps
So they scrapped the idea and just put the originals in
You guys think I'm correct? Or did they give an answer why?
January 28th, 2017, 02:56 AM
Ganon
Re: I think I know why bungie contacted buddy on here
If it was true, Bungie would have looked into it themselves. They are well aware all the customs we love are unprofessional, unbalanced trainwrecks. The ones that are good enough, are usually on the smaller side and ugly like tension or wizz. The sad truth is that if there were any good vanilla maps, the competitive community would have switched to custom edition 10 years ago, rather than disregard it. Perfect example being the XBC community literally making their own "MLG" maps because ours were so misguided (Visuals/Gimmicks over Gameplay/Balance). Counter-Strike is a good example of a healthy modding community over time, considering many custom maps were adopted by valve themselves.
January 28th, 2017, 11:19 AM
malolo420
Re: I think I know why bungie contacted buddy on here
Don't you kinda think that is them doing their own little look into it. My guess is one person there was like "Hey why don't we add some community maps?" So they agreed and said, get us some maps to take a look at and maybe we can. But then yeah...
What do you think that person from Bungie contacted buddy for?
February 1st, 2017, 12:25 PM
SirBobbington
Re: I think I know why bungie contacted buddy on here
I think the possibility of custom maps for the next Halo was brought up on here, but I doubt Bungie ever really entertained the idea. I'm not fully sure how copyright law applies to mods, but they would probably have to obtain permission from the mapper to use a custom map. Most of us are nothing but screen names, and pretty much all of us have moved on. Tracking down the likes of Mothergoat or DocOc would be a nightmare, but they could come out of the woodworks with a lawsuit if Bungie used their IP without permission.
I don't think they could have done it themselves, either. HaloMaps is the only central repository left, and it's so ridiculously out of date it's not funny anymore. Plus, if you go by top downloads, or top rated or whatever else, you are still going to get an 80/20 split between gimmicks and legitimately solid gameplay.
There were some legitimately good (vanilla, balanced, reasonably sized) maps in the olden days. It just makes me plain sad that most will probably never be played again.
February 1st, 2017, 01:31 PM
Lightning
Re: I think I know why bungie contacted buddy on here
Bungie would not have contacted us;
343 Industries would have.
February 2nd, 2017, 12:22 AM
t3h m00kz
Re: I think I know why bungie contacted buddy on here
Quote:
Originally Posted by Ganon
the customs we love are unprofessional, unbalanced trainwrecks. The ones that are good enough, are usually on the smaller side and ugly like tension or wizz. The sad truth is that if there were any good vanilla maps, the competitive community would have switched to custom edition 10 years ago, rather than disregard it.
well and there's the cases of the horrendously broken in-game networking and busted tick rate
stunt_man's servers are about as competitive as it can get without some major third-party hacking to get the game into a competitively viable state. I did a little work for him to re-implement descope as a matter of fact. problem being it's all hacky tag work rather than actual code fixes because my coding experience is extremely limited.
ignore the shitmarkers. that's me fucking around with optic.