Ledger: Skill bench: what the game’s debug viewer can settle
The debug character viewer plays any skill
record by number with its real cast code, on PC
and on Xbox (xemu), frame-stepped, from a camera
we set as numbers (FORMATS “Debug character
viewer: the skill bench”;
tools/bench/bench.sh). It is an
answer key, not a build: nothing below is
implemented by it. Shots stay private. xemu
output is “xemu-based”, never proof of console
particle sizes.
Rebuild side of the bench (viewer mode: same skill, camera, tick as a third row)
- Status: built (viewer)
- Now:
godot/tests/render_viewer.gd,bench.sh --target afterlife(all= PC + xemu + ours): the “Afterlife Dust” row, the viewer’s camera formula (checked to 1 px bytools/bench/viewer_camtest.py), one PNG per 30 Hz tick,chara_posper tick in game units. The list number is ourskills.jsonrecordfield, notid
Viewer look of the character (flat green, no light set)
- Status: PLACEHOLDER (viewer)
- Now: Ours draws the
character unlit with its own texture
(
--lit: our normal character shading); the sheet labels the row “unlit”. Body colour is not compared, the effect is - Where:
render_viewer.gd_unlit. Lead: where the viewer’s flat green comes from (its draw with no light set), not traced
Viewer text (list, header, motion / frame line)
- Status: not drawn (viewer)
- Now: Our row has none (the PC row hides it with a private exe copy, xemu keeps it)
- Where: — (not needed)
Glow pass in the viewer scene
- Status: INFERRED (viewer)
- Now: Our viewer mode draws no glow pass (no stage to feed it)
- Where:
render_viewer.gd. Lead: whether the viewer’s draw (PC 0x14015e050) runs the battle glow pass
Cast root motion moves the body
- Status: MISSING (viewer)
- Now: The game moves the
character by the cast slot’s root track with no
stick (list 61,
chara_pos: x up to 0.81, z down to −3.36 units by tick 16, back near 0 by tick 28; PC = Xbox to the third decimal); ours strips the track and the body stays at the origin on every tick - Where:
pd_character.gdroot strip,player.gdcast. Lead: bench runviewer-61(chara_posper tick, three targets); the “Root joint of a model” row
Straight shot leaves the hand on the release tick
- Status: MISSING (viewer)
- Now: List 61: the game’s
shot is out of the hand on tick 20; ours draws
it one tick at the feet on tick 21 and in flight
from tick 22 (the
Projectilenode exists from tick 22) - Where:
projectile.gd/data_skill.gdrelease. Lead: bench runviewer-61(every tick 1..35 of ours; PC every third tick)
Effects left on the caster after the release (list 61)
- Status: MISSING (viewer)
- Now: PC and xemu-based show no effect on the body from tick 25 on; ours keeps a red particle cloud on the body and arm on ticks 25..31
- Where:
pd_effect.gdslots of the cast. Lead: benchviewer-61presets right / front34, ticks 25..31; “Release tail” row below
Cast motion slot per skill
- Status: checked (scout sweep)
- Now: 354 of 374 list numbers play the slot we decode, 12 more are idle in both; record 230 plays the jump-start slot (a levitate: see “Levitate float animation”); records 262 and 282 idle against our slot 93 (L, check in a battle)
- Where: “Cast motion slot and release tick”, “Levitate float animation”
Reaction and effect ids per skill
- Status: checked (scout sweep)
- Now: The header’s three
reaction ids and effect id equal
skills.jsonfor all 374 - Where: Skill table
Cast pose of the straight fire shot
- Status: can settle now
- Now: The viewer shows
motion slot 70 for record 61 on both builds, the
slot we decode: the open part is the pose inside
the slot (hand beside the head), comparable tick
by tick from the
rightandfront34presets - Where: “eft0061 skill cast pose”
Hand bone the forming effect follows
- Status: can settle now
- Now: Step ticks 1..19 from
right/top: the forming effect’s centre against the hand joint - Where: “Hand bone the forming effect follows”
Effect slot meanings up to the release (forming, launch, flight, trail)
- Status: can settle now
- Now: Effects on / off on the same tick separates body from effect; the hit slot never plays (no target)
- Where: “Effect slot meanings”
Effect mesh roll sign
- Status: can settle now
- Now: An asymmetric rolling
mesh stepped tick by tick from
front - Where: “Effect mesh roll sign”
Release tail of the straight fire shot (colour, length)
- Status: can settle now
- Now: Ticks 20..31 from
righton PC and xemu-based - Where: bof audit rows
Point-sprite size, PC against Xbox
- Status: PC side only
- Now: PC is exact; xemu draws some sprites too small, so the Xbox size stays the decoded one
- Where: “Point-sprite meshes”, “Point-sprite size limit”
Multi-shot and bundled shots on PC
- Status: can settle now
- Now: Record numbers play on PC with no arsenal or aura set-up
- Where: skill kind rows
Hits, explosions on a body, flames left on a hit character, stage light from effects, sound
- Status: can’t
- Now: The viewer has no target, stage or sound path
- Where: their rows keep footage / battle captures
Skill records 375..386
- Status: can’t
- Now: Not in the viewer’s list