Halo 2 Forum
This topic has moved here: Subject: SNAZZY POST TITLE! READ ME! WOOO!
  • Subject: SNAZZY POST TITLE! READ ME! WOOO!
Subject: SNAZZY POST TITLE! READ ME! WOOO!
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Good point/question. I don't think it would work for the old maps b/c they are on your H2 disc, but for the 9 maps released in '05, that could be something to look into.

  • 05.10.2007 8:51 AM PDT

Achronos told us that these maps were made with being able to be patched specifically in mind, so that's the official line.

  • 05.10.2007 9:00 AM PDT
  •  | 
  • Elder Mythic Member

anyone who's played more than you has no life

anyone who's played less than you is a noob

Posted by: ThreeShot
They most likely just don't want to do it.


Highly unlikely.

Since i'm not [and I presume you are not] a computer games programmer I don't think we should say whether or not Bungie is able to patch the older maps. All we do know is Certain Affinity created these maps with the intention of being able to patch them soon after release. Bungie didn't create their maps with the same intentions.

  • 05.10.2007 9:14 AM PDT

"I'm a 40 in Team Spelling, but I have the most worstest time leveling up in Team Superlatives."

The thing is, there ARE ways to change things about the maps on the disk. For example, there was a hole on the Zanzibar sea wall that they went in and patched so you wouldn't fall through it. Therefore, a death wall could be put at the top of all maps to stop superbouncing.

On Tombstone, wasn't part of the problem a wall that could be shot through one way and not the other? Even if you couldn't add a death wall, couldn't one of those be added to dome each level? A person could still superbounce out and not be able to shoot you, but you could shoot them. Thoughts?

  • 05.10.2007 11:20 AM PDT

Chillin' without a crush

Sure it's possible, but seeing as it took over 2 weeks to fix a couple of glitches in one map, it would take forever to update and rebuild all those maps. Adding "death-barriers" on the ceilings of all the maps would take a tremendous amount of programming, a ton of time, and even more testing. At the average rate of 2 weeks per map, we're looking at 6 months or so.

So all Bungie would have to do is push Halo 3's release date back from November to summer of 2008. In exchange we get a limited improvement in game that's going to be abandoned within a few months of Halo 3's release anyway. Doesn't seem very likely.

  • 05.10.2007 11:58 AM PDT

RIP Halo 2.

Superbounces are a per-map problem. To replace all the maps would probably require a new update in order to get the game to run the old maps from the hard drive instead of the disc. So there's a decent chunk of time they need to spend to do that. Then there's a the matter of fixing the superbounces, lord knows how long that'll take, it took a while just for these two maps.

But let's magically assume they can do all that really easily. This means roughly a gigabyte of data will need to be downloaded (assuming only the playable map files are replaced and not the mainmenu, shared, and sp_shared). Now, on your run of the mill 768Kb DSL connection, that's about 3 hours of straight downloading. Now, think about the cost of the bandwidth alone for 1GB of data to each person. It's a lot of money. And now consider the servers and connection speeds required to distribute 1 gigabyte of data to each person who plays Halo 2.

  • 05.10.2007 12:02 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

if some random kids can figure out that death walls could work, dont u think bungie wouldve already thought of this as well? being that computer programming is their job? theyve had almost 3 years to tinker with these maps, if that was a feasible solution, they would have done it already

  • 05.10.2007 12:03 PM PDT

"I'm a 40 in Team Spelling, but I have the most worstest time leveling up in Team Superlatives."

To the three guys above this...I realize it would take time, but I think that your estimation of how much time it would take and how much memory a patch would take may be grossly overexaggerated.

For one, I'm not saying remove the superjumping spots or the physics themselves...I'm saying put in a death or "can't shoot through" barrier to make superjumping not worthwhile.

If the numbers you threw out about time to program and memory space were true, then yes, it wouldn't be worth it to anyone. However, what if it were a smaller download and took, say, two weeks? I mean, in most cases you'd just have to put a horizontal plane across the level's top. That's why I posted...hoping for an answer to those very questions.

  • 05.10.2007 12:42 PM PDT

Chillin' without a crush

It's not quite that simple unfortunately. The most recent map pack is a very good example. Certain affinity spent a lot of time designing and testing these maps, and they still were "flawed" enough to require a complicated fix. That was a crew of something like a dozen guys working for months.

I understand that the current Halo 2 maps are already done, but any project that would involve "tinkering" with these maps is incredibly complicated. With programming and design of this nature, it takes a little more than simply sticking in a ceiling on top of these levels. In order to ensure that changing the maps didn't "break" anything else would require a strenuous amount of testing. When you factor in the man-hours this could potentially take, it wouldn't be cost effective no matter how long it took to get it released.

And once again, who is going to pay for such a complicated task? Unless you want to pay $15 to redownload the same maps we've had for a couple of years now, it's just not in the realm of possibility.

  • 05.10.2007 3:45 PM PDT

"I'm a 40 in Team Spelling, but I have the most worstest time leveling up in Team Superlatives."

Posted by: medpimp
It's not quite that simple unfortunately. The most recent map pack is a very good example. Certain affinity spent a lot of time designing and testing these maps, and they still were "flawed" enough to require a complicated fix. That was a crew of something like a dozen guys working for months.

I understand that the current Halo 2 maps are already done, but any project that would involve "tinkering" with these maps is incredibly complicated. With programming and design of this nature, it takes a little more than simply sticking in a ceiling on top of these levels. In order to ensure that changing the maps didn't "break" anything else would require a strenuous amount of testing. When you factor in the man-hours this could potentially take, it wouldn't be cost effective no matter how long it took to get it released.

And once again, who is going to pay for such a complicated task? Unless you want to pay $15 to redownload the same maps we've had for a couple of years now, it's just not in the realm of possibility.


It took that crew of a dozen months to make the maps...it took a few days to FIX them.

Obviously it's not cost effective, but let me give you an example. Three days ago my car broke down, and today I found out it is going to take a $3000 fix. The warranty ran out a few months ago, but the problem was documented BEFORE the warranty ran out. Legally, GM doesn't have to help me in any way, but ETHICALLY, they have the duty to help me, as a customer, get a superior product.

I feel similiarly about Bungie fixing the maps. Bungie has something else to move onto that we are all excited about, so obviously the attention should go elsewhere (the warranty expiring). However, problems with superbouncing occured DURING the peak of Halo 2 usage (before the warranty expired). I would be willing to risk needing another "repair" (adding a death roof) to the maps knowing that at least we were moving in the right direction.

I know that isn't a 100% fit analogy. :-)

Still, I know they don't HAVE to do anything...but they SHOULD.

  • 05.11.2007 2:28 PM PDT

"I'm a 40 in Team Spelling, but I have the most worstest time leveling up in Team Superlatives."

Alot of good it's seemed to have done you.

  • 05.20.2007 11:32 PM PDT
  • gamertag:
  • user homepage:
  • last post: 01.01.0001 12:00 AM PDT

Posted by: Havok Se7en
Super bouncing is cool. ur just sayin that because u cant bounce like everybody els can


No, its cheating and unfair.

On Ascension, the bounce on Big Tower is easy, then grab a sniper and Rocket before you go, even a BR would work. Its camping up high, the only person down there that can kill him is the other sniper.

  • 05.21.2007 7:33 AM PDT
Subject: SNAZZY POST TITLE! READ ME! WOOO!

"I'm a 40 in Team Spelling, but I have the most worstest time leveling up in Team Superlatives."

This may be best for the Halo 2 forum, but because it has to do with online multiplayer and the recent updates I'll put it here.

Question:

If Bungie or Certain Affinity can put in coded "death walls" and remove superbounce spots from the new maps, why can't a patch be made to eliminate the superbounce from matchmaking? (at the minimum just put death walls that apply to the older maps)

I'm not trying to be a jerk about it...I was really wondering why not. I would appreciate intelligent feedback on this topic. Thanks!

EDIT: 1) There ARE ways to change things about the maps on the disk. For example, there was a hole on the Zanzibar sea wall that they went in and patched so you wouldn't fall through it. Therefore, a death wall could be put at the top of all maps to stop superbouncing.

2) Even if they didn't want a death wall at the top of all maps, there IS another solution...on Tombstone, wasn't part of the problem a wall that could be shot through one way and not the other? Even if you couldn't add a death wall, couldn't one of those be added to dome each level? A person could still superbounce out . However, let couldn't shoot through to you, but you could shoot them. Thoughts?




[Edited on 05.10.2007 11:22 AM PDT]

  • 05.10.2007 8:40 AM PDT

"I'm a 40 in Team Spelling, but I have the most worstest time leveling up in Team Superlatives."

Disregard...continue discussion.

[Edited on 05.21.2007 8:00 AM PDT]

  • 05.21.2007 7:55 AM PDT