7dd754f8e4
What I wanted from the new state: `ui_layout::sprite_blend_additive` and its three siblings, which expose `T8aD +0x04` bit 0x02 -- the decoded blend mode. Until this tag, `Element` surfaced `kind` (+40), `parent`, pivot, keyframes and `focus_link`, all from the RATC record, and nothing reached the sprite's own header. That is why the port has been carrying an authored additive map keyed by SCREEN NAME, transcribed from the Decoder's per-draw RB_BLENDCONTROL0 log, which cannot answer for a screen nobody drove the game to -- the Japanese menus being the case that raised it. Both spellings are needed, not one: `sprite_blend_additive` takes an &Element, and `blend_additive_by_name` takes a sprite name, because a button's focused variant is reached through focus_link and `ptbtn00f.t32` is in build.sprites while no element carries it as `sprite`. That is exactly the sharp case in my own map -- press_start's only additive entry IS ptbtn00f. Pin bumped as its own commit, per PORT-MISSION §2. Nothing else in this commit; the exporter does not read the new accessors yet. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018AHUQvXGyNcKonSEWsgWcX
91 lines
5.6 KiB
TOML
91 lines
5.6 KiB
TOML
[package]
|
|
name = "sylpheed-export"
|
|
description = "Convert a Project Sylpheed disc into the open asset tree the Godot port reads"
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
|
|
[dependencies]
|
|
# The decoders, PINNED BY REVISION. Not vendored and not reimplemented: they are
|
|
# disc-wide verified in their own repository, and floating the pin would let a
|
|
# decoder change land mid-milestone -- exactly the confusion this prevents.
|
|
#
|
|
# `sylpheed_formats::media` in particular owns the cases where one playable thing
|
|
# is not one archive entry (segment-spanning reads, multi-sub-wave banks, and the
|
|
# continuous cutscene-voice stream). Do not re-derive those here.
|
|
#
|
|
# Pin moved f817dd5 -> 7eeae30 on 2026-08-29. WHAT I WANTED FROM IT: `UiBuild`
|
|
# gained a public `records` map (record name -> the nested `.rat` leaf's byte
|
|
# range). Without it a consumer could not locate a leaf at all: `parse_build`
|
|
# sorted T8aD children into `sprites` and `.rat` children into a PRIVATE map, so
|
|
# the focus ring -- which lives inside `ptbtn0Nf.rat`, a record the parent
|
|
# bundle declares no element for -- was unreachable through the public API.
|
|
# Also brings `Keyframe::rotation_deg`, which the game does render.
|
|
#
|
|
# PINNED BY TAG, not by sha, and MISSION §2 now requires it. The reachability
|
|
# risk this comment used to warn about is closed: a sha reachable only from an
|
|
# `auto/*` branch is orphaned when that branch is deleted or -- worse --
|
|
# SQUASH-MERGED, because squash creates new commits, so `main` would look like
|
|
# it contained the work while this pin became unreachable. A tag is a permanent
|
|
# ref, it says what it is here in the file, and it fails loudly at FETCH rather
|
|
# than silently at build. `formats-pin-2026-08-29` is 7eeae30.
|
|
#
|
|
# Previous pin note, kept because the reasoning still holds:
|
|
# Pin moved 5414db3 -> f817dd5 on 2026-08-29. WHAT I WANTED FROM IT: `56cc7ac`,
|
|
# "a RATC child's name is stated, not inferred". A child was named by scanning
|
|
# backwards for the last printable run before its magic; for `pteff05.t32` the
|
|
# three trailing payload bytes are `38 41 58` = `8AX` and beat the real name, so
|
|
# the FULL-RESOLUTION BACKGROUND OF ALL FIVE MENU SCREENS registered under a
|
|
# name no element declares and resolved to no sprite. This port exported those
|
|
# screens without their background and said so in every render as "pteff05 (no
|
|
# sprite in the export)" -- which docs/DECISIONS.md then wrote up as correct.
|
|
# It was not. f817dd5 is the last commit touching `crates/` on that branch.
|
|
#
|
|
# Previous pin note, kept because the reasoning still holds:
|
|
# Pin moved 8b6dbcf -> 5414db3 on 2026-08-28. WHAT I WANTED FROM IT: the fix to
|
|
# `ui_layout::rest()`. At 8b6dbcf a trailing run of identical keyframes was
|
|
# always treated as the exit, so an element with no exit animation rested at its
|
|
# invisible pre-roll -- `ptframe1`/`ptframe2`, the main menu's circuit bracket,
|
|
# which a capture of the running game plainly shows. 5414db3 is the revision at
|
|
# which that fix carries its disc-wide check (30 of 13 991 elements move, 4
|
|
# become visible, 0 become invisible), not merely the one where it was written.
|
|
# A PATH dependency now that the decoders and the exporter live in one
|
|
# repository. This deletes a whole class of failure that the two-repo split
|
|
# created: no pinned revision to go stale, no tag to keep alive, no commit that
|
|
# a squash-merge can orphan, and no way for the exporter to be built against a
|
|
# decoder it was never tested with. A decoder change and the exporter change it
|
|
# requires now land in the same commit or not at all.
|
|
# PINNED BY TAG, which is what MISSION section 2 prescribes and what the tagging
|
|
# rule exists for: "the RE agent tags when it lands something you need and tells
|
|
# you over the message channel -- that is how you stay current without floating."
|
|
# That is exactly what happened here.
|
|
#
|
|
# The tag carries the CORRECTED keyframe association: a placement group is an
|
|
# 8-byte header then `frames` x {u32 time; 36-byte pose}, so pose 0's time is the
|
|
# group's lead-in word and EVERY POSE IS TIMED, including the last. The working
|
|
# tree's copy still has the retired `SYLPHEED_KF_TIME_SHIFT` knob -- a superseded
|
|
# partial fix that got the association right but left pose 0 untimed, which is
|
|
# why testing it moved the untimed frame from last to first instead of removing
|
|
# it. The old reading is behind `SYLPHEED_KF_TIME_LEGACY=1` here.
|
|
#
|
|
# 🔴 THE COST, STATED: `sylpheed-cli` builds from the WORKSPACE crate, so until
|
|
# this lands on `main` the exporter and the reference renderer read DIFFERENT
|
|
# decoders and `tools/port/verify-screen` is comparing two eras rather than
|
|
# detecting drift. `tools/port/verify-capture` is unaffected -- it compares the
|
|
# port against oracle CAPTURES and never touches the CLI -- and it is the check
|
|
# that matters. Revert to the path dependency the day the tag is an ancestor of
|
|
# `main`.
|
|
# Bumped c -> d 2026-08-29. What I wanted from the new state: `d` carries parser
|
|
# and `audio.rs` changes on top of `c`. ⚠️ Its headline change -- Reborn's
|
|
# renderer drawing `rotation_deg`, and `compose` drawing a leaf that carries
|
|
# geometry -- does NOT reach this port from here: `sylpheed-cli` builds from the
|
|
# WORKSPACE crate, so the reference renderer stays unrotated until the tag lands
|
|
# on `main`. This bump is for the parser, not for the renderer.
|
|
sylpheed-formats = { git = "https://git.mc02.dev/fabi/Sylpheed.git", tag = "formats-pin-2026-09-01" }
|
|
|
|
serde = { version = "1", features = ["derive"] }
|
|
serde_json = "1"
|
|
anyhow = "1"
|
|
clap = { version = "4", features = ["derive", "env"] }
|
|
image = { version = "0.25", default-features = false, features = ["png"] }
|