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

Unstacked mobs having unusual death behaviour #561

Open
Maroon28 opened this issue Jul 26, 2022 · 1 comment
Open

Unstacked mobs having unusual death behaviour #561

Maroon28 opened this issue Jul 26, 2022 · 1 comment
Assignees
Labels
💡 No known solution There's currently no known solution for the bug/feature.

Comments

@Maroon28
Copy link

Minecraft's Version

1.18.2 Purpur

Plugin's Version

3.8.0.322, Dev build from here https://hub.bg-software.com/job/WildStacker/322/

Describe the bug

When killing a mob which isn't stacked, they have unusual death compared to regular mobs. For example, if you shoot a mob to death with arrows, the last arrow bounces off the mob and hits the floor. Killing a mob with a sword also doesn't play the 'crit' sound if you deliver a final blow. I'm guessing the plugin is setting the mob's health to 0 regardless of if they're stacked or not, which is what's messing with the arrows and sounds/animations.

To Reproduce

  1. Get an unstacked mob
  2. Shoot the mob to death. Or kill it with a sword
  3. The last arrow is bounced off of the mob instead of disappearing. If you kill it with melee the mob just dies unnaturally without any crit noises.

Additional Information

No response

@Maroon28 Maroon28 added the Pending Pending reports to be investigated label Jul 26, 2022
@OmerBenGera
Copy link
Member

All of this is because WS tries to handle death by itself so it can prevent the death if needed.

There is no solution for that.

@OmerBenGera OmerBenGera added 💡 No known solution There's currently no known solution for the bug/feature. and removed Pending Pending reports to be investigated labels Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 No known solution There's currently no known solution for the bug/feature.
Projects
None yet
Development

No branches or pull requests

2 participants