fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: my language-sprite reading is refuted, and 'EN/JP pair' is withdrawn from the DIFFICULTY row

Browse Source 
sylpheed-port refuted the untested reading I recorded yesterday with a count, and I
reproduced it: 26 of 65 adjacent GP_DIALOG pairs differ in BUTTON COUNT, which two
languages of one dialog cannot. The names agree once read rather than counted --
ranking_NEXT against ranking_JUMP, py_ranking against pzeff, pzstg10 against
pzstg02.

So adjacent entries are unrelated dialogs, the 63 never needed the language
reading, the 2 matching pairs need no special account, and the 140:70 ratio is a
counting coincidence -- the same fact my halves-pairing zero was showing from the
other side.

Preserving their caution: this does not establish that 0/1 and 2/3 ARE language
pairs. Identical element sets is equally consistent with a duplicate, and for the
37 pairs differing without a button-count mismatch the language reading is
unsupported rather than refuted.

Withdraws a delivered claim: I called entries 2/3 'an EN/JP pair' in HANDOFF. The
DIFFICULTY identification does not rest on it -- unique geometry plus the capture
does -- but it was stated as fact and was not one.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-31 02:57:47 +00:00
parent 843f27b506
commit 2df5b04768
3 changed files with 89 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

45
crates/sylpheed-formats/examples/dialog_pair_button_counts.rs Normal file
View File

@@ -0,0 +1,45 @@
//! Do adjacent `GP_DIALOG` entries differ in BUTTON COUNT?
//!
//! I offered an untested reading for why 63 of 65 adjacent pairs have different
//! element sets: dialog text baked into language-specific sprites, so EN/JP
//! entries differ by construction. `sylpheed-port` refuted it with a count — two
//! languages of one dialog cannot differ in how many buttons they have. This
//! re-derives that with my own reader before I record the refutation.
//!
//! cargo run -p sylpheed-formats --example dialog_pair_button_counts
use sylpheed_formats::{pak::PakArchive, ui_layout};
use std::path::PathBuf;
fn btns(ar: &PakArchive, i: usize) -> Option<usize> {
let by = ar.read(&ar.entries()[i]).ok()?;
let b = ui_layout::parse_build(&by)?;
Some(b.elements.iter().filter(|e| e.name.contains("btn")).count())
}
fn main() {
let root = PathBuf::from(std::env::var("SYLPHEED_DISC").expect("SYLPHEED_DISC"));
let ar = PakArchive::open(root.join("dat/GP_DIALOG.pak")).expect("GP_DIALOG");
let n = ar.entries().len();
let (mut diff, mut same, mut skip) = (0, 0, 0);
let mut show = 0;
for k in (0..n).step_by(2) {
match (btns(&ar, k), btns(&ar, k + 1)) {
(Some(a), Some(b)) => {
if a != b {
diff += 1;
if show < 6 {
println!(" entries {k:3}/{:<3} button counts {a} vs {b}", k + 1);
show += 1;
}
} else {
same += 1
}
}
_ => skip += 1,
}
}
println!("\nadjacent pairs differing in BUTTON COUNT: {diff}");
println!("adjacent pairs with equal button counts : {same}");
println!("unreadable : {skip}");
println!("\ntwo languages of one dialog cannot differ in button count.");
}

2
docs/port/HANDOFF.md
View File

@@ -46,7 +46,7 @@ delivered.
| route | evidence |
|---|---|
| **image** | `0x820A41BB` lists **`DLG_SELECT_DIFFICULTY`** among the `DLG_*` dialog names, beside `DLG_MESSAGE_BOX`, `DLG_SYSTEM_PAUSE`. `GP_DIFFICULTY` appears **0** times |
| **disc** | `GP_DIALOG` entries **2/3** are the only builds there with `pcbtn00`–`03` — four buttons at design y **259/329/399/469**, spacing **70**, an EN/JP pair |
| **disc** | `GP_DIALOG` entries **2/3** are the only builds there with `pcbtn00`–`03` — four buttons at design y **259/329/399/469**, spacing **70**. ⚠️ ~~an EN/JP pair~~ — **withdrawn**: adjacent `GP_DIALOG` entries are generally *unrelated dialogs* (26 of 65 adjacent pairs differ in **button count**, which two languages cannot), so identical element sets here is **equally consistent with a duplicate**. The identification of the build does not rest on the pairing |
| **oracle** | my capture of the running screen puts its four rows at 323.5/394.0/463.5/533.5 — within **4 px** of those, spacing 70.5/69.5/70.0 against the disc's 70/70/70 |
📌 **Two consequences for you.**

44
docs/re/data/difficulty-is-a-dialog.txt
View File

@@ -26,7 +26,10 @@
# EASY / NORMAL / HARD / BACK. Design rows and spacing:
#
# entry 2 y 259 / 329 / 399 / 469 spacing 70, 70, 70
# entry 3 identical (the EN/JP pair, as everywhere else)
# entry 3 identical (⚠️ called "the EN/JP pair" here and
# WITHDRAWN 2026-08-31 -- see the section
# at the end; adjacent GP_DIALOG entries
# are generally unrelated dialogs)
#
# ✅ CONTROL: the same reader on GP_TITLE entry 5 returns 162/242/322/401/482,
# spacing 80 -- the rows that archive is independently known to place.
@@ -145,3 +148,42 @@
# => The join stays unbound. Table gives name -> id; disc gives a unique build;
# the tie is uniqueness plus the oracle capture. Positional ordering is now
# ruled out as the missing pointer, which narrows where to look next.
################################################################################
# 🔴 MY UNTESTED READING IS REFUTED, and it inverts the puzzle rather than
# solving it. 2026-08-31, sylpheed-port, re-derived here with my own reader.
#
# I offered: dialog text may be baked into language-specific sprites, so EN/JP
# entries differ in element names by construction -- which would explain the 63
# differing pairs and leave the 2 matching ones needing their own account.
#
# ❌ **26 of 65 adjacent pairs differ in BUTTON COUNT.** Two languages of one
# dialog cannot: a locale changes the glyphs on a button, not how many there are.
# Reproduced independently (examples/dialog_pair_button_counts.rs): 26 differing,
# 39 equal, 5 unreadable -- their count exactly.
#
# entries 6/7 2 vs 3 entries 44/45 2 vs 0
# entries 8/9 2 vs 0 entries 46/47 2 vs 0
#
# And the names say it once read rather than counted: 6/7 is ranking_NEXT against
# ranking_JUMP, 8/9 is py_ranking_* against pzeff*, 10/11 is pzstg10 against
# pzstg02 -- different subsystems, different stages.
#
# 📌 SO THE PUZZLE DISSOLVES INSTEAD OF DEEPENING. Adjacent GP_DIALOG entries are
# simply UNRELATED DIALOGS. The 63 never needed the language reading, so the 2
# that match need no special explanation either, and the 140:70 ratio is a
# **coincidence of counting, not a pairing** -- which is the same fact my own
# halves-pairing result of 0 was already showing from the other side.
#
# ⚠️ AND THE CAREFUL PART, which is theirs and which I am preserving: this does
# NOT establish that 0/1 and 2/3 ARE EN/JP pairs. Identical element sets is the
# signature in GP_TITLE; here it is equally consistent with a DUPLICATE. And 37
# of the 63 differ WITHOUT a button-count mismatch -- for those the language
# reading is UNSUPPORTED, not refuted. What is refuted is it as an explanation of
# the 63, which is what I offered it as.
#
# 🔴 CONSEQUENCE FOR A DELIVERED CLAIM: I described entries 2/3 as "an EN/JP pair"
# in HANDOFF.md and above. **Withdrawn.** The DIFFICULTY identification does not
# rest on the pairing -- it rests on the unique four-button geometry (0 rivals
# disc-wide) plus the oracle capture -- but the pairing was stated as fact and was
# not one.