So a halo game where its possible to make extremely entertaining and creative maps, gametypes, and machinimas doesnt have a working fileshare. What? How is it THAT difficult to put up the file share (which should have been up at launch) when clearly you have no other concerns at the moment about the state of this game. I shouldnt have to go on to youtube to find out the exact gamertag of the person whos fileshare i need to search to get a gametype. This is ridiculous. A week in, the fanboys used their classic “give it time” defence, and yet its been 2 months and its still not here. Garbage company, do yourselves a favor and just quit now while youre still ahead.
> So a halo game where its possible to make extremely entertaining and creative maps, gametypes, and machinimas doesnt have a working fileshare. What? How is it THAT difficult to put up the file share (which should have been up at launch) when clearly you have no other concerns at the moment about the state of this game. I shouldnt have to go on to youtube to find out the exact gamertag of the person whos fileshare i need to search to get a gametype. This is ridiculous. A week in, the fanboys used their classic “give it time” defence, and yet its been 2 months and its still not here. Garbage company, do yourselves a favor and just quit now while youre still ahead.
It will be up next month. Trust me I’m grr’d by this aswell.
A recent Halo Bulletin estimates that File Shares will be fully accessible and searchable in January.
> How is it THAT difficult to put up the file share (which should have been up at launch) when clearly <mark>you have no other concerns at the moment</mark> about the state of this game.
Incomplete list of other concerns that they have at the moment:
• Looking for more geometry holes in maps
• Dealing with promotions and related bugs
• Fixing weapon reload and cooldown bugs
• Fixing physics bugs on projectiles
• Fixing issues with the stats web app
• Investigating balance issues
• Investigating of gametype issues
• Investigating and banning of modders
• Fixing bugs when migrating maps into MM (likely cause of Haven Ordnance bugs)
• Implementing fine editing (hinted at in a CA interview, not directly confirmed)
• Implementing Campaign Theater (hinted at in a Bulletin, not directly confirmed)
:\
> A recent Halo Bulletin estimates that File Shares will be fully accessible and searchable in January.
>
>
>
> > How is it THAT difficult to put up the file share (which should have been up at launch) when clearly <mark>you have no other concerns at the moment</mark> about the state of this game.
>
> Incomplete list of other concerns that they have at the moment:
> • Looking for more geometry holes in maps
> • Dealing with promotions and related bugs
> • Fixing weapon reload and cooldown bugs
> • Fixing physics bugs on projectiles
> • Fixing issues with the stats web app
> • Investigating balance issues
> • Investigating of gametype issues
> • Investigating and banning of modders
> • Fixing bugs when migrating maps into MM (likely cause of Haven Ordnance bugs)
> • Implementing fine editing (hinted at in a CA interview, not directly confirmed)
> • Implementing Campaign Theater (hinted at in a Bulletin, not directly confirmed)
>
> :\
Also, 343 is using a Fileshare system different from Halo 3 and Halo: Reach, so there was bound to be some bugs.
apparently patience is lost on everyone I just look at this time as a beta 
thats the problem thought this so called “Beta” time should have been used BEFORE launching a broken game…oh maybe i dont know as an ACTUAL beta…seriously peoples patience being lost is justifiable
It’s a newer developer attempting to take the reins of Halo from Bungie, you can’t expect everything to transfer over perfectly. They simply tried a different engine (or something) for the fileshare system and it flopped.
Trust me, you’ll live without one for a while.
i get that…but heres the difference…also i commend you for having the patience of a saint…but the problem is 343 had a year of development, customs was a side note to them, pushed aside by matchmaking and campaign (which i think they did a phenomenal job of) But fileshare was established in halo 3…343 took over the fileshare from bungie and did a good job maintaining it
However as developers this should have been instituted, tested, refined, and thourahally figured out by now 2 months in.
Im no developer so i have no room to talk technicals…however i can say that the fileshare should not even show up, should not even be accessible,…it should have essentially an under construction sign posted for it to at least put an illusion on it and not make it feel like they arent working on it
Ive accepted the fact that it unoperational, (BUt this doesnt mean i agree with it bieng so)
Not to mention they have made NO attempt to allieviate any of the CUSTOMS CROWD
made no attempt to say “we -Yoinked!- up”
This should have been up (Or at least addressed ) 1 week into launch
Calm down.
It will be up in a month or less. Hopefully. Have patience.
Come back in a month or something.
Eat a snack, turn on the TV, and pass out from watching Law and Order.
> A recent Halo Bulletin estimates that File Shares will be fully accessible and searchable in January.
>
>
>
> > How is it THAT difficult to put up the file share (which should have been up at launch) when clearly <mark>you have no other concerns at the moment</mark> about the state of this game.
>
> Incomplete list of other concerns that they have at the moment:
> • Looking for more geometry holes in maps
> • Dealing with promotions and related bugs
> • Fixing weapon reload and cooldown bugs
> • Fixing physics bugs on projectiles
> • Fixing issues with the stats web app
> • Investigating balance issues
> • Investigating of gametype issues
> • Investigating and banning of modders
> • Fixing bugs when migrating maps into MM (likely cause of Haven Ordnance bugs)
> • Implementing fine editing (hinted at in a CA interview, not directly confirmed)
> • Implementing Campaign Theater (hinted at in a Bulletin, not directly confirmed)
>
> :\
• Looking for more geometry holes in maps - Coulda been located and fixed in a beta
• Fixing weapon reload and cooldown bugs - Coulda been located and fixed in a beta
• Fixing physics bugs on projectiles - Coulda been located and fixed in a beta
• Fixing issues with the stats web app - Coulda been located and fixed in a beta
• Investigating balance issues - Coulda been located and fixed in a beta
• Investigating of gametype issues - Coulda been located and fixed in a beta
• Fixing bugs when migrating maps into MM (likely cause of Haven Ordnance bugs)- Coulda been located and fixed in a beta
Halo 3 had a public beta; released with working file share.
Halo reach had a public beta; released with working file share.
The stuff they’re working out now, could have been worked out months ago if they had only had a public beta.
Folks can twist this into a pretzel and try to spin this all they want. You can point at all the problems side tracking them all you want. When it get’s down to the nitty gritty it just plain boils down to they would have had a better and more complete game at release if they hadn’t been so full of themselves and had a public beta to put the game through its paces, find the bugs, and get them fixed before release.
Look at the last three Halo titles released. One and two had public betas and were fully functional at release. The third didn’t and is a sloppy mess at release. 'Nuff said.
> i get that…but heres the difference…also i commend you for having the patience of a saint…but the problem is 343 had a year of development, customs was a side note to them, pushed aside by matchmaking and campaign (which i think they did a phenomenal job of) But fileshare was established in halo 3…343 took over the fileshare from bungie and did a good job maintaining it
>
> However as developers this should have been instituted, tested, refined, and thourahally figured out by now 2 months in.
>
> Im no developer so i have no room to talk technicals…however i can say that the fileshare should not even show up, should not even be accessible,…it should have essentially an under construction sign posted for it to at least put an illusion on it and not make it feel like they arent working on it
>
> Ive accepted the fact that it unoperational, (BUt this doesnt mean i agree with it bieng so)
>
> Not to mention they have made NO attempt to allieviate any of the CUSTOMS CROWD
> made no attempt to say “we -Yoinked!- up”
>
> This should have been up (Or at least addressed ) 1 week into launch
343 has existed since 2007 when it was created my Microsoft. It’s known since then that it would be making every Halo game after Bungie made two more.
They have had plenty of time to prepare.
I’m so sick and tired of folks who don’t know their history saying they’re a new company that needs a break because they didn’t have time, etc.
They have had all the time in the world and have no excuse.
They have basically understudied Halo along side Bungie for ODST and Reach, got their feet wet with Halo CEA and then did Halo 4. So it’s not like they did Halo 4 straight out of the box with zero experience.
343 was founded by Microsoft, it’s existed for five years, and large sums of money have been spent to hire brilliant minds. They have no excuse for this other than cutting corners to increase profit margins.
It’s not all powered by one big on/off switch, we just have to be patient. I’d say someone is around the clock trying to get it up and running. Don’t forget that Halo 3 and Reach had a beta so if there were any bugs they would’ve been squashed.
As far as I’m concerned, there is really no excuse for the fileshare not being up. They knew damn well that Halo 4 would be a hub of awesome maps and videos and screenshots from day 1, and they had the proven technology with 3 and Reach. I’m not a programmer, but when the coding already exists and works, I don’t see why it wasn’t implemented day 1.
Firstly, There’s ways to go about asking in a polite manner which doesn’t come across so aggressive.
The fileshare will be going live early 2013, As it wasn’t ready for release,
And rather than release a buggy unfinished feature 343 did the right thing and held it back by afew months.
Me, Personally would rather have a finished, Working feature than an unfinished one.