Question about ability "Control"

[Ruinom]

Now because of everyone's support, 2) is completed!!

Then I think the answer of 1) is in Battle.BIN subroutine2.

spoiler

lui   v0, $801a   # 001926e8:3c02801a
lbu   v0, $e189(v0)   # 001926ec:9042e189
addiu   sp, sp, $ffe0   # 001926f0:27bdffe0
sw   s0, $0010(sp)   # 001926f4:afb00010
lui   s0, $801a   # 001926f8:3c10801a
lw   s0, $e184(s0)   # 001926fc:8e10e184
.
.
.
addiu   sp, sp, $0020   # 001928cc:27bd0020
jr   ra   # 001928d0:03e00008
nop      # 001928d4:00000000

First of all I should try learning how to use the debugger.

To Jack
Which number is your favorite one? My favorite title is 2nd.

[Timbo]

The first one. It's hard to point out why but it grabs me harder than all of the others.

[Ruinom]

It's been quite while.
Lately, I taught myself how to use the debugger by some tutorials.

However, some breakpoints were hit more than necessary.
For example, I set a Unit Data breakpoint (801908cc) then I used invite.
When ally character finished turn, the breakpoint were hit and hit and hit....
Which breakpoint is better?

To Jack
I'm looking forward news of 6th.

[Choto]

instead of unit data, you want the "current status" byte that holds wether or not the unit has invite. for psx version this is at 0x59 in unit data as you can see here: http://ffhacktics.com/wiki/Battle_Stats

you also want to find the specific unit's data. 801908cc is the start of unit data. Each unit's data is 0x1c0 long. However, we know that allied unit data starts at 0x1924cc. So if you start there and check that unit's job to see which unit it is, then go 0x1c0 further and check the next unit... you can find the specific unit that you want. Then, go to that 0x59 byte and set a breakpoint.

but with that WOTL stuff, it could be different.