Post: default_mp findings help
06-02-2011, 07:21 PM #1
Arvindian
Error… Cat invasion!
(adsbygoogle = window.adsbygoogle || []).push({});
I have recently been snooping around the 1.12 Debug default_mp.self and have found some lines that I am really confused with and need some help on what they mean.

Here are some screenshots :

You must login or register to view this content.

You must login or register to view this content.

The Most Interesting one I've found :

You must login or register to view this content.


---------- Post added at 08:21 PM ---------- Previous post was at 04:26 PM ----------

Bump, Please I need help with this, This may help us ALL!
(adsbygoogle = window.adsbygoogle || []).push({});
06-02-2011, 07:44 PM #2
Originally posted by Arvindian View Post
I have recently been snooping around the 1.12 Debug default_mp.self and have found some lines that I am really confused with and need some help on what they mean.

Here are some screenshots :

You must login or register to view this content.

You must login or register to view this content.

The Most Interesting one I've found :

You must login or register to view this content.


---------- Post added at 08:21 PM ---------- Previous post was at 04:26 PM ----------

Bump, Please I need help with this, This may help us ALL!


We can look on the default_mp.self of 1.11 and look what is changed (sorry for bad english :S)
06-02-2011, 07:47 PM #3
Originally posted by Arvindian View Post
I have recently been snooping around the 1.12 Debug default_mp.self and have found some lines that I am really confused with and need some help on what they mean.

Here are some screenshots :

You must login or register to view this content.

You must login or register to view this content.

The Most Interesting one I've found :

You must login or register to view this content.


---------- Post added at 08:21 PM ---------- Previous post was at 04:26 PM ----------

Bump, Please I need help with this, This may help us ALL!


This is interesting, but we need to be able to decode all of it. Also, the backup.gsc is probably hidden in the playstation or on the server and when it detects that a .gsc has been modified it will load that. If we can locate this backup.gsc and modify it, then modify the normal .gsc It should load the mods in the backup.gsc. Not sure how we're going to do this though... lol.

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo