The straight fire shot, the rebuild against the game, difference by difference (eft0061 + executable)

Input: a side-by-side recording of the same cast (data record 130, effect eft0061) in the 2017 PC build and in the rebuild, plus an Xbox recording of the same skill. Footage is used only to locate and to check; values come from the executable (1.3.25854.2), the effect pack and the animation data. Confidence: H read in code or data and seen in footage, M read in code or data only, L footage only.

1. The stage is lit by effect lights (corrects “the stage gets no effect light”) — H

2. Cast animation and the feet

3. The flash at charge and release (“the missing effect”)

What the game shows is a yellow-white fill of the orb in the last third of the charge and a 1.2–1.5 m cloud at the chest for about half a second from the release. Both are particle01 emitters of the pack (H: data + both builds’ footage):

slot element joint frames size texture blend colour → end emit
0 cast 2 right hand 0–22 3000 5 0x1200 (1, 0.3, 0, 0.5) → 0 haze from the first tick
0 cast 3 right hand 19–24 4000 5 0x1200 the release peak
0 cast 4 right hand 17–22 300 → 100 4 (1, 0.5, 0, 1) streaks
0 cast 5 right hand 17–24 3000 7
0 cast 6, 7 wrist, forearm 14–22, 16–22 6
3 release 1 body 0–4 3000 6 one/one (1, 0.25, 0, 1) → 0 12 per tick, life 15, speed 0.5

The cast slot’s meshes run to frame 23, three ticks past the release; its late mesh set (frames 12–23) is the body-sized ring both builds show at launch.

The rebuild draws the same elements through the decoded particle draw, but they come out as a small dim red smudge (charge) and a red cloud (release) where the game saturates to yellow-white. The element list and timing are right; the open part is how overlapping additive sprites add up. Not decoded in this run (no render probe was made). Leads, in order: (a) the sum is taken in linear light in the rebuild and on stored 8-bit values in the game (a dozen layers of a dark orange stay red in the first and clip to yellow in the second), M; (b) a factor in the particle01 colour path (the vertex colour clamp or the alpha weight of blend 0x1200), L; (c) the glow pass on the summed frame, L.

Decoded in bof4 (H): the blend column above is not used: every particle draw sets one / one, add itself (section “Effect particles”, Blend). The rebuild drew elements 2 and 3 with their material’s source colour / one, i.e. the sprite colour squared, and the cast haze textures are dim (their brightest texels are about half of full scale), so the square stayed a dim red. Drawn one / one, a dozen haze layers add up to yellow. Lead (a) is ruled out: the Godot compatibility renderer used here adds the stored values (no sRGB step on output: 0.5 reads back 128, 0.5 + 0.25 reads 191). Render probe (godot/tests/render_flash.gd, play camera, 1280 × 720), mean of a 120 px box at the chest: tick 16 (168,117,47) → (191,140,43), tick 20 (120,53,47) → (170,95,51); the PC footage at the same moment ≈ (216,192,60). Still open: after the release the rebuild turns red within about two ticks where the game stays yellow for about eight (leads: the release cloud’s joint, the body joint at the hips, against the game’s chest-high cloud; the glow pass; the aging rate of the cloud).

4. The red burst

It is the same release instance (slot 3 on the caster), so the game does play it (H): element 0 is an msparticle00 on the body joint at 2 units up (frames 0–5, texture 8, blend 0x1200), elements 2–4 are three particle01 streak emitters on joints 0.7, 1.0 and 1.3 m up (size 300 → 100, the plain red texture 4, 8 per tick, life 25, frames 0–4). In the PC build these read as small orange sparks around the flash. In the rebuild they are large red dots because msparticle00 is still an inferred quad emitter and the point sprites take the Xbox size rule (xbox_sprites in pd_effect.gd); the PC port draws them below a pixel. That part is a port difference: the Xbox recording has visible, small sparks.

5. The green glow around the character is not part of this effect

Green glow and rising ribbons sit on the player character through the whole recording in both builds, stronger with a higher aura level and absent at level 0 (L, footage). It is a separate system the rebuild does not have. Leads in the executable (M that these are the right entry points, nothing inside decoded): the battle class pdBattlePsp (init 0x14019aa30, per tick 0x14019b520) loads and runs an aura script (init 0x14019ac40, per-tick run from 0x14019b7a8), loops over the four players’ positions, draws into the render targets at 0x14054c260 (set up by 0x1402864e0) when bit 0x100000 of 0x14052fff4 is set, and the result goes through the aura-box colour filter (0x140289172); the aura shell meshes (vertex format 0x0B) and the aura effect element are the geometry side. (Corrected 11-14, auraglow: decoded in “Character aura glow, the cast / aura-card flare …” at the end of this file. The shell meshes and the aura effect element are not used by the shipped aura script; the glow is a blurred silhouette of the character.)

6. Skill card at a cast press — contradiction, not resolved

7. Not examined

The wall impact (fire puff, dark smoke, a scorch mark that stays): the pack’s hit slot 2 has only an msparticle00 and one particle01; the mark belongs to “Surface marks”. Not compared.

Implementation notes for the rebuild

Ordered by how visible the change is.

  1. Flash colour and brightness. Probe first: render eft0061 slots 0 and 3 alone and compare with the PC frames; test whether the additive sum is done on encoded or linear values in the compatibility renderer (tests/gpu_blend_probe.gd is the starting point). Fix in pd_effect.gd particle_material only after the probe names the cause.
  2. Stage effect light. Keep one “latest allocated effect light” index beside the pool (set on allocation, never re-picked, cleared at battle setup). Each frame, if that record is live, write its colour, range and position to the stage materials’ p0_* uniforms; otherwise the stage light script’s values. Characters keep their own two-channel pick.
  3. Character aura glow. Needs its own decode run (section 5) before any build work.
  4. No card for a press that starts a cast, and aura paid at the release tick. The first is from footage until the missing gate is decoded; list it as such.
  5. Body yaw during the cast. Fix the cast yaw at the cast start, turn by the turn step per tick, and let neither camera nor lock-on turn the body for the 40 ticks. Verify with a run that logs the body yaw per tick during a locked cast while the camera orbits.
  6. Spark size. Follows the msparticle00 decode and the point sprite size choice.