Here's the second and the last update for tonight:
I was wrong to believe that the images started from 0x2B13 in my earlier post. After peeking around a little, I came to think that the images start from 0x2B10, with a dummy character (can also be a single pixel dot), and continue with number 0 after that in ASCII order. This makes zero the second character, and it can be accessed with index 1 in eVic char table.
Hexadecimal value (index) of 0 is 0x30 in the ASCII table, and subtracting 0x01 (the index of 0 in the eVic table) from 0x30 yields 0x2F.
Now, if we skip forward to the offset 0xECA1 in v1.1 file, and take the characters until the next 0x00, we get:
0x1E, 0x40, 0x3F, 0x35, 0x32, 0x4A
Now, if we add the value 0x2F we found earlier (by subtracting the index of 0 in the eVic table from the index of 0 in the ASCII table) to every char, it becomes:
0x4D, 0x6F, 0x6E, 0x64, 0x61, 0x79
And finally, we open up the
ASCII table, and get the characters that correspond to these hexadecimal values:
"M", "o", "n", "d", "a", "y"
Coincidence? Lets get the next string until 0x00 (starts from 0xECA8)
0x25, 0x46, 0x36, 0x44, 0x35, 0x32, 0x4A
Now add 0x2F:
0x54, 0x75, 0x65, 0x73, 0x64, 0x61, 0x79
and finally translate to ASCII:
"T", "u", "e", "s", "d", "a", "y"
Happy Haxx0ring! ^^