Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Pitch40 to more efficient angles #5221

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Pilot1782
Copy link

Type of change

  • Bug fix
  • New feature

Description

When Pitch40 mode is selected in ElytraFly, the player will now pitch down to 32-33 deg then after hitting the lower bound, will pitch at the supplied rate to -49 deg. Finally they will pitch down at roughly 0.5 deg/tick until looking at 32-33 deg. These angles come from the findings of this video where said angles are much more optimal than the standard 40/40 profile. Ideally this will net ~3 block of max altitude gain per cycle until ~90 block above the lower bound.

How Has This Been Tested?

In testing in a default superflat single-player world, where the player starts on a tower to y=13, pitch rate of 13, lower bound of -40 and upper bound of 0, the maximum height I achieved was roughly y=51.

Checklist:

  • My code follows the style guidelines of this project.
  • I have added comments to my code in more complex areas.
  • I have tested the code in both development and production environments.

@Pilot1782 Pilot1782 marked this pull request as ready for review February 25, 2025 02:14
@Wide-Cat
Copy link
Collaborator

Wide-Cat commented Mar 1, 2025

Why did you bother making the pitch changes random in a certain range? I don't really see what benefit it has over just using the respective values where appropriate.

@Pilot1782
Copy link
Author

In terms of the effectiveness of the module, it has no change, but to a server running some level of anticheat looking for repeated movements this level of "error" is within the range of a human.

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