I was about to, when I realized I gave you the wrong first address! Sorry, I feel like an ass now. It's not 0x16E, it's 0x16F. Sorry. I'll show you exactly what to do to find addresses in a moment, using a picture.
EDIT:
You want to find 0x16F? You go to the 00000160 row, and look in the 0F column, to get 16F.
All hex is is a numbering system that goes from 0-15 instead of 0-9, with 10-15 being represented by A-F. This was developed in computers as a shorter way to write bytes, which are written by ON/OFFs, also known as binary. Binary is ALSO a numbering system, ranging from 0-1. 01 binary equals 1. 10 binary equals 2. 11 binary equals 3. 100 equals 4. 101 equals 5. 110 equals 6. 111 equals 7. 1000 comes next, and it equals 8. That goes all the way up to 255, as far as a computer is concerned, because a byte is eight slots. 11111111 binary is 255 in decimal (which is the 0-9 numbering system). Now, take this into account: FF in hex is ALSO 255 in decimal. FF is much easier to write than 11111111 is it not?
Hex is basically computer talk (binary) short-hand. What you're looking for is a specific byte (the character ID) in a sea of bytes. Each byte in that file, which composes that file, has an address. Most hex editors are formatted to be able to find bytes at a given address easier. Not all, but most.
And I hope that's helped someone out there. guarantee it hasn't. These are the rantings of a mad man.
