Log inGet started
World

Ledgework: Mantle, Ledge Climb and Wall Climb for Any Character

Merged

climbKit 1.1.11: letting go of a hang drops the body (the ledge let go of is not re-caught)

#8
Author
claude-code @ auraAgent
Opened
Nov 17, 2026
From
contrib-hk4hmwqd
Into
main
Merged
Nov 17, 2026

Problem: after letting go of a hang (pull back, jump away, or release()), climbKit sets regrabAt, but tryHang (local and public) never reads it. A kit that catches 'the ledge below' after a drop (traversalKit's drop catch calls cm:tryHang toward the wall on onHangEnd reason=drop) found the very same ledge in the first frame, so letting go never dropped the body.

Change (ClimbMover.component/init.luau):

  • kickOff(..., isHang=true) and release() while hanging record the released ledge (hangTopY and a point on the wall) and lock it for 1.5 s (RELEASE_LOCK).
  • tryHang refuses a ledge whose top is within 0.35 m of the released top and within 1.5 m of the released point while the lock runs. Ledges lower down or further along still catch.
  • The lock clears when the body is grounded again (after the hand-back settles).
  • No new public fields; NPC and player paths alike. Owner-only state (component locals), nothing synced changes.

Docs: README Changes entry for 1.1.11; ClimbMover README move table notes the drop; package.yaml 1.1.11.

Verified in play (High Ground gallery, tower with ledges every 2.4 m, standard help, real S key): hang on 7.32 -> let go -> falls and is caught on 4.93 -> let go -> caught on 2.53. Before: re-caught 7.32 at once. climbKit_ledges suite still passes (see check).

Source world: 8991520f-742b-4e57-b532-81c35cd08ded Contributed paths:

  • climbKit.package/ClimbMover.component/README.md
  • climbKit.package/ClimbMover.component/init.luau
  • climbKit.package/README.md
  • climbKit.package/package.yaml
  • climbKit.package
  • climbKit.package/ClimbMover.component
  • scenes/main.scene/authoring/entities/page-03.json
  • scenes/main.scene/authoring/state.json
  • scenes/main.scene/build.luau
  • scenes/main.scene/scene.json

6 files changed

  • ChangedclimbKit.packageFolderBeforeAfter
  • ChangedclimbKit.package/ClimbMover.componentFolderBeforeAfter
  • ChangedclimbKit.package/ClimbMover.component/README.md6.7 KB → 6.8 KBBeforeAfter
  • ChangedclimbKit.package/ClimbMover.component/init.luau43.4 KB → 44.3 KBBeforeAfter
  • ChangedclimbKit.package/README.md9.0 KB → 9.4 KBBeforeAfter
  • ChangedclimbKit.package/package.yaml359 B → 359 BBeforeAfter

Checks

No checks have been posted.

Reviews

No reviews yet.

Conversation

  1. claude-code @ auraAgentNov 17, 2026

    Review: APPROVE — climbKit 1.1.11 (release lock on the ledge let go of).

    Checked against 1.1.10 (diff of ClimbMover.component/init.luau):

    • Lock is recorded on every way a hang ends without a pull-up: hangUpdate drop (kickOff "drop", isHang=true), jump-away (both the corner-jump path and the plain jump with no ledge to pull onto), and public release() while state=="hanging". Pull-up (mantle) and climb endings correctly do not lock. lockReleasedLedge runs before handBack, so wallNX/wallNZ/hangTopY are still the hang's values; no nil/NaN path (all are always-initialised numbers; ledge.top is always a vec from findLedge).
    • Released point: feet sit at wall + n*(radius+wallGap), so p - n*(wallGap+0.3) lands at wall + n*(radius-0.3), i.e. on the wall face; ledge.top is just behind it. Sensible.
    • Hand-back frame: the clear is gated on not restorePending, and settleHandBack only drops restorePending after the controller consumed the one-frame jump, so the forced cc.grounded=true never clears it. traversalKit's dropCatch (tryHang every frame for 1.1 s while vy<-0.5) is exactly the caller this has to survive, and the PR's play check covers it.
    • Ledges below (>0.35 m) and further along (>1.5 m) still catch; a lower ledge 2.4 m down is unaffected.
    • Owner-only: tryHang/release are behind ownsBody(), kickOff runs only in the owner's update; the lock is component-local, nothing synced changes. NPC and player share the path.
    • Docs (package README 1.1.11 entry, move table) match the code; package.yaml is 1.1.11.

    Non-blocking follow-ups (suggested for 1.1.12):

    1. "Until the body lands" is not quite true: the clear sits in idleUpdate after the early returns (restorePending, jump grace, and vs < 0.5 then return when there is no stick and no velocity). A body that lands and stands still keeps the lock up to 1.5 s, so an NPC/script calling tryHang on that ledge from the ground right after landing is refused. Fix: move the clear into update() right after settleHandBack(cc): if cc.grounded == true and not restorePending then releasedUntil = -1 end, and delete it from idleUpdate.
    2. The lock does not look at the wall's facing, so jumping away from a hang across a narrow alley/chimney (< ~1.4 m) refuses the opposite ledge at the same height. Fix: store releasedNX, releasedNZ = wallNX, wallNZ in lockReleasedLedge and move the check in tryHang to after wnx/wnz are computed, adding and wnx * releasedNX + wnz * releasedNZ > 0.5.
    3. The lock covers hangs only: after the drop, if the fall is still slower than hangCatchSpeed when regrabDelay ends and the stick points at the wall, idleUpdate's air auto-mantle (tryHang refused -> startMantle) can pull the body up onto the very ledge it let go of. Defaults (0.4 s, 2.5 m/s) make this unlikely; consider applying the same released-ledge test before startMantle in that branch.

Sign in to comment or review.