I think that you are reading here is in trouble for your modified FE being freeze(hang , stall , crush).
Here, I want to write how to respond when freeze.

In order to solve the problem,
You have to search for the cause of the freeze.
“Why did it freeze?”

Once you know the cause, you can solve the problem by removing the cause.
In FEBuilderGBA, we have several useful tools to find the cause.

Connect to emulator

If you use the function to connect to the emulator, you will get the data from the emulator and display it in an easy-to-understand format.
If you freeze on an event, let's find the event that is running before the event freezes.
It is an event where there is a problem.
Let's identify at which event the problem is occurring.

To connect to the emulator, start the emulator with the F5 key.
Then, the “connection tool to the emulator” will also start automatically.

In the latest version, “Emulator connection tool” is enabled by default.
Updating from an older version may be disabled.
In that case, please enable by option.

Actual example

The event froze in the Prologue.
What exactly is the problem?

Using the function to connect to the emulator, you can see the event, it is obvious.
It seems to freeze at this event.

Why?

The answer is because Because I mistook Seth and Gilliam.
In the prologue, Gilliam is not exists.
Therefore, trying to lower Gilliam's HP, problems arise.

In this way, using the connection function to the emulator makes it easy to find the last event where the problem occurred.
Please identify the culprit from the event's final gait, dining message.

Lint

FEBuilderGBA has the Lint function.
When wrong contents are written, Lint automatically detects it.
Lint is aimed at discovering bugs before running.

Did Lint find any errors in your ROM?
In that message, bugs that may occur in the future may be hidden.

If there is an error in the chapter currently edited, it will be displayed at the top of the right side of the main screen.
Click to see the contents.

If Lint's error report is incorrect, you can ignore the error.
Right click and say that this is not a bug, the item will not be reported.

It is important to always create a condition without Lint's point out.
If you leave an error, I will overlook important errors.

To check errors in the chapter of the event that exists in ROM, select menu → Tools → Lint.
It reports errors that exist in all chapters.

Difference Debug Tool

If you can not identify the cause of a bug even if you use the connection function to the emulator or the Lint function, you may be able to fix the bug by using the difference debug tool.
When did you start out of your ROM freezing problem?
You mixed bugs with somewhere fixes.

The difference debug tool has the function of automatically detecting a mixed bug by taking 3 points DIFF of the last version without a bug, the first version which puts a bug and the current version is.
Bugs in the program do not come out arbitrarily.
I always put the wrong data somewhere.

The difference debug tool automatically finds and corrects the incorrect data.
Please check this out for details.
Automatic detection of bugs by 3 points DIFF_EN

Return from backup

Even if you use the difference debugging tool, if you can not find the cause of the bug and can not fix it, you only have to take the last resort.
Finally, return the data to the backup that was working correctly.
This is a painful decision.

In many cases, you can solve it without doing so far, but if you can not solve it by any means, there is no choice but to take this measure.

With FEBuilderGBA,
FEBuilderGBA automatically creates a backup before writing to ROM.

Let's restore from this data.

Try asking a question

I do not want to return from backup, but if I want to cure a bug,
so, let's ask a question on the net.

In addition, since frequently asked questions are written in FAQ, please check before asking questions.
QA_EN

To ask for a bug, you need the contents of the bug and the UPS difference to reproduce the bug.
The easiest way to create these is to use “menu” → “file” → “problem reporting tool(Create Report Issue)”.
By using this tool, it automatically creates the ups patch necessary for reproducing the error and compress it in 7z format.

Please attach this 7z with a comment attached.
A kind person may answer.
Discord(chat)　

Although it is also written in the FAQ, please write in your native language you are using on a daily basis when writing.
When posting with a machine translated word, we do not understand the meaning anymore, please stop it.
Please post in the language you are using on a daily basis.

We are hungry for the topic of remodel FE, so welcome your posts.