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

Stone block as Head and Item #714

Closed
JosephStarke opened this issue Nov 12, 2019 · 5 comments
Closed

Stone block as Head and Item #714

JosephStarke opened this issue Nov 12, 2019 · 5 comments

Comments

@JosephStarke
Copy link

Describe the bug
I use mythic mobs to make custom mobs, and libs disguises and skinner to disguise them. Libs disguises and skinner both require protocol lib. In 1.13.2 I made mobs with custom skins and they worked perfectly fine, with no issues through this exact same way. recently I updated to 1.14.4 and now all the mobs with custom skins spawn with there skin correctly except they have a stone block and their head and item, which sometimes turns to normal after a while. I sent this error to the developer of libs disguises and he said it was a bug in protocol lib.

To Reproduce
Steps to reproduce the behavior:

  1. You need to download Mythic Mobs, libsdiguises, skinner, skinner lib, and protocol lib.
  2. Create a skin for a mob and upload it to https://mineskin.org/
  3. Plug the correct information into libs disguises custom skin folder and the skinner config, then apply the skin in Mythic Mobs on your created mob and spawn it in.
  4. Then your mob will have a stone head and item (even if not given an item), and will crash the server when it attacks a player.

Expected behavior
It should spawn normally without a stone head or item, and not crash the server when attacking the players.

Screenshots
Showcase

Desktop (please complete the following information):

Smartphone (please complete the following information):

  • Device: N/A
  • OS: N/A
  • Browser: N/A
  • Version: N/A

Additional context
(This a the bug that I got once):
https://pastebin.com/0SQdf9YZ

@MiniDigger
Copy link

if the author says this is a bug in protocollib, he should open a proper issue with easy and minimal reproduction steps (aka a couple lines of code)

this in itself isn't super helpful as you run 5 plugins that could interfere here, half of them are not even open source, so this is really not actionable.
please get the author to do a proper bug report.

@dmulloy2
Copy link
Owner

Can you run /protocol dump and paste the output with pastebin? That might narrow it down a little.

It would also be helpful if @libraryaddict could provide some more info here.

@JosephStarke
Copy link
Author

Here is the protocol dump: https://pastebin.com/eE0whbRr

@dmulloy2
Copy link
Owner

Yeah, I still don't really know what's going on there. It's probably some interaction between all 3 of those plugins which could be happening anywhere. We need a proper bug report from the libs disguises author

@libraryaddict
Copy link

Sorry for the lack of replies, I misread the bug report and likely isn't a PL bug.
The attribute thing is what I had been looking at, where the items is likely LD itself.

@dmulloy2 dmulloy2 closed this as completed Dec 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants