Skip to content

PLZA marker walk: count steps with no distance read toward the stop (03.08) - #620

Draft
dayfine wants to merge 5 commits into
plza/0304-save-movedfrom
plza/0308-catch-in-zone
Draft

dayfine wants to merge 5 commits into
plza/0304-save-movedfrom
plza/0308-catch-in-zone

Conversation

@dayfine

@dayfine dayfine commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Depends on #619 (base plza/0304-save-moved; the diff shows only this change).

03.08's catch_more_species walked out of Wild Zone 1 on console B (2026-11-16, run 1): the walk to the 100 stop read 120, then 109, then for about 13 s the marker's digits read nothing or garbage while it kept stepping, and it came out at 37 by a market stall, past the far gate. In runs 2 and 3 the first read at Taunie's rocks was a lone 1 or 4, which was trusted, so the patrol thought it was already at its stop.

The marker walk now steps only on a distance read taken (two of three agree, or within 12 of the last): with none it stands, turns the camera back onto the marker and reads again, logging the stretch; there is no dead reckoning. The patrol's walks toward the objective have a floor of 57 (60, just before the far gate, less the stop slack): reads below it are not taken and a walk toward ends at it, which also rejects the 1 and 4 at the start. The A-prompt B guard in press_a_through_lines from the earlier version is dropped (the walk out had no A press), and the 03.08 plan no longer carries the zone-exit autosave note: that badge was a false one on the green zone walls, and 03.08 starts from 03.07's after_catches autosave.

Tested with the MarkerDistance replay suite (run 1's reads: four steps, it stands at 109 and never takes 42/39/37; runs 2 and 3's start reads give no position), syntax-checked locally; not run on the console yet.

03.08's catch_more_species walked out of Wild Zone 1 (console B,
2026-11-16): the walk to the 100 stop read 109, then the marker's digits
did not read for 13 s while it kept stepping, and it stopped on the first
reads it took again, 37, in the city by a market stall. No Pokemon locked
on there, so ten stops threw nothing. The badge 20 s in was the game's
autosave on leaving the zone.

MarkerDistance (replacing DistanceReads) counts each 0.6 s step since the
last read taken as 3 of the distance, so a walk to a stop ends there when
the digits stop reading. The 03.08 plan notes the autosave; it keeps the
catches' autosave as its save.
03.08 run 2 (console B, 2026-11-16) read a lone "1" at about 135 on the
walk's first look, took it as the start and ended the walk to 100 at
once. A read is now taken when it is near the position (the last read
moved on by the steps since), or when two of the last three reads not
taken agree with it, each moved on by its steps; so the first read
needs three that agree, and a lone misread among them does not hold the
start back.
… MarkerDistance

03.08 run 3 read 1, 1 and 4 with the marker at 120 behind a rock; those
agreed within 12 and ended the walk to 100 at once. A read not taken that,
moved on, is at 0 or less now agrees with nothing. The catch steps' start
read (Taunie's rocks, the walk back to the road) goes through
MarkerDistance too, and the lines after a throw press B, not A, on an A
prompt over the scene (a zone gate's "A Leave").
03.08's walk to 100 stepped on through 13 s of unread and garbage digits
after 109 and came out at 37 in the city (console B, 2026-11-16). Dead
reckoning is gone: the walk steps only on a distance read taken, and with
none it stands, turns the camera back onto the marker and reads again.
The patrol's walks toward the objective never go below 57 (60, just
before the far gate, less the stop slack), and reads below it are not
taken, so the lone 1 and 4 at Taunie's rocks (runs 2 and 3) give no start.

The A-prompt B guard in press_a_through_lines is dropped: the walk out
had no A press. The 03.08 plan drops the zone-exit autosave note: that
badge was a false one on the zone walls; its start save is 03.07's
after_catches autosave.
…locked

Run 4 of 03.08 (console B, 2026-11-16) stood with the marker's digits
under an NPC's speech bubble; re-centering put the marker right back
under it. MarkerDistance now answers every third look in a row with no
read taken with a new view: the camera nudged left, then right (the
marker kept 0.12 of the width off the middle, by its own x), then a
short sidestep across the line to the marker, left then right, out to
two steps each side. After those it is BLOCKED and the walk ends,
logged, without a step on. Every nudge and sidestep is logged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant