Post: [1.19]Stat Limits Research + Functions
Options
06-06-2016, 06:53 AM
#1
01cedricv2
NGU Elite Lifetime Mermber
Hey NGU!
Today I´m gonna release my Research on how the Stat Limits are working on BO2 and how I couldnt un-patch them, thats why I mainly release my Research. :madsal: You´ll find all Addresses ive found near the Bottom of the Thread.
You may ask yourself, why isnt it possible to do All Client Stats on BO2, like the normal way(like on other CoDs)? Let me explain it to you with a simple Picture(Thanks to Shark for taking the Pictures of those D4nk H4x):
You must login or register to view this content.
As you can see on the Picture, in the Sv_CacheClientStatChange function (which is server-sided, if it isnt, let me know) there some "LiveStats"-Function on BO2, but on BO1, there arent. These Functions are most likely the checks, which are holding the "Stat Limits". Stat Limits should be common to you, if not, let me explain...: The Stat Limits are the Limits of the Game (for example not more then 65536 XP per Game) etc... Anyway lets get back to the topic, on BO1, all client stats should be possible to do using the GScr stat functions in a sprx or GSSC(if you use Com_EnCodeYEnc)! BO2 has those limits which i couldnt remove! Maybe youre lucky and/or skilled enough to do so, if you manage to get it to work, dont sell it as of I release my research aswell for everyone, so you should do aswell
Now we get to the good Part, the BO2 Stat Functions, associated Functions(Functions which are used by the Stat Functions) and some Client_t Offsets, I tryed and used! It is a Pastebin containing most likely everything Ive found, not included are the Functions & Sources I got from several Peoples! (Because I wont release someone elses work without their permissions
)
REMINDER: If there some incorrect ones, I would like to see you to post the right ones into here, so I can replace them!
I hope it helped you in any way
_-°Credits for helping me°-_
SC58, Shark, xCSBKx, mrdarkblue, DevOps, Krxxl, Enstone, Sabotage and everyone else Ive forgot <3
Today I´m gonna release my Research on how the Stat Limits are working on BO2 and how I couldnt un-patch them, thats why I mainly release my Research. :madsal: You´ll find all Addresses ive found near the Bottom of the Thread.
You may ask yourself, why isnt it possible to do All Client Stats on BO2, like the normal way(like on other CoDs)? Let me explain it to you with a simple Picture(Thanks to Shark for taking the Pictures of those D4nk H4x):
You must login or register to view this content.
As you can see on the Picture, in the Sv_CacheClientStatChange function (which is server-sided, if it isnt, let me know) there some "LiveStats"-Function on BO2, but on BO1, there arent. These Functions are most likely the checks, which are holding the "Stat Limits". Stat Limits should be common to you, if not, let me explain...: The Stat Limits are the Limits of the Game (for example not more then 65536 XP per Game) etc... Anyway lets get back to the topic, on BO1, all client stats should be possible to do using the GScr stat functions in a sprx or GSSC(if you use Com_EnCodeYEnc)! BO2 has those limits which i couldnt remove! Maybe youre lucky and/or skilled enough to do so, if you manage to get it to work, dont sell it as of I release my research aswell for everyone, so you should do aswell
Now we get to the good Part, the BO2 Stat Functions, associated Functions(Functions which are used by the Stat Functions) and some Client_t Offsets, I tryed and used! It is a Pastebin containing most likely everything Ive found, not included are the Functions & Sources I got from several Peoples! (Because I wont release someone elses work without their permissions
)REMINDER: If there some incorrect ones, I would like to see you to post the right ones into here, so I can replace them!
I hope it helped you in any way
_-°Credits for helping me°-_
SC58, Shark, xCSBKx, mrdarkblue, DevOps, Krxxl, Enstone, Sabotage and everyone else Ive forgot <3
The following 8 users say thank you to 01cedricv2 for this useful post:
06-06-2016, 08:01 AM
#2
Scouse Power
Knowledge is power
Originally posted by 01cedricv2
Hey NGU!
Today I´m gonna release my Research on how the Stat Limits are working on BO2 and how I couldnt un-patch them, thats why I mainly release my Research. :madsal: You´ll find all Addresses ive found near the Bottom of the Thread.
You may ask yourself, why isnt it possible to do All Client Stats on BO2, like the normal way(like on other CoDs)? Let me explain it to you with a simple Picture(Thanks to Shark for taking the Pictures of those D4nk H4x):
You must login or register to view this content.
As you can see on the Picture, in the Sv_CacheClientStatChange function (which is server-sided, if it isnt, let me know) there some "LiveStats"-Function on BO2, but on BO1, there arent. These Functions are most likely the checks, which are holding the "Stat Limits". Stat Limits should be common to you, if not, let me explain...: The Stat Limits are the Limits of the Game (for example not more then 65536 XP per Game) etc... Anyway lets get back to the topic, on BO1, all client stats should be possible to do using the GScr stat functions in a sprx or GSSC(if you use Com_EnCodeYEnc)! BO2 has those limits which i couldnt remove! Maybe youre lucky and/or skilled enough to do so, if you manage to get it to work, dont sell it as of I release my research aswell for everyone, so you should do aswell
Now we get to the good Part, the BO2 Stat Functions, associated Functions(Functions which are used by the Stat Functions) and some Client_t Offsets, I tryed and used! It is a Pastebin containing most likely everything Ive found, not included are the Functions & Sources I got from several Peoples! (Because I wont release someone elses work without their permissions )
REMINDER: If there some incorrect ones, I would like to see you to post the right ones into here, so I can replace them!
I hope it helped you in any way
_-°Credits for helping me°-_
SC58, Shark, xCSBKx, mrdarkblue, DevOps, Krxxl, Enstone, Sabotage and everyone else Ive forgot <3
Today I´m gonna release my Research on how the Stat Limits are working on BO2 and how I couldnt un-patch them, thats why I mainly release my Research. :madsal: You´ll find all Addresses ive found near the Bottom of the Thread.
You may ask yourself, why isnt it possible to do All Client Stats on BO2, like the normal way(like on other CoDs)? Let me explain it to you with a simple Picture(Thanks to Shark for taking the Pictures of those D4nk H4x):
You must login or register to view this content.
As you can see on the Picture, in the Sv_CacheClientStatChange function (which is server-sided, if it isnt, let me know) there some "LiveStats"-Function on BO2, but on BO1, there arent. These Functions are most likely the checks, which are holding the "Stat Limits". Stat Limits should be common to you, if not, let me explain...: The Stat Limits are the Limits of the Game (for example not more then 65536 XP per Game) etc... Anyway lets get back to the topic, on BO1, all client stats should be possible to do using the GScr stat functions in a sprx or GSSC(if you use Com_EnCodeYEnc)! BO2 has those limits which i couldnt remove! Maybe youre lucky and/or skilled enough to do so, if you manage to get it to work, dont sell it as of I release my research aswell for everyone, so you should do aswell
Now we get to the good Part, the BO2 Stat Functions, associated Functions(Functions which are used by the Stat Functions) and some Client_t Offsets, I tryed and used! It is a Pastebin containing most likely everything Ive found, not included are the Functions & Sources I got from several Peoples! (Because I wont release someone elses work without their permissions
)REMINDER: If there some incorrect ones, I would like to see you to post the right ones into here, so I can replace them!
I hope it helped you in any way
_-°Credits for helping me°-_
SC58, Shark, xCSBKx, mrdarkblue, DevOps, Krxxl, Enstone, Sabotage and everyone else Ive forgot <3
COD is gay but you are cool so this is geat!
The following user thanked Scouse Power for this useful post:
06-06-2016, 10:28 AM
#3
boutthatlife
Grunt
Originally posted by 01cedricv2
Hey NGU!
Today I´m gonna release my Research on how the Stat Limits are working on BO2 and how I couldnt un-patch them, thats why I mainly release my Research. :madsal: You´ll find all Addresses ive found near the Bottom of the Thread.
You may ask yourself, why isnt it possible to do All Client Stats on BO2, like the normal way(like on other CoDs)? Let me explain it to you with a simple Picture(Thanks to Shark for taking the Pictures of those D4nk H4x):
You must login or register to view this content.
As you can see on the Picture, in the Sv_CacheClientStatChange function (which is server-sided, if it isnt, let me know) there some "LiveStats"-Function on BO2, but on BO1, there arent. These Functions are most likely the checks, which are holding the "Stat Limits". Stat Limits should be common to you, if not, let me explain...: The Stat Limits are the Limits of the Game (for example not more then 65536 XP per Game) etc... Anyway lets get back to the topic, on BO1, all client stats should be possible to do using the GScr stat functions in a sprx or GSSC(if you use Com_EnCodeYEnc)! BO2 has those limits which i couldnt remove! Maybe youre lucky and/or skilled enough to do so, if you manage to get it to work, dont sell it as of I release my research aswell for everyone, so you should do aswell
Now we get to the good Part, the BO2 Stat Functions, associated Functions(Functions which are used by the Stat Functions) and some Client_t Offsets, I tryed and used! It is a Pastebin containing most likely everything Ive found, not included are the Functions & Sources I got from several Peoples! (Because I wont release someone elses work without their permissions )
REMINDER: If there some incorrect ones, I would like to see you to post the right ones into here, so I can replace them!
I hope it helped you in any way
_-°Credits for helping me°-_
SC58, Shark, xCSBKx, mrdarkblue, DevOps, Krxxl, Enstone, Sabotage and everyone else Ive forgot <3
Today I´m gonna release my Research on how the Stat Limits are working on BO2 and how I couldnt un-patch them, thats why I mainly release my Research. :madsal: You´ll find all Addresses ive found near the Bottom of the Thread.
You may ask yourself, why isnt it possible to do All Client Stats on BO2, like the normal way(like on other CoDs)? Let me explain it to you with a simple Picture(Thanks to Shark for taking the Pictures of those D4nk H4x):
You must login or register to view this content.
As you can see on the Picture, in the Sv_CacheClientStatChange function (which is server-sided, if it isnt, let me know) there some "LiveStats"-Function on BO2, but on BO1, there arent. These Functions are most likely the checks, which are holding the "Stat Limits". Stat Limits should be common to you, if not, let me explain...: The Stat Limits are the Limits of the Game (for example not more then 65536 XP per Game) etc... Anyway lets get back to the topic, on BO1, all client stats should be possible to do using the GScr stat functions in a sprx or GSSC(if you use Com_EnCodeYEnc)! BO2 has those limits which i couldnt remove! Maybe youre lucky and/or skilled enough to do so, if you manage to get it to work, dont sell it as of I release my research aswell for everyone, so you should do aswell
Now we get to the good Part, the BO2 Stat Functions, associated Functions(Functions which are used by the Stat Functions) and some Client_t Offsets, I tryed and used! It is a Pastebin containing most likely everything Ive found, not included are the Functions & Sources I got from several Peoples! (Because I wont release someone elses work without their permissions
)REMINDER: If there some incorrect ones, I would like to see you to post the right ones into here, so I can replace them!
I hope it helped you in any way
_-°Credits for helping me°-_
SC58, Shark, xCSBKx, mrdarkblue, DevOps, Krxxl, Enstone, Sabotage and everyone else Ive forgot <3
It would be better if the all clients stats did not work on bo2 as inevitably once someone does get it to work, it will load to mass derank lobbies like mw3 which sucks
06-06-2016, 06:21 PM
#4
01cedricv2
NGU Elite Lifetime Mermber
Originally posted by boutthatlife
It would be better if the all clients stats did not work on bo2 as inevitably once someone does get it to work, it will load to mass derank lobbies like mw3 which sucks
Agree, it shouldnt be public if someone get it to work, but hopefully the peeps are ripping their ass off now, as of 80% of the community are just lazyfuckers
06-07-2016, 12:02 PM
#5
BullyWiiPlaza
Climbing up the ladder
So nobody found this out yet? Surprising 
So can someone tell me already if the checks are server-sided or client-sided? According to you it therefore seems server-sided.
It would be impossible to get "unlimited" stats if the checks were client-sided.
So can someone tell me already if the checks are server-sided or client-sided? According to you it therefore seems server-sided.
It would be impossible to get "unlimited" stats if the checks were client-sided.
Last edited by
BullyWiiPlaza ; 06-07-2016 at 12:05 PM.
06-07-2016, 12:20 PM
#6
01cedricv2
NGU Elite Lifetime Mermber
Originally posted by BullyWiiPlaza
So nobody found this out yet? Surprising
So can someone tell me already if the checks are server-sided or client-sided? According to you it therefore seems server-sided.
It would be impossible to get "unlimited" stats if the checks were client-sided.
So can someone tell me already if the checks are server-sided or client-sided? According to you it therefore seems server-sided.
It would be impossible to get "unlimited" stats if the checks were client-sided.
They´re most likely server-sided,but they need to be called from somewhere! There is this one function called "actionOnBadStats", which, when you watch the pseudo-code in the PDB, drops (kicks) the client when "bad" stats have been setted. This one uses client_t to check it, so maybe it is that one!
06-07-2016, 12:48 PM
#7
BullyWiiPlaza
Climbing up the ladder
Originally posted by 01cedricv2
They´re most likely server-sided,but they need to be called from somewhere! There is this one function called "actionOnBadStats", which, when you watch the pseudo-code in the PDB, drops (kicks) the client when "bad" stats have been setted. This one uses client_t to check it, so maybe it is that one!
Hey, I noticed that setting a client's prestige kicks them but it's working fine on the host if a certain dvar is set. It might be related to the "actionOnBadStats" thing.
06-07-2016, 12:50 PM
#8
01cedricv2
NGU Elite Lifetime Mermber
Originally posted by BullyWiiPlaza
Hey, I noticed that setting a client's prestige kicks them but it's working fine on the host if a certain dvar is set. It might be related to the "actionOnBadStats" thing.
Yes i know, they getting kicked out! Im gonna look into it
06-08-2016, 09:10 PM
#9
anthonything
Space Ninja
Originally posted by 01cedricv2
Yes i know, they getting kicked out! Im gonna look into it
So by the way, think of it this way, If a client can receive stats in any interval based off of environment conditions, no matter the increment, if the environment conditions can be replicated in any means, these stats can be done in intervals with the same function. All client stats is possible, no matter the limits 3arc put in the game. Also, you may want to look into _gamerep.gsc, as that is the real clientside limitation behind the in game stats monitoring. The server side checks are relative to the client's response, so if you can find a way to override the clients scripts with your own modified response, the server will accept. Also, i have an idea, maybe find a way to create a false request for the client? Ie: set xuid to their xuid, sent a stat modification with your own modified client side check, and maybe the server will accept? Just a thought towards your research.
At this point i think im going to get into this scene. I had motivations before because i always like a challenge, and know that i understand GSC so extensively, i think it should be much easier to figure this type of stuff out.
Last edited by
anthonything ; 06-08-2016 at 09:26 PM.
The following user thanked anthonything for this useful post:
Copyright © 2025, NextGenUpdate.
All Rights Reserved.
