Hex Editing Madden

[Xanathol]

Re: Hex Editing Madden

Just to kind of 'whet your whistle', here is what my editor looks like - REMEMBER - until we can figure out the checksum thing, this is nothing but a VIEWER!

( OK images not showing in my post... so here are links to them instead! )
Main
Contracts
Appearance


Simplistic, yes, but as you can see, all of the player data is there ( lots of scrolling to the side for other fields :wink: ).

[Jd_Seven]

Re: Hex Editing Madden

Just to kind of 'whet your whistle', here is what my editor looks like - REMEMBER - until we can figure out the checksum thing, this is nothing but a VIEWER!

( OK images not showing in my post... so here are links to them instead! )
Main
Contracts
Appearance


Simplistic, yes, but as you can see, all of the player data is there ( lots of scrolling to the side for other fields :wink: ).

Impressive, it has been long overdue for this kind of software for madden. Madden could get lots of roster love with this tool. Brilliant stuff man, keep it up please. Thanks

[dhsmustang]

Re: Hex Editing Madden

Just to kind of 'whet your whistle', here is what my editor looks like - REMEMBER - until we can figure out the checksum thing, this is nothing but a VIEWER!

( OK images not showing in my post... so here are links to them instead! )
Main
Contracts
Appearance


Simplistic, yes, but as you can see, all of the player data is there ( lots of scrolling to the side for other fields :wink: ).

Looks great. What's the old polynomial?

[Xanathol]

Re: Hex Editing Madden

Looks great. What's the old polynomial?

The table is in the source in this post. I didn't reverse the table back to the poly yet - just haven't had time.

[Xanathol]

Re: Hex Editing Madden

Ok, it looks like the poly used in the original table was 02608EDB after doing a bit of reverse engineering of the table. If push comes to shove, we may be able to brute force different polys through the checksum code to check against the header. Probably take a few days, but theoretically doable.... maybe?

Edit: 02608EDB or DB8E6082... depends on byte order in the table... anyhow...
Edit 2: ok missing something about the table or I dunno what, because I cannot regenerate the table with either poly above.... The code generates a proper table for a standard poly ( ex 0xEDB88320 ) and the reversing algorithm returns the standard poly as expected....