øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=25;area=showposts;start=435e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/indexae03.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=25e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/indexae03.html.zxJ›h^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ . OKtext/htmlISO-8859-1gzip@øÕ ÿÿÿÿÿÿÿÿWed, 11 Mar 2020 08:19:46 GMT0ó°° ®0®P®€§²ð®I›h^ÿÿÿÿÿÿÿÿ*+  Show Posts - assassin

Show Posts

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.


Messages - assassin

436
General Discussion / missing avatars
« on: November 11, 2013, 04:06:32 PM »
the Final Fantasy VI (Portraits) gallery is all gone!

437
out of curiosity, how big is FF4's Battle Mechanics code?  in FF6, it's a little under half of a bank (C2), so about 26000 bytes.  exclude graphics and menu displaying stuff from this if possible.  (in FF6, i'm including the menu setups, but not their tile drawing or cursor navigation.)

438
Quote from: Deathlike2
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.

i mean they can coexist in that a character will resist ElementX and be immune to ElementY.  this is relevant should they be attacked with the two elements separately.  that distinction wouldn't be possible with the hypothetical change i was responding to, as both'd simply be Immune.

anyway, i realize it's different when both elements are in one attack.  i read about your Ice and Fire Claw example..  that's just weird.  are the weapons not treated as separate strikes?

439
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.

are the Resists still retained in their original RAM byte?  will they still cause Weak to their "opposite" element, or will having been reclassified as Absorb prevent that from happening?  iow, order of operations might matter if the answer to the first question is "no".

also, is there any further Penalty for Absorb?  e.g. will opposite elements become Very Weak (or instant death ;) )?

------

Quote from: Grimoire LD
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.

that would make things a bit all-or-none, no?  suppose you have one piece of equipment that Resists ElementX, and another that is Immune to ElementY.  in your scenario, i think that ElementX and ElementY would wind up both being treated as Immune.

ah, maybe that's what you were striving for.

but i see merit to the existing way (with your bugfix to stop lingering Very Weak applied, of course) of having Resists and Immunities alongside one another, along with their varying penalties of Weaks and Very Weaks.  obviously, maintaining multiple categories has more precision.  and as i mentioned in my prior post, there's a nice parallelism to this system.

i would say that Square took this path because they wanted you to be able to have Resists and Immunities co-existing.  it is a departure from what they did with Absorb, but still plenty logical.  despite Absorb and Immune starting off as bits in the same data byte, they indeed had different systems employed for their implementation.  it's hard to pick one method over the other (though i find the Absorb way less intuitive).

---------

Quote from: Algorithms Guide
[for physical attacks]
FF2/4/4ET (SNES)
Weakness > Immunity > Absorb/Resistance

Quote from: Grimoire LD
Weakness and Very Weak are kept separate with Very Weak taking precedence where applicable.

if both of these are true, then is Adamant Armor garbage against elemental physicals in FF4DS?  or does that game use the GBA elemental priority:

Quote
FF4A (GBA)
Immunity > Weakness > Absorb/Resistance
?

440
i'd be inclined not to mess with it.  making it extend to equipment outside of the one with the actual Immunity is a bit overreaching.  as is having normal Weaknesses involved.

there's already a nice parallelism (as seen in 03/9A69 and 03/9A78): Resist gives Weak to the "opposite" element, and Immune gives Very Weak to the "opposite" element.  greater magnitude in one direction is matched by larger in the other.

(out of curiosity: do they work the same in reverse?  will initial Weak give Resist to opposite, or Very Weak provide Immune to opposite?)

i understand the desire to try and "complete" an item like Glass Helm that has a bit set.  but it's always possible that it was set for no good reason, or that whatever aborted plan the designers had in mind with it simply can't be discerned from available information.

a couple of items in FF6 -- Paladin Shield and Memento Ring, iirc -- have a mystery bit set that does jack squat.  it can be fun to speculate on why it's there, but there's no actionable info.  and it's possible that whatever goal the designers had for it was eventually accomplished by one of the items' many other data fields.

441
Quote
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.

very nice.  can $21A1 normally have any of the bottom bits set if the top bit is clear?  if so, what happens?

as for Glass Helm/Mask, retooling it would definitely involve changing the order of things.  and if it were to make you Very Weak to the "opposite" of anything you Resisted, would it also have the decency to bump up all such Resists to Immunities?  doing one without the other seems a bit asymmetrical.  it'd be like having dirty bathwater without actually having a baby, or however that expression goes.

-----

EDIT:

Quote
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.

so to be sure, Immunity will give Very Weak for "opposites" of Immune elements, but it won't do anything to transform Weak elements into Very Weak?  or can gear with Immune transform Fire Shield's Fire weakness into severe Fire weakness, as written earlier?

iow, is $21A1 (as shown in your earlier post) the Very Weak elements, or is it a preliminary value that generates Very Weak after combining with normal Weak?

442
Quote
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.

eh, now you're mixing and matching reinterpretation/rebalancing with actual bugfixing.  i bet you could make space for a fix.

a possible optimization is to move "LDY #$0021" before the $9DA8 call at 03/9A7F.  then we can do "INY" at 03/9A8B.  just 2 bytes, but it's a start.  you've found other inefficiencies elsewhere.

where's the code that undoes normal Weakness after an equip change?  does it work by specifically subtracting out the removed equipment's elements, or by zeroing the property, then rebuilding it based on the equipment that's still there?  (my guess is the latter.)

if the game calls 03/9A78 after an unequip, and $21A6 indeed holds the right current value, i'm not sure why $21A1 wouldn't in turn wind up with the right value.  so i'm not entirely following how the bug occurs code-wise, though your explanation makes sense logically.

also, when Immunity turns Weakness into Very Weakness, is the original element still marked in the Weakness variable as well, or does it get cleared from there?

443
Quote from: Grimoire LD
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.

good work.  this definitely seems to be the soundest fix for it.

out of curiosity, what is the top bit of $27F0?

------

Quote
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.

i'm not following you here.  are you saying "Very Weakness" should never be set, or that it's being set for too long?  does this have anything to do with Immunity?

444
Quote
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)***

so $2125 is Elemental Resists (as in reduced damage), and $2126 is Elemental Nullifications (as in zero damage)?

Quote
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)

where is equipment Evasion being read?  i don't see code for that.  $AD,X was the elemental bits.

and what is $27F3?

445
what's $A9?  is that ever added to anything?  when's it first read after this?

at first, i was thinking that they wanted to have "Immune" guarantee the maximum Evasion value of 99 (because they knew that setting $AA to 128+ would later get Evasion capped to 99).  now for this, they could've skipped the "ORA $AA", and still accomplished what they wanted.

and i figured the bottom 7 bits of $AD,X were just a normal integer.  however, the $A9 code is suggesting they aren't, because it's being treated like a bitfield as well..  except i don't anticipate it ensuring 99 of anything, because $A9 will be under 128.

at this point, i'd say the bottom 7 bits of $AD,X are a list of unknown properties, and the top bit is a switch to control what variable(s) these properties will be applied to.

however, the whole idea of adding a bitfield to an integer, which is what 03/9A00 does, seems wrong.  FF6 does mix and match the two a little (by having a 16-bit value where bits 0-7 are a character's normal HP or MP, then bits 8-9 are flags that select a certain percentage bonus to give to the stat), but FF6 actually has code to interpret this rather than just add things willy nilly.

this makes me think that the FF4 makers didn't want to use $AA in 03/9A00, but some other variable, though that's with the caveat that i know nothing whatsoever about this game. :P  i wonder if you'll find some "complementary" code, where they read some other variable and treat it like a bitfield to do certain things, except the variable was never set in the first place (or maybe it was set as an integer).  then two things would be resolved in a nice, tidy basket.  if only.

that's a bit of speculation.  anyway, i'm with you that something seems suspect here.

446
- What's at 03/998B thru 03/9990, for comparison?
- What is 7E/396C?
- How is $AA originally built up from your various pieces' of equipment Evade values?  Is there capping done then, and if so, is it done with 03/9A00?

447
Game Modification Station / Re: FF6 Improvement Project
« on: October 04, 2013, 08:09:03 PM »
I was just going off of the Japanese and FF6 Advance scripts, but it looks like the Final Fantasy Wiki says the same thing:

that page links to a "War of the Magi" article, which defines "magi".

i'm inclined to agree with DrMeat64.

from what i can tell, there were two wars:
1) between the quarrelling gods/goddesses after being banished to this world.  they created Espers (from humans, and from animals according to one source) to serve as soldiers.  after growing ashamed of their actions, they gave the Espers back their free will, and sealed themselves in stone.
2) some time later, humans who extracted magic power from Espers -- and would come to be known as "Magi" -- fought the Espers.  that's the "War of the Magi" that happened 1000 years before present day.  the gods/goddesses were non-participants in this, still being statues.

448
General Discussion / Re: NFL season 2013-2014 week 5
« on: October 02, 2013, 02:03:39 AM »
Week 1

Lenophis:
8-8

Deathlike2:
11-5

---------

Week 2

Lenophis:
12-4

Deathlike2:
11-5

---------

Week 3

Lenophis:
8-8  (including one missed pick)

Deathlike2:
8-8

---------

Week 4

Lenophis:
11-4

deathlike2:
8-7

---------

1st quarter totals

Lenophis:
39-24  (including one missed pick)

Deathlike2:
38-25

you're both doing great.

---------

hey, i have no horse in this race, but your little competition here makes football more interesting.

449
Game Modification Station / Re: FF6 Improvement Project
« on: September 07, 2013, 09:53:44 PM »
yep, NSRT is good.  also, datacrystal.romhacking.net has the CRC32s (which is what most emulators will show) and SHA-1s.

450
Game Modification Station / Re: FF6 Improvement Project
« on: September 05, 2013, 06:09:22 PM »
Read the webpage and the Readme before applying the patch.