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

[Bug Report]: Overcharge keeps the charged damage when use another bow. #278

Open
rtxyd opened this issue May 15, 2024 · 5 comments
Open
Assignees
Labels
Maybe a bug? Maybe not? Good for newcomers

Comments

@rtxyd
Copy link

rtxyd commented May 15, 2024

Describe the bug; What happened?

Use a vanilla bow with overcharge enchantment, overcharge and shoot the arrow record the damage. Then switch to another vanilla bow without enchantment shoot the arrow. See the damage. (I use dummmmmmy mod to test, with overcharge III enchantment)
Shoot that bow which has the enchantment, without charge (immediately release the bow) will reset the damage.

Expected Behavior

Damage multiplier should not stay when you change bow.

Mod Version

MC Dungeons Weapons 9.0.4

Minecraft Launcher

Other

Operating System

Windows

Modpack

No response

Additional context

modlist:
dummmmmmy-1.20-1.8.17b-fabric
mcdw-9.0.4

@rtxyd rtxyd added the Maybe a bug? Maybe not? Good for newcomers label May 15, 2024
@chronosacaria
Copy link
Owner

@rtxyd This sounds like a very niche situation. Is there any chance that you could upload a video of what you're doing? It sounds like, since the overcharge status effects is still applied to the player that it is carrying over to any bow, but, a video would help to confirm this

@rtxyd
Copy link
Author

rtxyd commented May 15, 2024

wait a minute

@rtxyd
Copy link
Author

rtxyd commented May 15, 2024

20240515150339.mp4_20240515_153951.webm

@rtxyd
Copy link
Author

rtxyd commented May 15, 2024

@chronosacaria video uploaded again, have a look

@chronosacaria
Copy link
Owner

@rtxyd I'm so sorry for my delayed response. I've been insanely busy. This is definitely wild and absolutely a bug on our end. Thank you, so much, for catching that and for providing the video. It helps a lot in figuring out what we need to do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maybe a bug? Maybe not? Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants