![]() So the first 2 bytes represent the offset to where the text will start then each 2 bytes from there onward are how many bytes from the initial offset you move forward before the next message starts normally between messages is the hex vale FF FF each pointer will end on the seconf FF. I have a new found hatred for using strings in C.įinally I have figured out how the pointers work I will try to explain. So to speed things up I created my first C program to check against the table file is a string is valid if it is then return the full hex output needed to inject that string. Next I noticed that searching through the table file for valid string was faster then using a reference image and a calculator (not fun trust me) it was still slow. ![]() Here is the table file loaded into a compatible hex editor that supports double byte table files this is "Translhextion" remember to enable "Thingy View Active" via the checkbox. Time for a update! So I have managed to make a translation table that will show what text the the crazy hex values are actually representing now this table file was rushed there were over a thousand tiles to translate and I may have made mistakes so I will update in the future.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |