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.

Sign up for GitHub

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

Jump to bottom

Velocity completely broken. #1168

Closed
MastaNub opened this issue Apr 24, 2019 · 2 comments
Closed

Velocity completely broken. #1168

MastaNub opened this issue Apr 24, 2019 · 2 comments
Labels
Bug The issue is a fault in the expected behavior of the application
Projects
Impact Bugs
Milestone
4.7

Comments

@MastaNub
Copy link

Describe the bug
Velocity is completely broken. I don't even know what's happening but it's entertaining.

To Reproduce
Just turn it on. Default settings.

Expected behavior
Should work like it did back in 1.12.2 4.4.

Videos
https://youtu.be/oDt61NehT4w
https://youtu.be/tsGfz_wbuyo

Additional Client Info
  • Impact Version: 4.6 for 1.13.2
  • Using Optifine? Yes
  • Using LiteLoader? No
  • Enabled mods: Velocity on 100% 100% Yes Yes 100%
  • Operating System: windw10
@MastaNub MastaNub added the Bug The issue is a fault in the expected behavior of the application label Apr 24, 2019
@MastaNub MastaNub changed the title Please add a brief but descriptive title Velocity completely broken. Apr 24, 2019
@leijurv leijurv added this to Needs triage in Impact Bugs via automation May 29, 2019
@leijurv leijurv added this to the 4.7 milestone May 29, 2019
@leijurv
Copy link
Member

leijurv commented Jun 3, 2019

This is a combination of one bug, and one user error. The user error is that those sliders are what percentage of knockback you take, if you want the Velocity module to do anything they need to be at not 100%. 100% means it does nothing. The actual bug that I'm going to fix is that knockback inversion (like reverse knockback) setting defaults on, which is extremely confusing and a bad decision. Gonna make it default off.

@leijurv leijurv closed this as completed Jun 3, 2019
Impact Bugs automation moved this from Needs triage to Closed Jun 3, 2019
@leijurv
Copy link
Member

leijurv commented Jun 3, 2019

Fixed in 4.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug The issue is a fault in the expected behavior of the application
Projects
Impact Bugs
  
Closed
Milestone
4.7
Development

No branches or pull requests
2 participants
@leijurv @MastaNub