- last post: 01.01.0001 12:00 AM PDT
Poll: Agree? [closed]
| I Can't Read:
13%
|
|
(4 Votes)
|
Total Votes: 30
Halo 1 and Halo 2 had no RSA Map Encryption.
Halo 1 had no map protection while Halo 2 had a simple CRC Checksum. Without a doubt Halo 1 and 2 were the best community driven games. showing sites like iBotModz, se7ensins and HaloMods coming out to say "Hai".
But Halo 3, it used an amazing RSA encryption. How this works, there is a Private Key and a Public Key. The Public Key is in your xbox that checks if the file had been resigned with the Private key. The Private key is inside Bungie and they resign the maps before release. Now, why the -blam!- are you using this stupid peice of -blam!-?
This is an amazing example of Halo 2 modding.
Why don't bungie go back to the cool Bungie, and stop being the pricks Microsoft made them? I still play Halo 2 mods on XBC with friends, it's easily more fun and more customizable than Forge. Even though Forge is sick ;).
Now, the reason Bungie and the rest of the community hate modders is because they cheat. NO. This is wrong! Modders make amazing maps, amazing varients and the community fun that Halo thrives off. Cheaters on the other hand, manipulate the game to get a 50 or something stupid. Hate them, no us.
So, Bungie. Here is an idea.
Matchmaking: Have a RSA map encryption check, if you fail this check kick them out of matchmaking lobby and ban them till they remove the mods (Simalar to Halo 2).
Custom Games/Forge: Have no check, let the community have fun, and also, remove that thing, if you have a diffrent .map people can't join and stuff.
Campaign: Disable achievements if the RSA check has registered a faulty .map.
Now Bungie, read this and think. Do we want the community to have fun again? Do we want to kick ass again? Do we want to take over the world again? And Kick CoD in the ass?
What was that? You do? Yeah, i thought so. :)
[Edited on 10.04.2009 8:06 AM PDT]