Hi everyone, my name is Loz and I'm from Latin America, un gusto saludarlos .

Viewing some documents from your website, the videogame pointers section (http://chief-net.ru/index.php?option=com_content&task=view&id=109&Itemid=33), more specifically the GBA relative pointers section.

That document mentions that the formula for finding the relative pointers of GBA is:

Ptr = 0x7843F8 - 0x7843B0 = 0x0048

Where:
0x7843F8 = Dialog Start Offset
0x7843B0 = Offset where the Pointer is located

This has me confused, since we only know the offset of the start of the text and we want to find the offset where the pointers are located, but in the formula, you already know the pointer offset, how could I find the offset of a relative pointer in GBA if I only know the text start offset, please, someone could me guide to understand it. I may have misinterpreted the document, could you help me understand it, please.

I don't know anything about the Russian language, so it help me with the Google translator, this translator is not good for translating from Russian to Spanish, but, still try I to understand as best I can what is mentioned in that document, I may have misinterpreted the document, could you help me understand it, please.

Hi, Loz.
In the above example, it was told in advance that the table of pointers has been found visually. If you look in the hex editor at the area around the text block, you can see a table with bytes that have a structure that is distinguishable by the human eye: in this case, 16-bit values that slowly grow from one to the other.
This could not be the case for exactly your ROM. In the most general case, debugging is the guaranteed way to find the pointer table.

Hi Griever, tan you very much for answering .

So, the only way to find the offset of the relative pointers would be by means of a debugger, my knowledge about using a debugger is zero .

Searching for information on the Internet, I found messages mentioning the no$gba emulator, but I did not find information on how to use it, knows of a document that mentions how to use it, or maybe someone can guide me to use this emulator correctly.

Well, you could search for absolute pointers, as they are described in the document. If they cannot be found, you can search visually before or after block of text for suspicious tables of bytes, which can be pointers.
Let me know if none of these methods worked for you.
Debugging requires some assembly knowledge and is a vast theme for explanation.

The game I am testing does not have absolute pointers, so I'm sure it has relative pointers.
So, I will have to train my eyesight to recognize a suspicious byte table.

Disassembly and debugging, for now are out of my reach, my knowledge is null, but if a document was made to explain it, I'm sure it would help many people like me to learn it.

Griever, thank you very much for answering my questions .

No problem, let me know if you still can't find these pointers.