Skip to content

Inaccurate knockback from other entities #3636

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

Open
PutterBeanut opened this issue Apr 12, 2025 · 0 comments
Open

Inaccurate knockback from other entities #3636

PutterBeanut opened this issue Apr 12, 2025 · 0 comments
Labels
possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f

Comments

@PutterBeanut
Copy link

Versions

  • Mineflayer: 4.27.0
  • Server: Paper 1.21.4 v225
  • Node: 20.17.0

Description

The Mineflayer bot does not seem to take knockback or be pushed around accurately in a few areas:

  1. Entity Collisions:
    When the bot's hitbox overlaps with another player or mob, there is no mutual pushback as expected. The bot remains stationary instead of being pushed away like a normal entity would.
  2. Excessive Vertical Knockback on ground:
    When punched while standing on solid ground, the bot is knocked vertically much higher than it should be—sometimes even a full block upward, which shouldn't normally happen.
  3. Excessive Knockback in water:
    The same issue occurs when the bot is in water (especially noticeable in 1-block-deep pools). It experiences significantly more knockback than a player or mob would under the same conditions.

Additional context

I am not extremely well-versed in the protocol that backs this library, so it's possible that the issue stems from slight inaccuracies in how movement or velocity is being simulated or handled.

Any ideas? Thank you in advance!

@PutterBeanut PutterBeanut added possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f labels Apr 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Stage1 just created by someone new to the project, we don't know yet if it deserves an implementation / a f
Projects
None yet
Development

No branches or pull requests

1 participant