Effects

The client has three effect systems with a shared lower layer (a particle = SPT script + sprite, an entity = R3E + material + textures).

A. Mesh effects (permanent): Chef table (Monster.ini, Npc.ini, ItemEffectList…) → .EFF → texture layers and particle/entity slots
B. Event effects (“magic”: hit, skill, force, level-up, item on the ground): event code → id → MagicSptList.spt → [MagicTrack] script → EffectEntityList.spt
C. Map effects: .ebp (objects and particles by BSP leaves), .r3x (weather), sky\*.r3e

Game data controls A and B: the Chef tables and the Effect lists. The event numbers of B are hard-coded in the client — they can only be filled in.

How it works

• “Number → EFF” tables: Monster.ini, Npc.ini, GuardTower.ini, Siege.ini — by record number; Unit.ini — part number + (group − 0x25) × 100; recall.ini — animus by kind and level (a multiple of 5); items — the chain ItemEffectList (model → column) → PatternList → EffectFileList (upgrade level 0–8), column 5 is for female meshes.
• Magic: monsters — 95000 + effect code × 40 + slot, skills and force — ids by grade and level with the weapon kind in bits 20–27, items on the ground and projectiles — by model and ammo row number (group 11 rows are never reordered). A ranged attack shows damage only when a projectile or a track with check_damage arrives.
• Animation hit frames (effectNum, effectFrame in Resource.edf): effectNum 1–9, frames increasing within the animation; an attack animation without a hit frame shows no damage and adds it to the next hit.
• The client parses the .spt/.txt lists word by word: a comment word starting with a digit becomes an id; the first id wins.

What matters when editing

• An EFF from the Chef tables is a separate file; particle and entity numbers exist in Particle.ini/Entity.ini and are below 0xC00; an SPT has entity_file.
• In MagicSptList and EffectEntityList every id has a path (≤ 89 characters), ids do not repeat, comments contain no numbers.