fix(re-capture): name_block_bases reads the disc from $SYLPHEED_DISC, loudly #44
Reference in New Issue
Block a user
Delete Branch "fix/name-block-bases-disc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
name_block_bases.py's data-table section globbed/work/sylph_extract/**/*.pak, which has existed nowhere since/workbecame a clone. It matched nothing and reported "0 disc names" with no error. The committed artefact records 13,450, from back when that path existed. The disc now comes from$SYLPHEED_DISC, and running without it is an error (exit 1).Verified: with
SYLPHEED_DISC=…/sylph_extract, the section reproduces the committed figures exactly: 13,450 names, 50 / 261 rows,sub_82341A20 r30 0x82088F94 217 names 89% disc. Without the disc it exits 1.⚠️ The artefact is deliberately not regenerated
Rebuilding
docs/re/data/name-block-bases.txtfrom the current database changes findings: solved bases move, three perfect 15/15 rows vanish, and the file loses 280 lines. The cause is the database, not this script.The string extractor's Shift-JIS path requires kana, so kanji-only Japanese never reaches
strings. That includes the allocator's debug lines, e.g.32B 未開放 %4d : 最大…使用量 %4d / %4d. The bases those names pinned no longer resolve:sub_8285F2C8 r5@0x820AE7ACgot 15/15 before and 7 now. The rule is a precision trade-off: of the 133 strings it rejects, the sample is mostly binary noise (%垂MAp). Loosening it is a heuristics decision, and regenerating first would bake the loss into an artefact thatplayer-tuning-tables.mdcites.🤖 Generated with Claude Code