From 81b685461371ab42e3ed868cb8f9cdf4c9f14b26 Mon Sep 17 00:00:00 2001 From: Sylpheed RE agent Date: Wed, 19 Aug 2026 05:08:59 +0000 Subject: [PATCH] docs/re: point the ship item at the end-to-end mission-path measurement The entry said the crash blocks it; it now also says how far a run gets (past SELECT DATA, into a cinematic) and that the crash's firing point moves, so nobody goes looking for a menu route around it. --- docs/re/BACKLOG.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/re/BACKLOG.md b/docs/re/BACKLOG.md index 1d901746..f166d4b8 100644 --- a/docs/re/BACKLOG.md +++ b/docs/re/BACKLOG.md @@ -607,4 +607,9 @@ throw, 537 stacked dumps, with `--mem_watch=false`. See [`title-crash-stl-tree.md`](title-crash-stl-tree.md). So a second capital-ship capture needs that crash dealt with first. Everything up -to the save-slot screen is now scripted and works. +to the save-slot screen is now scripted and works, and one run got *past* it — +`SELECT DATA` reached with zero crashes, slot chosen, the game proceeding into a +cinematic — before crashing at the same `0x82307128`. The crash is intermittent +in **where** it fires, not whether, so there is no menu route around it. See +[`title-crash-stl-tree.md`](title-crash-stl-tree.md) for the end-to-end +measurement and for what has been ruled out (`--mem_watch=false`, twice).