![]() ![]() And again, another 28 bytes later we get hex "77 00" - decimal 119, the rifle ammo. So what if we look forward another 28 bytes at 19160? We find "30 00" - decimal value 48, the value of shotgun ammo. The SMG value starts at 19132 - 28 bytes apart. Click to enlarge.įrom there we can deduce further - The pistol value starts at byte 19104. The 2 values (pistol value in blue, SMG value in red). So, where to go from here? We can repeat the above exercise with the other values to find them, but we can help to deduce the whereabouts by adding some logic to what we already know - in this instance, we're looking for ammo values, we've found one, and we can reason that it's quite likely that these values will be grouped together.įor example, the SMG ammo value (70 00) was found nearby (which is the decimal equivalent of hex value FFFF) So, let's change these two bytes to FF (the largest 2-character hexadecimal value - like 99 is in decimal), reload the game, and see what happens. The bytes representing the pistol ammo highlighted in red (click to enlarge) There's ways around that but it's a bit of of scope for this project - I might do a follow up post later dealing with those things.Īs it happened, with the pistol ammo amount I lucked out, there was only the one instance.: If you continue to find nothing, it could well be there's some additional encoding or perhaps simple encryption on the file. "01 09" becomes "09 01" and search for that. Simply reverse the order of the bytes above - e.g. In layman's terms, you can think of it as reading from left-to-right or right-to-left. In which case the endian ordering of the file could be an issue - this refers to the order in which the bytes are used to create the actual number.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |