FE_Builder_GBA -- If you have any questions, attach report7z

A major update of FEBuilderGBA was performed.
The ROM pointer constants have been modified.
This will allow FEBuilderGBA to open ROMs that are not readable by FEBuilderGBA or that intentionally do not let him read them.

ROMs have not one but multiple pointers.
For example, the Unit pointer is not only in 0x10108, but also in 0x104EC and 0x10538.
Until now, only 0x10108 has been used, but if this cannot be obtained, other pointers are looked for.
This allows us to open ROMs even if a particular pointer is damaged.

Allow users to define pointers directly for cases where there is only one pointer or where the above methods cannot be used to track it down.
If a file named YOURROMNAME.custom_pointer.txt is created with the same name as the ROM, its contents will be referenced.

This content is a tab-delimited key value type definition file.
For example, if portrait_pointer is moved to 0xA59B08 instead of the default 0x005524, you would define the following

portrait_pointer	0xA59B08
class_pointer	0x17ADC

YOURROMNAME.custom_pointer.txt for YOURROMNAME.gba, and so on.
Creating this file is a bit more difficult because of the knowledge of the FEBuilderGBA source code and the knowledge of ASM.

Please refer to this file to see what constants are available.
You can use C# reflection to rewrite all uint type constants.

4 Likes