Climbing's geometric fallback is 53.6% exact, and plane-1 landings fall into void #54
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
World.Climbing.Geometrycovers the{placement, action}pairs the transportdump never saw. Measured against the pairs the dump does cover, it is 96.7%
plane-correct and only 53.6% exact — so roughly half of the staircases it
answers for put the player on the wrong tile of the right floor.
Destination validation itself is no longer missing (#19 closed that;
Contract.Landingnow refuses a destination that is not standable). Two thingsremain:
The accuracy itself. Half-wrong is good enough to be unnoticeable in
testing and bad enough to be reported constantly once people use stairs a lot.
Landing on plane 1 outside a building drops you onto open void, and the
landing check cannot see it. No plane above
0carries a blocked-floor flagin the flag build, so an upper-floor tile with nothing on it reads as ordinary
open ground rather than as a hole.
Contract.Landingtherefore accepts it. Thefix is not in
Landing— it is that the flag build has no notion of "there isno floor here" above ground level, which is a decode question rather than a
rules one.
Blocking for a stable release: a staircase is a thing every player uses in
their first ten minutes.