It is now displayed because FELint has expanded the range to check.
The content of this error,
you are making an ax that can throw 0xD1 weapons.
However, the unit that can use this ax does not hold the motion that throws ax.
For example, please look at the general battle animation.
The ax that can be thrown is set individually.
It is unnecessary in the case of a sword or a spear.
Only the ax that can be thrown needs to be specially specified.
This is the specification of GBAFE.
Axs that can be thrown need to set hand axs motion individually.
Otherwise, battle animation will freeze.
FELint points out that.
You made an ax called Requiem at 0xD1.
That ax capable of range attacks such as 1-2.
However, you have not set that motion to a unit that can use an ax such as 0xB General.
However, I do not know if this is the cause of your battle animation freezing.
Information is insufficient.
If you want to solve the problem completely please send me ups file.
Your ROM is corrupting the stack in the function for the growth rate.
The push / pop relationship of the stack has been broken.
Therefore, I searched for patches that you are using with a patch seeking growth rate.
So I found this DSFE Growths.
Uninstalling this patch resolves the problem.
However, in general, DSFE Growths works properly if it is standalone.
I think that it competes with any other patches.
I have to investigate more which competing with other patches.
Also, to turn off the FELint warnings, please do the following.
Set the attack range of 0xD1 Requiem to 1-1.
(If you want to change 0xD1 Requiem to 1-2 please set motion 0xD1 Requiem to a class that can use axes.)
It is unreasonable to set a achievement flag in a store.
This achievement flag turns ON when an event occurs.
Once the flag is set, the event is considered to have occurred, and it will not work the second time.
In other words, this shop, once entering, will never enter the store again.
Also, if you have never entered this store, I think that flag 0x09 is in effect at other events.
Either change to another flag or not to set a flag at all.
I tried to do this in the new ROM, and it turned out, as you did, that it was error-free. I think he might have been in conflict with another patch.
I think I have almost solved the icon bug now. If I put the icon I imported into the original system icon, it won’t happen.