armageddonsnipe

I think you are wrong, anthony is resigning the 360 gamesave.com theme, and he only have a .con resigner, theme are .con than...

i'll test it gt armageddonsnipe btw i have xsata

teamspeak if more easier to use.

for leaking mod no, it could be matchmaking ban and / or file share ban but for release mod yes, this is a console ban because you do some retro-engineering onto microsoft files, and because you used retro-engineering (i dunno the spelling) to find microsoft private keys

no, the con resigner is not only for halo but for all the file, bungie only could change the hashes

even a .con will go wrong, if people with flashed console grave a halo 3 cd with the slayer , ctf ,skull etc etc moded onto, when they'll go on matchmaking...hmmm

i think forging in custom is fake...But all others looks true

I'll recomend one thing PROVE BUNGIE THEY RE WRONG! Just do some REAL mod, stop that s*** with CLONES everywhere just for proving you can mod, do some REAL mod with REAL stuff like a f*cking crazy pinball mod or i dunno but stop clones evreywhere, that's why bungie think you are kinda young boys playing with a new game

i think it is very possible, the troop hog is already on the .map file and the .con file so you should spawn some ghost al around and replace the ghost meta by the troop hog meta