Skip to content

Apply jumpPenalty to diagonal ascents - #5153

Merged
leijurv merged 1 commit into
cabaletta:1.21.4from
EvModder:pr/diagonal-ascend-jump-penalty
Oct 21, 2026
Merged

leijurv merged 1 commit into
cabaletta:1.21.4from
EvModder:pr/diagonal-ascend-jump-penalty

Conversation

@EvModder

@EvModder EvModder commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

MovementDiagonal presses jump to ascend, but unlike MovementAscend, MovementPillar, and MovementParkour its cost never includes jumpPenalty. Since bf03a00 (2019), raising jumpPenalty to discourage jumping has made diagonal ascents relatively cheaper, so paths reroute their jumps instead of avoiding them.

This adds context.jumpPenalty to the diagonal ascend cost.

Diagonal ascents are only considered with allowDiagonalAscend (default false), so default behaviour doesn't change. With it enabled and the default penalty of 2, one diagonal ascend now costs about 11.7 ticks, against about 11.3 for a traverse followed by an orthogonal ascend (9.7 before this change). In practice, a diagonal hop is also a slower one.

MovementDiagonal presses jump to ascend, but its cost omitted
jumpPenalty, which every other jumping movement (ascend, pillar and
parkour) charges. Raising jumpPenalty therefore made diagonal ascents
relatively cheaper than orthogonal ones, rerouting jumps instead of
avoiding them.
@EvModder
EvModder marked this pull request as ready for review October 21, 2026 03:21
@leijurv
leijurv merged commit 62c784d into cabaletta:1.21.4 Oct 21, 2026
1 of 2 checks passed
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.

2 participants