øA slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=25;area=showposts;start=435 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/indexae03.html slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=25 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/indexae03.html.z x J›h^ ÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ . OK text/html ISO-8859-1 gzip @øÕ ÿÿÿÿÿÿÿÿ Wed, 11 Mar 2020 08:19:46 GMT 0ó° °® 0® P® €§² ð® I›h^ ÿÿÿÿÿÿÿÿ*+
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
They don't really coexist though... not in this game. Absorb and Immune have precedence depending on the game port, and whether it is physical and magical. In FF5, FF6, and onwards, there is a distinction intentionally made. Just not this game.
Having seen how the Cursed Ring works, where elemental equipment benefited from the effects of the Cursed Ring (resistance to elemental -> Absorbs elemental), Immune ideally would reflect this. Say you had an Ice Shield + Cursed Ring combo... all Fire elemental magic attacks would be absorbed (think Rubicante). Having an Ice Shield + Flame Armor would allow you to absorb both.
I still don't fully grasp why Square took this path in particular. The easiest thing to do would have been to make 80 on the normal elemental byte be read as Immune (rather than set up an entirely separate byte for it) and add an exception for it if this Immune bit is triggered to (BMI) instead to use Very Weak instead of Weak elemental figurings. But 80 on the normal elemental byte does nothing.
[for physical attacks]
FF2/4/4ET (SNES)
Weakness > Immunity > Absorb/Resistance
Weakness and Very Weak are kept separate with Very Weak taking precedence where applicable.
FF4A (GBA)?
Immunity > Weakness > Absorb/Resistance
Oh what a fool I've been! The answer was so simple!
$03/9A82 F0 07 BEQ $07 [$9A8B] A:0002 X:0003 Y:0026 P:envMxdIzc - Branch if 00 to 039A8B
Completely useless, it does nothing but Prevent the byte from being rewritten. It is the singular cause of the bug and nulling it does nothing adverse. Other armor types don't interfere with it as the specifications for where it is drawn is still the same Elemental Immunity Byte. So the easiest answer is...
$03/9A82 EA NOP A:0010 X:0003 Y:0026 P:envMxdIzc
$03/9A83 EA NOP A:0010 X:0003 Y:0026 P:envMxdIzc
That will keep the x4 weakness and while it will keep the "Very Weak to" 80 stores in Very Weak, an 80 on its own does nothing and is not necessary to worry about.
As it is specifically that a Very Weak value is written only if the Immune bit has other elements attached with it. I'm not sure where I got the idea that Immune stacked with other Elements.
Immunity to one element should not come with such a high price as x4 Weakness, in my opinion in the first place and this prevents the potential problem of being unable to fix the value's issues because of the lack of space.
This looks to be a legitimate fix and I have noticed no problems. Instead of trying to add to the code, it seems like it was just best to work around it.
Since we're on the topic of Immunity problems, lets look at x4 Weakness is never removed, eh?
...
Because of the way the game works it will never decrement any bits that come into the x4 Weakness Byte.
The other 7 bits of AD are Elemental Resistance, Fire, Ice, Bolt, Holy, Dark, Air, Absorb and the game carries them as normal until it reaches the Branch if Minus portion, once it sees that it isn't 80 it leaves that value behind. Though I do have to wonder why it is then saved to A9... instead of AA. Maybe it is an off-by-one error? It wouldn't be the first time that Square had this happen (In this very game!)
Now A9 in this routine's purpose ends here...
$03/999E A5 A9 LDA $A9 [$00:00A9] A:0001 X:0005 Y:0025 P:envMxdIzC
$03/99A0 91 80 STA ($80),y[$7E:2125] A:0001 X:0005 Y:0025 P:envMxdIzC
25 elemental defense (if immunity bit wasn't set)***
Why it has to jump through loops to put the value into 7E2125, I'm not really sure. More interestingly is what happens to the value in AA...
$03/99A3 A5 AA LDA $AA [$00:00AA] A:0001 X:0005 Y:0026 P:envMxdIzC
$03/99A5 91 80 STA ($80),y[$7E:2126] A:0000 X:0005 Y:0026 P:envMxdIZC
26 elemental defense (if immunity bit was set)***
Read one byte of Equipment (Evasion), store it in AA, move on to the next piece of equipment. (Shields are not read here for some reason however)
I was just going off of the Japanese and FF6 Advance scripts, but it looks like the Final Fantasy Wiki says the same thing: