Jump to content

cbox


Reach mods

halo3

By halo3
in Reach Modding

 Share

Recommended Posts

halo3 Gunnery Sergeant Grade 1

halo3

Posted
Posted

Lol crappy quality since I don't have a capture card, but besides that what do you think?

http://www.youtube.com/watch?v=a2ClmrObO2U

http://www.youtube.com/watch?v=jUqOGPSk1J8

  • Like 1
Quinn Colonel Grade 3

Quinn

Posted
Posted
It seems like a lot of company's today are not learning from their mistakes. I mean, if Reach is already modable, thats pretty much a fail for Bungie.
jmdalmighty Lietenant Grade 2

jmdalmighty

Posted
Posted

Not rly as they have not finished the game so it's not a fail.

Also if someone is just having fun and desicedes to recod it I doubt it for prase so no need to be flamming someone for something they haven't done something wrong

iBotPeaches General Grade 6

iBotPeaches

Posted
Posted

It seems like a lot of company's today are not learning from their mistakes. I mean, if Reach is already modable, thats pretty much a fail for Bungie.

 

Any company is setup for this, and its not really their fault. I will break it down.

 

The introduction of devs/jtags allows for anyone to run an unsigned XEX (something Bungie has no control of), thus all restrictions they put on in place (such as RSA checks) are useless since anyone can remove them and continue to play. The people to blame would be Microsoft. If they could step up the encryption/security on their XEXs then I bet this wouldn't happen. Something like making them next to impossible to decompress and recompile would be one option, but I think all that information is hard-coded into the 360 firmware way beyond any firmware update.

 

Bungie has had the .map structure for 10 years now with minor changes on every version. That means that once the XEX is cracked, and .maps can be edited we already have a headstart from H1, H2, H3, ODST. Other games have strange files that no one maps out, thus modding is limited. I hope that made sense.

Rogue Modder Lietenant Grade 4

Rogue Modder

Posted
Posted (edited)

Any company is setup for this, and its not really their fault. I will break it down.

 

The introduction of devs/jtags allows for anyone to run an unsigned XEX (something Bungie has no control of), thus all restrictions they put on in place (such as RSA checks) are useless since anyone can remove them and continue to play. The people to blame would be Microsoft. If they could step up the encryption/security on their XEXs then I bet this wouldn't happen. Something like making them next to impossible to decompress and recompile would be one option, but I think all that information is hard-coded into the 360 firmware way beyond any firmware update.

 

Bungie has had the .map structure for 10 years now with minor changes on every version. That means that once the XEX is cracked, and .maps can be edited we already have a headstart from H1, H2, H3, ODST. Other games have strange files that no one maps out, thus modding is limited. I hope that made sense.

 

To add on, Bungie did do something against this. They encrypted the tagid's, but we already managed to figure out how. Since Halo 2's Disaster with Matchmaking (Cheating) mods, Bungie have been the only games company ahead of the game and introducing Server side SHA-1 and MD5 .map file checks. This will check if your map is 'Corrupt' (modded), if so fail to laod and try another map from the hopper. And in custom matches with other players the xex will check the ashes so you can't play with them.

 

 

Slip he's just showing what he has done no need to be negative

 

Dun talk abut teh slipstreams liak tht. k.

 

 

...and still have money for a bj.

 

I was gonna say get a girlfriend, but then i was like. nop they cost alot more. ;x

Edited by Dakote
  • Like 1

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...