Accessory passive-effect table Confirmed

At a glance

Magic

none - static data in SCUS_942.54 (the game's main executable)

Where

Name / description / scope table at 0x8007625C (file 0x66A5C), 64 × 12 bytes; the index bytes ride the item-effect descriptors (+3) and equip rows (+5)

Index space

0x00..=0x3F; index = bit position in the character's ability bitfield at record +0xF4

Sentinels

0x40 (equipment rows) / 0x41 (consumable rows) = no passive

Parser / engine

legaia_game_tables::accessory_passive; engine-battle::accessory_passives

Confidence

Confirmed - all appliers traced (how we know); assignments byte-verified against the curated accessory table

Used by

Battle formulas, Pause menu (Goods panel), Shops page

How an accessory grants its effect

1. Equipped itemeight slot bytes per character, record +0x196
2. Index bytedescriptor +3 (Goods) or equip row +5
3. Ability bitset bit index in char +0xF4; >= 0x40 sets nothing
4. Global maskall three character records OR'd together, joined or not
5. Point of useeach mechanic tests its own bit

The stat aggregator rebuilds this chain on every equipment change (it is event-driven, not per-frame), so un-equipping takes effect immediately.

The stat aggregator walks the eight equipment-slot bytes of each of the three character records, with no test for who is in the party (record +0x196) and resolves each item to an index:

kind = item_table[id].byte(+0)
if kind == 1: index = equip_bonus[sub].byte(+5)
if kind == 2: index = descriptor[sub].byte(+3)
if index < 0x40:
    char[+0xF4 + (index>>5)*4] |= 1 << (index & 0x1F)

• char +0xF4..+0x103 is the per-character 4×u32 ability bitfield - the home of the MP-cost bits (indices 0x04/0x05).
• All three records' bitfields are then OR'd into a global 4×u32 mask - how party-wide passives are consumed. A member who has left the party still contributes: their accessory's party-wide passive stays in force.
• An index of 0x40 or above grants nothing. In retail every equipment row carries the 0x40 sentinel (no equipment grants a passive) and every consumable carries 0x41; only accessory and quest-item rows carry live indices.

The same gate is read by the pause menu's Goods detail panel and the description resolver to fetch the display text. The battle damage path reads the first two bitfield words directly as the defender's elemental-resist / spirit words (details under how we know).

Passive name/description table

A static 64-record table at 0x8007625C (stride 0xC) gives each index its menu name, effect description, and scope:

Party-wide scope is set on exactly indices 0x30..=0x37 and 0x3B..=0x3F - the battle-end, encounter and escape modifiers.

The 64-index space

The bands, with example items (full per-index list in the source doc):

Quest items share indices with their purchasable twins (Mei's Pendant = Life Ring, each Egg / Talisman = the matching Jewel) - which is what first exposed the index space. Indices 0x3E/0x3F have populated description records, but the Point / Platinum Card rows carry the 0x41 sentinel; the cards are special-cased by item id in the Goods panel.

Status-guard clear masks

Seven indices are status guards - the amulets that stop poison, curse, stone and the rest from sticking. The guard applier ANDs a fixed mask into the battle actor's status word per set bit, and the mask table is what pins the battle status-flag bit map:

Master Guard's mask is the definition of "ailment": 0x1C7F is the union of the six above plus 0x0800, the one condition with no guard of its own. It does not clear the AI-delegation group Rage sets - a passive, not an ailment, so a full cure leaves it standing. Bit assignments and the HUD elements are on save-record; engine mirror engine-battle-vm::status_effects::display_flags.

Magnitudes and the Talisman arm

The percent boosts (0x00..=0x0C) are applied inline by the aggregator - no magnitude table exists. Per index: +10% = base/10, +25% = base>>2, +20% = base/5, added to the copied base and capped (HP 9999, AGL 280, others 999). Every other index is a point-of-use flag: each consumer tests the bit where the mechanic lives - MP cost at cast time, the steal table for Steal Attack, the guards in the damage path, encounter rate in the field step roll, loot in the battle-end reward resolver.

A separate arm of the same aggregator watches equip slots for specific item ids (not passive indices) and grants or revokes battle spells: the five Talismans grant summon spells, and the top-tier Ra-Seru weapons grant their own. A Talisman is therefore "guard passive by index + summon by id".

How we know

In the port: parser legaia_game_tables::accessory_passive (CLI asset accessory-passive); engine engine-battle::accessory_passives - item id → index + scope, the bitfield rebuild on every aggregator pass (battle entry, equip commit, load), the party mask test, and the percent boosts under the retail clamp block. Source of record: docs/formats/accessory-passive-table.md.

See also