(adsbygoogle = window.adsbygoogle || []).push({}); Well I'm sure many of you have seen this thread: You must login or register to view this content.

I did too, but I don't think that is what IW has done. As many of you know, when the 1.12 patch came out for MW2 it prevented GSC modding by encrypting the GSC's into the default_mp.self. CFG mods still worked, however, because the default_mp didn't have the cfg files encrypted into them. For those who don't know, Modern Warfare 3 uses the same encryption for it's fastfiles as mw2 did, and I along with many others have already opened up the patch and found nothing there except localized strings. There are 2 possible explanations for this:
1. The GSC's are in there but have a new encryption key.
2. The GSC's are only present in the default_mp.self.

We will be able to mod localized strings in the .ff files, but as it stands out it looks like mw3 will be hack-free for a while.

Please take this at face value as the game isn't even out yet and this is all speculation, I just thought I'd share my thoughts on how I think hacking is prevented in this game :angel:

Hope this helped some of you out

That's not how IW patched GSC modding. They're not inside the default_mp.self.

Your sig is soooooo true.

:carling: I luv u babe

For one, online play isn't hackable at the moment due to firmware restrictions... But nothing is completely "unhackable" unless all the data is stored on their own servers instead of on our consoles, which will probably not happen for a long time.

I dont think our user data is stored on the servers initially, when youve been playing for a while and rank up , ive noticed when you look at the leaderboard your stats will stay the same as they were when you first logged in , i think the data is uploaded at the end of a session ie when you quit the game, this patch anyway. definitly exploitable , someone with the knowledge could possibly inject modified data into the user data with a modded ps3 using the ps3 file browser, as long as it were running as a background service while MW£ was running.

then care to explain where? eboot?

They removed the MP GSC compiler from the executable.

haha and i always thought the key lays in the default_mp