![]() I could look to see if what I think could be a section of pointers makes sense given the rest of the file (assume pointers for text are at the end of lines/sections and comparing section count with possible pointer width) but if I change the window width/section width and suddenly end up with a line of 0000s going down the screen or a diagonal line/repeating pattern on diagonals then I am probably onto something. As the hex quite literally represents the contents of the file then hackers might share dumps and screenshots for other hackers to contemplate but they know the other hacker will be able to filter out the useless information. They might also realise a change could be in any number of places but is in a fixed location relative to something easy to find, or if there is a wide selection of options might direct a user to make a change with one rather than making however many thousands of patches that the combinations of such changes might make (think put this number in here to make the pokemon of your choice appear, and put this other number to put this in your inventory - if there are 500 pokemon and 500 items that is 250000 total combinations before you even consider someone might only want 1 potion rather than a full stack, far easier to say "this location and this number from this list, and this location and this list has numbers"). Skilled ROM hackers might use a hex editor as a least worst option to make a small change, or initially analyse a file to see if it looks similar to things they have seen before*, has certain tells**, has patterns worth exploring or similar. The word processor analogy also often holds quite well - hex editors tend to feature niceties like overwrite/insert, go to location, simple common operations (I would say most boolean and bitwise operations are much like "make bold" or change case in a word processor). See the API reference for details.Hex editing is not a thing, a skill, or ability beyond the obvious "hex is 0 through F, type it like you would in a word processor but using that instead" and less obvious "hex editors tend to be split into three sections - left typically is the location in the file/memory/hard drive, middle is the data represented as hex, and right is typically some kind of text decode that can be customised to be a different encoding or a custom one in some cases as you desire). Its permissive BSD-style license won’t burden you. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |