docs: file #338 — player steps at 0.400 where Setup 0x02000001 authors 0.600/1.500

Spotted in the #337 [support] capture and deliberately left out of that
fix so the fix stayed falsifiable. Filed with what is NOT established
attached: whether retail reads the authored Setup field at all is the
first question, and the entry says to grep named-retail before touching
anything. The #337 lineage already burned two diagnoses reasoned from
source.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-06 22:17:28 +02:00
parent ea83b043df
commit 3171f43002
2 changed files with 41 additions and 1 deletions

View file

@ -24,6 +24,46 @@ What does NOT go here:
- Every session: scan OPEN issues at start; promote/close anything we touched during the session before ending.
- Promoting to a Phase: mark as `DONE (promoted to Phase X)` + commit SHA where the Phase entry landed.
## #338 — The player resolves with stepUp/stepDown 0.400 where Setup 0x02000001 authors 0.600 / 1.500
**Status:** OPEN
**Severity:** unknown until measured, plausibly medium. A 1.5 m step-down is
what keeps a mover attached to a descending slope; 0.4 m is not, so this is a
candidate contributor to descent/edge feel — but that link is NOT established
and must not be assumed.
**Filed:** 2026-08-06, spotted in the #337 `[support]` capture while chasing a
different defect. Deliberately not chased there: it does not cause the Neftet
wedge, and folding it in would have made that fix unfalsifiable.
**Component:** physics / movement.
### The observation
The human Setup `0x02000001` authors `StepUpHeight = 0.600` and
`StepDownHeight = 1.500`. The live `[support]` probe lines show the player
resolving with `stepUp=0.400 stepDown=0.400`.
### What is NOT yet established
- Whether the authored Setup values are what retail feeds `CPhysicsObj`, or
whether retail also substitutes constants at this seam. **Grep
`named-retail` for `get_stepup_height` / `get_stepdown_height` and their
callers before touching anything** — the authored DAT field being ignored is
only a defect if retail reads it.
- Where the 0.400 comes from: a hardcoded default, a stance/posture-dependent
value, or a value that never got wired from the Setup.
- Whether it has any observable consequence. Do not open this by reasoning
from the source; the #337 lineage already burned two diagnoses that way.
### Related
Sits next to #32 (local-player cliff edge-slide), which has its own research
at `38db9fff` and needs a live `ACDREAM_DUMP_EDGE_SLIDE=1` capture before a
fix. If both turn out to touch descent feel, do NOT bundle them — they have
different mechanisms and need separate gates.
---
## #337 — Neftet rock plateaus: wedged at the top, jumps sink into the mesh, corpses fall through — FIXED, awaiting live acceptance
**Status:** FIXED 2026-08-06 by #333's fix — the query-site broadphase reach

View file

@ -270,7 +270,7 @@ Dropping the columns would make the two captures incomparable.
---
## Separate observation, not part of this defect
## Separate observation, not part of this defect — now filed as #338
Setup `0x02000001` authors `StepUpHeight = 0.600` and
`StepDownHeight = 1.500`. The live `[support]` lines show the player resolving