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

Longbows (seemingly) always fire at maximum velocity #5206

Closed
snackerpirater opened this issue Apr 3, 2024 · 1 comment
Closed

Longbows (seemingly) always fire at maximum velocity #5206

snackerpirater opened this issue Apr 3, 2024 · 1 comment
Labels
1.19 Issue affects 1.19 Bug Issue describes unintended or broken behavior Confirmed Issue has been verified as being caused by Tinkers, or an enhancement is planned to be added Resolved Issue is fixed in code, but there is not a release with that fix yet.

Comments

@snackerpirater
Copy link

Minecraft Version

1.19.2

Forge Version

43.3.9

Mantle Version

1.10.23

Tinkers' Construct Version

3.8.0.14

Describe your issue

Longbows will always fire arrows at their maximum velocity (as if fully drawn) regardless of draw time. This includes merely clicking the bow. The bow appears to draw at a normal speed (based on its animation), but the arrow always fires at the same velocity. Tested with multiple longbows to confirm that the fired arrow's velocity depends on the maximum velocity of the bow itself.

Crash Report

No response

Other mods

None, confirmed with solely Tinkers' and Mantle

Tried reproducing with just Tinkers?

Yes

Performance Enchancers

None of the above

Searched for known issues?

Searched open issues

@snackerpirater snackerpirater added 1.19 Issue affects 1.19 Bug Issue describes unintended or broken behavior Unreviewed Issue is new and is awaiting the team to review it labels Apr 3, 2024
@KnightMiner KnightMiner added Resolved Issue is fixed in code, but there is not a release with that fix yet. Confirmed Issue has been verified as being caused by Tinkers, or an enhancement is planned to be added and removed Unreviewed Issue is new and is awaiting the team to review it labels Apr 8, 2024
@KnightMiner
Copy link
Member

Fixed in v3.8.1.16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.19 Issue affects 1.19 Bug Issue describes unintended or broken behavior Confirmed Issue has been verified as being caused by Tinkers, or an enhancement is planned to be added Resolved Issue is fixed in code, but there is not a release with that fix yet.
Projects
None yet
Development

No branches or pull requests

2 participants