Editing Player Profiles

Yay I've cracked the player HS and average for batting. This was complicated but hopefully now all the others will be simular:
There are three bytes that control it: 125, 126 and 127
125 gives the HS in simple hex; the second byte of 126 also controls the HS
126 and 127 then control the average:
the first byte of 126 added to the value in 127 (in base 16). This is multiplied by 2.
The second byte of 125 now determines whether the average is odd or even. It goes as follows:
0 = average is even
8 = average is odd (add 1)
1 = average is even (add 256 to batting HS)
9 = average is odd (add 1 and add 256 to batting HS)

I know this is extremely complicated so if you don't follow don't worry. Prakash is the only one who has to understand it...
 
I've cracked the test values as well and they're even more complicated:
bytes 119, 120, 121
121 is Average
the second byte of 120 is multiplied by 16 and added to the first byte of 119. This is multiplied by 2 again.
The second byte of 119 then determines what happens next:
0 = multiply by 2
C = add one, multiply by 2, add one
4 = multiply by 2, add one
8 = add one, multiply by 2


I'm not joking. Try it if you don't believe me :P
 
Damn thats some really confusing hex stuff. No wonder I wasnt able to crack it despite trying like crazy !!!

Hopefully now Prakash will be able to put something in the player editor to change these values as well.
 
I've finished off the HS and Average values for batting:
The bytes they relate to are as follows:
Test: 119, 120, 121
ODI: 122, 123, 124
FC: 125, 126, 127
OD: 127, 128, 129

Note: All the numbers are in hex so A = 10 C = 12 11 = 17 etc


Test (119, 120, 121)

6C 03 2B

Average = 2B = 43

HS = 6C 03 {(03*16) + 6} x 2
then do the following to answer: (108) add 1, multiply by 2, and add 1 (because of the C)
= 219

The second byte of 119 (in this case C) determines what happens as follows:
0 = multiply by 2
C = add one, multiply by 2, add one
4 = multiply by 2, add one
8 = add one, multiply by 2


ODI (122, 123, 124)

24 C2 04

Average = C 04 = {(04 x 16) + C}/2
= 38

HS = 24 2 = {(2*16) + 2} x 2
then do the following to answer: (68) mutliply by 2 , add 1 (because of the 4)
= 137

The second byte of 122 (in this case 4) determines what happens as follows:
0 = multiply by 2
C = add one, multiply by 2, add one
4 = multiply by 2, add one
8 = add one, multiply by 2

FC (125, 126, 127)

DB 10 21 (the 2 belongs to OD)

Average = 10 1 = {(1*16) + 1}
then multiply answer (17) by 2 (because of the 0)
= 34

HS = DB 0
= 219

The second byte of 125 (0 in this case) determines whether the average is odd or even. It goes as follows:
0 = average is even
8 = average is odd (add 1)
1 = average is even (add 256 to batting HS)
9 = average is odd (add 1 and add 256 to batting HS)


OD (127, 128, 129)

21 11 25 (the 1 in 21 belongs to FC)

Average = 25
= 37

HS = 2 11 = {(17[11]*16) + 2}/2
= 137


Therefore M.Trescothick:

6C 03 2B 24 C2 04 DB 10 21 11 25 =
Test: Av 43 HS 219; ODI: Av 38 HS 137; FC: Av 34 HS 219; OD: Av 37 HS 137
 
hey colin i am having troubles with some players for example take Yousuf Youhana, his test HS values are D0 1C 31 so
{(28*16) + 13} * 2 = 922
since the second part is 0 i am multiplying it by 2
then 922 * 2 = 1844 :! whats this huge value or am i doing it wrong :unsure:

i have another method to find HS for test {(x/4) + (y*64)} where x and y are the decimal(not hex) vales of 119 and 120 bytes, for example
M.Trescothick 6C 03 ---->> 108 003
so his test HS will be {(108/4) + (3*64)} = 27+192= 219 :up
 
Bloomin 'eck well done Colin - you have put some hard work into this. I hope when someone does release a fully functional player editor you get some deserved credit B)
 
where can i get this player editor, im sick of replacing players
 
Originally posted by Tim@Mar 5 2004, 04:41 PM
Yeah Great Work Colin you'll be working for EA soon :lol:
Yeah send him in to bring it down and release a patch
 
I've done a little bit of work on the bowling Average and Best Bowling Innings figures.
The bytes relate as follows:
Test: 130, 131, 132
ODI: 133, 134
FC: 135, 136, 137
OD: 138, 139, 140

These are fairly approximate as there is likely to be some overlap. There is however one major problem. The figures for BBI wickets and BBI runs are messed up. In the player editor BBI wickets comes first (10 is the max you can set) and BBI runs comes second. However some players have this the wrong way round and it changes sometimes too for no reason. This is an EA bug and I need to find a way of working round it which is going to take a while...
 
whoa...we have big time scientists and mathematicians here... never thought editing a game would even lead to code cracking. Good work! :)
 
what is the latest on updating stats? this i think will be the most important feature of any player editor. i hate manually clicking esp. when they are in the thousands of runs
 
Prakash and I are working on it but I've just been away on holiday for a week and now I'll be away from my home PC for another week so progress will be slow...
 
i have finished uptill colin got it cracked, i was been busy lately so i could not research more on cracking the values
 

Users who are viewing this thread

Top