This is because TextID: 0xF1B has an incorrect character code entered.
If you change this string correctly, it will work normally.
Hi, I’ve got an issue regarding summoning:
Once a phantom is summoned, the option to summon doesn’t go away, granting a free 10xp.
How can I fix this?
Are you editing the Summon table correctly?
That behavior often happens when the unit being Summoned is already on the map.
It appears the hex address is different than normal.
Usually it’s 95F5A4, but instead it’s 165D944, and when I try to change it this message pops up:
“Address 0095F5A4 is out of range, unable to write.”
Other than this everything else is the same.
I’m not sure if I should write what happened here too, so… I will only send the link :v.
However I can explain what happened.
In any case the report is more detailed. But to resume everthing: The CG freezes, the text doesn’t appears, but the music keep playing.
Specify a space after Orc.
NG
“[SetName]Orc”
OK
"[SetName]Orc "
This solves the problem.
This is a problem related to 2-byte processing.
GBAFE is designed on the assumption that Japanese is 2 bytes.
Therefore, it does not assume that the number of characters will be odd at 3 and that there will be fractions.
The routine to search for the name to be output by the SetName command searches for line breaks, copying characters in 2-byte units.
“Orc” is three characters long, so this routine will not detect the end of the line.
You can avoid this problem by adding a space at the end to make it four characters.
If you don’t like the space, you can use the padding character [.]. “@001F” should be used.
0808EB2E D00A beq #0x808eb46
0808EB30 6AD9 ldr r1, [r3, #0x2c]
0808EB32 7808 ldrb r0, [r1, #0x0] @1st
0808EB34 7010 strb r0, [r2, #0x0]
0808EB36 7848 ldrb r0, [r1, #0x1] @2nd <<<
0808EB38 7050 strb r0, [r2, #0x1]
0808EB3A 1C88 add r0 ,r1, #0x2
0808EB3C 62D8 str r0, [r3, #0x2c]
0808EB3E 3202 add r2, #0x2
0808EB40 7888 ldrb r0, [r1, #0x2] @search \n (@0001)
0808EB42 2801 cmp r0, #0x1
0808EB44 D1F4 bne #0x808eb30
0808EB46 6AD8 ldr r0, [r3, #0x2c]
1 Like
Please send report7z.
I made a patch to fix this SetName’s problem
NAME.en=Fixed bug where SetName crashes with odd bytes
INFO.en=Fixes a bug in SetName(@0080@0023) for text escape sequences that caused a crash when trying to set a name with an odd number of bytes.\r\nThis is a glitch problem caused by the processing of two bytes in Japanese.\r\nThis patch will fix this process to scan for single bytes.\r\nIf it were any other character encoding, the newline would be 0x01, so there would be no weird side effects.
1 Like
New function.
You can now see the FE6 UnitRAM structure in the Debugger.
But, there is one limitation.
FE6 can hold up to Support10, but currently only Support7 can be seen.
However, other than that, it works correctly.
1 Like
tutorial to add thai language please
I want to translate story for thai people
When using the English version as a base
Install the UTF-8 Patch so that all characters can be handled.
Note: UTF-8 Patch is only available for the English version.
This is because the Japanese version is made with SJIS.
UTF-8 is compatible with the alphabet (ASCII), but not with SJIS.
1.1.
Anti Huffman Patch is required.
However, in the case of FEBuilderGBA, it is automatically recommended when it becomes necessary, so there is no need to manually insert it from the patch list.
You will need to create a Thai font.
You will need two fonts: an item font and a text font.
You can do this by auto-generating, but the quality is not very high.
If you don’t like it, you will have to adjust it manually.
You may get a slightly better result by using google’s notofu font.
Now that you are ready to display the Thai language, go ahead and translate the text.
If you are using the Japanese version as a base.
Create a tbl file.
Specifically, please refer to the Chinese and English (FE6) tbl files.
FEBuilderGBA\config\translate\zh_tbl
FEBuilderGBA\config\translate\en_tbl
In tbl, map the Thai characters on top of the Japanese characters.
You will need to create a font for the Thai language.
You need to replace the font of the Japanese characters overwritten in tbl with the Thai language.
Basically, it is the same as the one based on the English version.
Can you make an example picture step by step please? Thank you.
You’ll have to figure that out on your own.
Guides for localizing translations are out of the scope of FEBuilderGBA.
I’ll attached some screenshots, so if you can’t look up the information yourself based on those, you shouldn’t do it.
Data Crystal (tbl)
https://datacrystal.romhacking.net/
Hello, I have a question regarding dead units.
Am I doing something wrong? Why do some units suddenly appear to be perfectly fine when a chapter without battle preparations start?
They can be used perfectly fine, but when a chapter with battle preparations does start, they automatically get into the hidden status again. Why is that?
This is an issue for me because I wanted to have permadeath in my hack, and this is messing up my plans.
You forgot to attach report7z.
Perhaps You just mistakenly issued LOAD2 to PlayerUnit.
As mentioned at the beginning of this thread, please attach report7z when asking a question.
1 Like
Sorry, you’re right, I forgot.
I wanted to ask you another thing.
…How do I make a backup?
I’ve been trying to find where are
the backups of my game in FEbuilder
all day but I haven’t found anything.
That’s the reason I haven’t sent the report7z yet…
The automatic backup is created in the same folder as the ROM.
Unless you have disabled it in your FEBuilderGBA settings, every time you write to a ROM, it will automatically generate a backup with a date.
If report7z can’t detect any previous automatic backups, then you probably renamed the ROM forcefully.
If you want to change the name of the ROM, please use “FEBuilderGBA MENU->File->Change Project Name”.
If you don’t, you will lose the link to your previous backups.
1 Like
Yep, it was that I renamed the ROM forcefully, now I see.
Also, I forgot to thank you for helping me, it was that I tried to use an incorrect command to load my units into the battlefield.
Seriously, I’m so grateful for your help.
Your problem has been solved, is that correct?
Please be careful in the future not to break the link with your backup.
And if you have any questions, please attach report7z.
1 Like