Skip to content

feat: add double jump and glide fields to AvatarLocomotionSettings#407

Open
decentraland-bot wants to merge 1 commit into
mainfrom
feat/double-jump-and-glide
Open

feat: add double jump and glide fields to AvatarLocomotionSettings#407
decentraland-bot wants to merge 1 commit into
mainfrom
feat/double-jump-and-glide

Conversation

@decentraland-bot
Copy link
Copy Markdown
Contributor

Summary

  • Adds three missing fields to PBAvatarLocomotionSettings that already exist on the experimental branch (added in PR feat: double jump and glide #340 "feat: double jump and glide", merged 2026-03-02):
    • double_jump_height (field 7) — Height of the double jump (in meters)
    • gliding_speed (field 8) — Maximum speed when gliding (in meters per second)
    • gliding_falling_speed (field 9) — Maximum falling speed when gliding (in meters per second)
  • These fields are already consumed by unity-explorer/dev and were left out when the base AvatarLocomotionSettings component was promoted to main via PR feat: locomotion settings #398.
  • The other changes from PR feat: double jump and glide #340 (Movement.jump_count, Movement.glide_state/GlideState enum in comms.proto, and disable_double_jump/disable_gliding in PBInputModifier) are already present on main.

Context

Test plan

  • Verify proto file compiles without errors
  • Verify field numbers 7, 8, 9 match experimental branch exactly
  • Verify no breaking changes to existing field numbers 1–6

Requested by Nico Earnshaw via Slack

Add three missing fields to PBAvatarLocomotionSettings that already
exist on the experimental branch:
- double_jump_height (field 7)
- gliding_speed (field 8)
- gliding_falling_speed (field 9)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

Test this pull request

  • The @dcl/protocol package can be tested in scenes by running
    npm install "https://sdk-team-cdn.decentraland.org/@dcl/protocol/branch//dcl-protocol-1.0.0-25917707223.commit-7110989.tgz"

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.

3 participants