-
Notifications
You must be signed in to change notification settings - Fork 24
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
Villager issue #782
Comments
Finally, I found how to reproduce the issue, would you be able to fix the issue ? :/ Thanks Ps : After every dispawn, the second error pops. |
I knew this issue for a long time. I had tried several ways to solve this problem but fail to do so. This issue only happened in 1.14/1.15 minecraft and it only affect llama & villager. |
This type of issue is indeed very hard to understand and fix, but, the only thing still weird for me is the entity loss. Maybe minecraft is designed like that, in this case that's not convenient for users at all :/ |
A solution by spigot or the game itself should be easier for you and users (if possible and caused by server). Even though the issue isn't really fixed, there would is no bad impact ^^ |
Actually it is a huge issue for spigot server as it will crash the server when this issue happened. PaperSpigot will not cause crashing instead of showing errors. Let me explain why this issue happen. |
Describe the bug
A clear and concise description of what the bug is.
Sometimes, using a villager pet, the error below pops "randomly" and causes other issues with real villagers (they disappear).
Thanks in advance for your help :)
To Reproduce
Steps to reproduce the behavior:
I don't really know how to reproduce this issue, I'll investigate. Maybe try to interact with them, try to use them with job blocks among other villagers...
Expected behavior
This errors shouldn't happen and cause issues.
Further Information (please complete the following information):
https://mcpaste.io/08608ec608c7c5e3
Occured once, then this occured several times :
https://mcpaste.io/feac24a57831d921
The text was updated successfully, but these errors were encountered: