Rumor: Modders accidentally leak Halo 3 information? Options

[Xbox-Scene]

Rumor: Modders accidentally leak Halo 3 information? Posted by XanTium | May 18 20:27 EST | News Category: Xbox360

From gamesradar.com: [QUOTE] A Halo modding community has accidentally made various hidden game files public, found by retrieving hidden data in the Halo 3 Beta code. Before we go any further, a warning: the following are in no way official or confirmed features of Halo 3. * New equipment: Instacover ; Smoke (suggested this might be a smoke grenade?) ; Jammer * New vehicles: Chopper ; Pelican ; Shadow * New weapons: Flamethrower ; Claymore Grenade * New mode: Infection (described as "Destroy the Flood or become infected. Score points for killing flood or big points for infecting a human. The player with the most points wins." * New rankings: The highest rankings are now Killpocalypse and Killionaire, instead of Double Kill and Triple Kill. * A reference to a map editor has also been found, a returning feature from Halo 2. [/QUOTE] News-Source: gamesradar.com

[flashfreak]

Smoke Grenade, maybe. Jammer? I reckon, and that would be very cool.

Chopper? Maybe. Pelican? Probably not player drivable. Shadow? Doubt it, thats the covenant ship i think.

Flamethrower? What a joke Its been there since Halo 1. Claymore? Yes, its been in the vids.

Infection Mode? Mad!

Kill Rankings? Meh, nothing really wrong with the current setup.

Map editor? Could be very interesting. If it suttin like Far Cry's then that could be cool, but could also change it a bit

[Tural]

The information is not confirmed.
The information should not have been public.
It is unreleased information.
The stories on all these sites should not have been published.
The information was removed from our site (Halomods) at least three days ago.
Again, none of this is confirmed.
It's in very bad taste that sites are publishing this story, as it is mainly fictitious and creating a massive amount of false beliefs and rampant speculation without any type of proof at all. On top of that, Halomods has crashed from the traffic and there wasn't even information on the site. I'm appalled, as is the rest of the community, at the people publishing these stories on various sites without any judgment about the sources or thinking about the repercussions.


This post has been edited by Tural: May 19 2007, 01:32 AM

[telo{+}]

It's in very bad taste that sites are publishing this story

I'm appalled,

Sorry buddy, but its time to grow up

Its not up to YOU to decide whats news. Its the readers job and since this is one more then one site its pretty clear the readers want to know. How about you go wag your finger on one of the many other sites.

If Bungie didn't want to people to know they should have removed all references. Also, if these kids in question didn't release it some one else would have.




I hope flamethrower is a joke.... its an outdated weapon now.... maybe it comes around and is retro-cool in the future ?

[Master Reefed]

I'm appalled, as is the rest of the community, at the people publishing these stories on various sites without any judgment about the sources or thinking about the repercussions.

what kindve "repercussions" could come from publishing a "halo hyped" BS story about modders on an xbox-scene?

This post has been edited by Master Reefed: May 19 2007, 01:45 AM

[PrismSub5]

If Bungie didn't want to people to know they should have removed all references.

Actually, many (read:all) developers leave unused stuff on disc's/demo's, its way too much work to filter every bit that is unused.

This post has been edited by PrismSub5: May 19 2007, 02:03 AM

[Tural]

what kindve "repercussions" could come from publishing a "halo hyped" BS story about modders on an xbox-scene?

Primarily the fact that the site is now down due to the massive traffic over information that no longer exists and the fact that people are taking this to be confirmed information and are citing the maps as the factual basis. It is creating false speculation.

[Mr007]

Its shit like this that piss off bungie and M$.Lets hope they dont cut the beta short or start banning more people soon.

[mckenn88]

I thought X-S was known for only publishing valid and referenced news stories. This is a big letdown that some "heresay" was put on the homepage. I don't and will not believe any of this until an official statement has been made.

[eldritch2k4]

Maybe it's me, but can't anything be left alone? Whatever happened to opening the box, putting the game in, and being surprised?

And how the hell do you "accidentally leak" information like that? There's nothing accidental about putting information that hasn't been released by the official source out in the open like this.

[Agent ME]

Accidental? Leak? Appalling?

How do those describe this?

It wasn't accidental - you don't accidentally open up a file in a hex editor and look for strings.

It wasn't a leak - that would imply that someone who was under an NDA or whose job relied on something squealed - this is all information from the public beta.

Appalling? I'd say keep it up - I want to know what other things or references are hidden in the beta.


It's not like it was impossible for Bungie to prevent this - they could've easily removed all the strings not pertaining to the demo, or put simple encryptions on the strings.

This post has been edited by Agent ME: May 19 2007, 02:58 AM

[Tural]

Accidental? Leak? Appalling?

How do those describe this?

It wasn't accidental - you don't accidentally open up a file in a hex editor and look for strings.

It wasn't a leak - that would imply that someone who was under an NDA or whose job relied on something squealed - this is all information from the public beta.

Appalling? I'd say keep it up - I want to know what other things or references are hidden in the beta.
It's not like it was impossible for Bungie to prevent this - they could've easily removed all the strings not pertaining to the demo, or put simple encryptions on the strings.

Agent ME, we were clear that we would not allow the discussion about leaked information after we saw what had happened on the Bungie forums. Bungie staff got involved, was not happy one bit, and we respected that by removing the information from the site. Just because we're modders doesn't mean we don't respect Bungie. They didn't want the information up there, we did the right thing and removed it.

As for you saying it wasn't leaked: Just because the beta is public does not give anyone permission to publish information that was not public. The content was not accessible via the game itself, it was only accessible by sifting through the map files in hex. While it is technically not illegal to put it up, it was not appreciated and we took it down, as Bungie wanted.

mckenn88, exactly. The information is just that, rumors. It is not confirmed, and thus not a good story to publish. As I stated, it is causing unjustified speculation about something which comes from unreliable sources.

This post has been edited by Tural: May 19 2007, 03:07 AM

[Agent ME]

Oh, Bungie got involved directly?
Then disregard what I was saying mostly. I'd figured they'd expect us to comb the files after Halo 2 I'm disappointed Bungie didn't prepare for this.

This post has been edited by Agent ME: May 19 2007, 03:30 AM

[ssj4android]

I thought X-S was known for only publishing valid and referenced news stories. This is a big letdown that some "heresay" was put on the homepage. I don't and will not believe any of this until an official statement has been made.

Remember that Ninja mod thing? Remember the claim that we'd be able to run Xbox 1 homebrew on the 360? Did any of that ever happen?
Anyway, nothing wrong with reporting this stuff IMO.
I thought the Claymore grenade was already in the the beta.

[90CelicaST]

Guys, I think that the story on the front page should be updated to go along with the source, which states:

The information has since been removed from the forum in question.

This post has been edited by 90CelicaST: May 19 2007, 05:26 AM