Topic: Armor Modding Info

[Deathlike2]

I'm pretty sure this isn't new info, but I started to mess around with some of the armor data, which I've found a lot more meaningful now..

Note that the most significant/leading bit in this info is bit 0.

Byte 0:
Bit 0 - Metallic
Bit 1-7 - Magic Evasion value

Byte 1:
Bit 0-7 - Defense value

Byte 2:
Bit 0-7 - Evasion value

Byte 3:
Bit 0-7 - Magic Defense value

Byte 4:
Bit 0 -  Shield Bonus? (Defense Multiplier += level/16)
Bit 1-7 - Elemental/Status table

Byte 5: Race Resistances

Byte 6:
Bit 0 - Ring
Bit 1 - Armor
Bit 2 - Shield
Bit 3-7 - Character Equippability table

Byte 7:
Bit 0 - Str
Bit 1 - Agi
Bit 2 - Vit
Bit 3 - Wis
Bit 4 - Will
Bits 5-7 - special table that dictates bonuses

Note: When any of the bytes 0-4 = 1, the bonuses are positive. When any of the bytes 0-4 = 0, the bonus is 0 or negative.

[Phoenix]

That matches my own data, for the most part. I believe the byte 6 armor classification bits are:

bits 0-1:
     00: Shield
     01: Helmet
     10: Armor
     11: Gauntlet / Ring
bit 2: ?

However, I'd also like to point out that these don't actually work. It's another case of the bits matching, but not useable. The determination of which pieces of armor equip where is hard-coded.

Also, I think you meant to write "bit" in byte 7, and in your last sentence. Just to supplement your info, the table for those three bits that determine the stat bonuses is like this:
000: +3      100: +5, -5 to all stats not increased
001: +5      101: +10, -10 to all stats not increased
010: +10   110: +15, -15 to all stats not increased
011: +15   111: +5, -10 to all stats not increased

[Deathlike2]

Yea...

For a moment, I thought you could apply the shield bonus to non-shield data, but I must've been crazy for a bit.

[Phoenix]

I did some testing with that a while back, and what I found was that if you deactivated the shield bit on shields, it gave the following changes:

[defense value]+4 is added to attack
[defense% value]/2-49 is added to attack%

Not sure what coding does this, and I'm sure it's not intentional, but it's interesting nonetheless.