Post: [THEORYS] GSC Mods on 1.13+
Options
06-25-2012, 12:49 PM
#1
Roy944
Grunt
1 :
1) Have a default_mp.self on 1.0
2) Have a default_mp.self on 1.13
3) Decrypt 1.13 SELF and find the "version"
4) Copy the version of the SELF and past it on 1.0
5) Now you can connect with 1.0 SELF with 1.13 clients and USE player_sustainammo; GSC Mods etc...
6) Enjoy
2 :
1) Create a CFG Patch
2) Add command "fs_game "/dev_hdd0/mods/";
3) Add your scripts on /dev_hdd0/mods/
4) Add vid_restart or devmap command to recompile scripts
5) Enjoy.I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
The following 2 users groaned at Roy944 for this awful post:
06-25-2012, 03:37 PM
#2
FuntCase
Mario!
Originally posted by Roy944
Hi everybody i have some theorys to bring back 1.11 Mods on 1.13+ and above.
1 :
2 :
I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
1 :
1) Have a default_mp.self on 1.0
2) Have a default_mp.self on 1.13
3) Decrypt 1.13 SELF and find the "version"
4) Copy the version of the SELF and past it on 1.0
5) Now you can connect with 1.0 SELF with 1.13 clients and USE player_sustainammo; GSC Mods etc...
6) Enjoy
2 :
1) Create a CFG Patch
2) Add command "fs_game "/dev_hdd0/mods/";
3) Add your scripts on /dev_hdd0/mods/
4) Add vid_restart or devmap command to recompile scripts
5) Enjoy.I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
second theory is all well and good except that the gsc compiler was removed
The following user thanked FuntCase for this useful post:
06-25-2012, 03:41 PM
#3
GE90
< ^ > < ^ >
Originally posted by Roy944
Hi everybody i have some theorys to bring back 1.11 Mods on 1.13+ and above.
1 :
2 :
I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
1 :
1) Have a default_mp.self on 1.0
2) Have a default_mp.self on 1.13
3) Decrypt 1.13 SELF and find the "version"
4) Copy the version of the SELF and past it on 1.0
5) Now you can connect with 1.0 SELF with 1.13 clients and USE player_sustainammo; GSC Mods etc...
6) Enjoy
2 :
1) Create a CFG Patch
2) Add command "fs_game "/dev_hdd0/mods/";
3) Add your scripts on /dev_hdd0/mods/
4) Add vid_restart or devmap command to recompile scripts
5) Enjoy.I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
why dont you try it?
06-25-2012, 03:50 PM
#5
Uk_ViiPeR
Meh
Originally posted by Roy944
Hi everybody i have some theorys to bring back 1.11 Mods on 1.13+ and above.
1 :
2 :
I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
1 :
1) Have a default_mp.self on 1.0
2) Have a default_mp.self on 1.13
3) Decrypt 1.13 SELF and find the "version"
4) Copy the version of the SELF and past it on 1.0
5) Now you can connect with 1.0 SELF with 1.13 clients and USE player_sustainammo; GSC Mods etc...
6) Enjoy
2 :
1) Create a CFG Patch
2) Add command "fs_game "/dev_hdd0/mods/";
3) Add your scripts on /dev_hdd0/mods/
4) Add vid_restart or devmap command to recompile scripts
5) Enjoy.I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
devmap = lags out for ps3.
vid_restart = restarts the cinematic.
06-25-2012, 06:16 PM
#6
Taylor
Former Black Knight.
Originally posted by Roy944
Hi everybody i have some theorys to bring back 1.11 Mods on 1.13+ and above.
1 :
2 :
I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
1 :
1) Have a default_mp.self on 1.0
2) Have a default_mp.self on 1.13
3) Decrypt 1.13 SELF and find the "version"
4) Copy the version of the SELF and past it on 1.0
5) Now you can connect with 1.0 SELF with 1.13 clients and USE player_sustainammo; GSC Mods etc...
6) Enjoy
2 :
1) Create a CFG Patch
2) Add command "fs_game "/dev_hdd0/mods/";
3) Add your scripts on /dev_hdd0/mods/
4) Add vid_restart or devmap command to recompile scripts
5) Enjoy.I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
:dumb: How do u expect us to decrypt the .self for black ops when we can't even decrypt the Mw2 one :lol:
06-25-2012, 06:29 PM
#7
247Yamato
< ^ > < ^ >
Theories.... I simply think that if you link the USB 3.0 to the PS3 pad and stick the controller to the tv receptor, you could easily mod in 1.13, put be sure to bypass with the jailbreak mod unless you want the xbox to break. A ps3 broken is a lot of money for repairing ftw so load the PaTcH carefully or crash the screen with black screen which is annoying. In conclussion, load the mod fast and use a class with scar-h and usp45, if not console bypass will fail.
The following 6 users say thank you to 247Yamato for this useful post:
06-25-2012, 08:53 PM
#8
TheFallen
Former Dark Night
Originally posted by Roy944
Hi everybody i have some theorys to bring back 1.11 Mods on 1.13+ and above.
1 :
2 :
I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
1 :
1) Have a default_mp.self on 1.0
2) Have a default_mp.self on 1.13
3) Decrypt 1.13 SELF and find the "version"
4) Copy the version of the SELF and past it on 1.0
5) Now you can connect with 1.0 SELF with 1.13 clients and USE player_sustainammo; GSC Mods etc...
6) Enjoy
2 :
1) Create a CFG Patch
2) Add command "fs_game "/dev_hdd0/mods/";
3) Add your scripts on /dev_hdd0/mods/
4) Add vid_restart or devmap command to recompile scripts
5) Enjoy.I saw that E3 Team patched the EBOOT.BIN of 1.13 MW2. Wich means that they can patch 3.60+ apps.
But ... i saw that they ONLY patched the EBOOT.BIN; the default_mp.self is basically the retail version (1.0)
Basically it does nothing ... anyone could patch this that way because, you just take the 1.12 eboot and 1.0 default_mp.self and add 1.13 on the SFO.
I know that E3 are not noobs, but they did it wrong.
First one won't work because each default_mp.self (update) runs on a different server so you would need all of the server addresses ect. And the second one wouldn't work because fs_game is read only plus the engine no longer runs .gsc files as .gsc.
The following user thanked Cmd-X for this useful post:
06-25-2012, 09:09 PM
#10
Roy944
Grunt
Originally posted by TheFallen
First one won't work because each default_mp.self (update) runs on a different server so you would need all of the server addresses ect. And the second one wouldn't work because fs_game is read only plus the engine no longer runs .gsc files as .gsc.
Are you telling me that everytime they update the game, they buy a different server ?
---------- Post added at 04:09 PM ---------- Previous post was at 04:06 PM ----------
Originally posted by ViiPeR
devmap = lags out for ps3.
vid_restart = restarts the cinematic.
vid_restart = restarts the cinematic.
devmap = Simply reload ENTIRELY the map and turn sv_cheats to 1 (oh and btw, no one can join you, the game will reject ANYONE. (saw it on the minicon))
vid_restart = doesn't even work on PS3, i tried it.
The following user thanked Roy944 for this useful post:
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
