Editing Player Profiles

[barmyarmy]

Can you post a screen of what you've changed.

 

[sid_19840]

Can you post a screen of what you've changed.

Hmm,well I changed that byte number for a created player(originally 00) to 10.I feel Im not understand some part of this.

btw are the calculations you mentioned stored in that single byte of two digits?

 

[barmyarmy]

10 in hex isn't a proper value for this in binary so it won't work.

 

[sid_19840]

10 in hex isn't a proper value for this in binary so it won't work.

Actually 10 is a valid hex value.

After it goes frm 00 to 0F,it moves to 10 to 1F...

But anyway I can understand what you mean.

 

[Cricketman]

hey guys, do you know where i could get a hex editor?

 

[barmyarmy]

There's plenty of freeware ones around. I use Hackman, Sid uses hex workshop. Just google it.

 

[sid_19840]

ok,Im trying to crack all the stats values in the small amount of free time that I have atm.

The number of test inning's is controlled by byte number 22 and 23.

The relationship is pretty simple.Its just the hex conversion of the decimal value.

Eg: Ponting 148 Test Innings.

Thus the byte number is the hex value of 148 i.e 94.(in this case byte 23 is 00)

The two bytes 22 and 23 can be combined in the following way.

If 22 and 23 is 40 01,then the no of test innings is 0140=320

40 02=0240 i.e 576 etc.

So that means that the max no of test inns possible is FFFF=65535.

------------------------------------******************---------------

The next couple of bytes i.e 24 and 25 work in the same exact fashion but it contol's NO(Not out's) in tests.

I treid giving my player 288 not out's.

So I simply calculate the hex value of 288=120 i.e 0120

and I put these values for bytes 25 and 24 resp.

So bytes 24 and 25 look like 20 01.

So the limit in this case is FFFF as well i.e 65535

----------------------8888888888888888888888---------------------------

ok,so the next couple of bytes 26 and 27 work the same way :happy,this time controlling no. of over's bowled by a bowler in tests.

So I tried putting 12345 overs(lol),so simply the value is 3039.

Thus I put bytes 26 and 27 as 39 30.

--------------------------------------------------------------------------

Im pretty bored of explaining the same analogy again.So I wont .

Thenext couple of bytes 28 and 29 stand for Test Wickets.


30 31 -No of runs conceded by bowler in tests (i.e the R attribute for Bowler's)

Btw the average,stike rate etc seem to take care of itself.

I tried having my player with 12345 overs,23456 wickets and 34567 runs conceded(I know that's a lot ),and the avg,stk rate etc were all in place.

32 33-No of runs scored in tests(batting).

--------------------------------------------------------------------------

Byte 34 control's the number of 50's scored by a batsman in tests.

So the limit for this byte is FF=255.

Similarly byte 35 contol's the number of 100's in tests.(this is quite obviously is also limited to 255).

--------------------------------------------------------------------------

Bytes 36 and 37 once again work with the initial analogy,controlling the no. Of catches(Ct) in tests.

--------------------------------------------------------------------------

 

[sid_19840]

k,I need some help now.

I cant find how bytes 38,39..42 work,they all seem to edit thing's like matches played,5 wicket hauls etc,but I cant find the mathematical relation.
So could someone(Colin or Prakash) have a look at these bytes.

Here are some other stuff Ive found meanwhile.

byte number 42 and 43-control's no if ODI innings.

44 and 45 control Not Out's in ODI's

46 and 47 control No. of overs bowled in odi's

48 and 49 control No. of ODI wickets in odi's

50 and 51 control No. of Runs conceded in odi's(bowler)

52 and 53 control No. of Runs scored in odi's(batsman)

54 controls no of ODI fifties

55 controls no of ODI centuries

56 and 57 control no. of catches taken in odi's


Byte 58.. seems to work exactly as bytes 38-42.

 

[sid_19840]

k,here's more btw there's a definate pattern here,easy enough to follow.

62 and 63 control no of first class innings.

64 and 65 control Not Out's in first class.

66 and 67 control No. of overs bowled in first class.

68 and 69 control No. of wickets in first class.

70 and 71 control No. of Runs conceded in First Class(bowler)

72 and 73 control No. of Runs scored in First Class(batsman)

74 controls no of First Class fifties

75 controls no of First Class centuries

76 and 77 control no. of catches taken in first class.

82 and 83 control no. of One day innings.

84 and 85 control not out's in One day.

86 and 87 control no. of overs bowled in One day.

88 and 89 control no. of wickets in first class

90 and 91 control No. of Runs conceded in One day(bowler)

92 and 93 control No. of Runs scored in One day(batsman) .

Once again Ive left out the bytes in between.

 

[barmyarmy]

Well done. I'll try to find time to take a look later.

 

[Burma's Finest]

Great work Sid! With any luck, some kind soul will have all of the necessary info soon to make a player editor. :happy

 

[sid_19840]

Great work Sid! With any luck, some kind soul will have all of the necessary info soon to make a player editor. :happy

Thanks,I'll try having another look at the bytes,Im really finding it hard to get time though.

Yes Ive managed to find out how they work,infact Colin had(in the invision board forum),I'll just confirm them later,

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)

EDIT-Im not sure if they work exactly like this,but it works pretty similarly,so u shd be able to figure this out.

 

[sohum]

I thought I'd chip in and say great job. I would try helping out but I don't really know anything about hex editing. I'll try anyway, and probably mess up my game but whatever. But, y'all deserve a standing round of applause. Good job and keep it up!

 

[amitbansal]

Yeah great work.

 

[sid_19840]

Thanks to Sohum and Amit.

btw I didnt know anything abt hex at all when I was first here except how hex numbers are related with decimals,but it was colin who taught me most of the stuff along with prakash,so the credit goes to them,but now Im learning more day by day and also learning assembly lang. programming in my college,which I find interesting.

So my advice would be that if you really want to do something,try to get there and give it a go,and try using all the help u can along the way,cheers.