1.13.1 issue with spawners

Question

1.13.1 issue with spawners

Sikatsu opened this issue 6 years ago · 9 comments

Sikatsu commented 6 years ago

What steps will reproduce the problem?

Mine a zombie pig spawner will give a normal pig spawner back

Expected output

It should give a zombie pig spawner instead.

What do you see instead?

A pig spawner is given

/version output?

This server is running CraftBukkit version git-Spigot-2440e18-6304ccd (MC: 1.13.1) (Implementing API version 1.13.1-R0.1-SNAPSHOT)

SilkSpawners version

6.0.0-Snapshot

Checklist

I am aware that issues caused by /reload are ignored
If there is a (potential) plugin conflict, I've identified the conflicting plugin
I have added a valid /version output
I have added a valid SilkSpawners version
I have attached necessary information like a screenshot, my list of plugins, config or permissions file(s)

timbru31 · Answer 1 · 2018-08-30T20:05:03.000Z

Where did you obtain the spawner from? If mined naturally, is your world a freshly generated or have you upgraded (if yes from which version?)

…

On 30. Aug 2018, at 9:55 PM, Sikatsu ***@***.***> wrote: What steps will reproduce the problem? Mine a zombie pig spawner will give a normal pig spawner back Expected output It should give a zombie pig spawner instead. What do you see instead? A pig spawner is given /version output? This server is running CraftBukkit version git-Spigot-2440e18-6304ccd (MC: 1.13.1) (Implementing API version 1.13.1-R0.1-SNAPSHOT) SilkSpawners version 6.0.0-Snapshot Checklist [x ] I am aware that issues caused by /reload are ignored [x ] If there is a (potential) plugin conflict, I've identified the conflicting plugin [x ] I have added a valid /version output [ x] I have added a valid SilkSpawners version [x ] I have attached necessary information like a screenshot, my list of plugins, config or permissions file(s) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

Sikatsu · Answer 2 · 2018-08-30T20:54:05.000Z

I added it as a vote reward. It runs an essentialsX command to give the spawner. So it gets placed and once it gets mined it'll become a pig spawner. Fresh 1.13 world.

timbru31 · Answer 3 · 2018-08-30T20:59:24.000Z

Please try /ss give instead. It might be esssentials that’s broken, too. I‘m going to take a look anyway

…

On 30. Aug 2018, at 10:54 PM, Sikatsu ***@***.***> wrote: I added it as a vote reward. It runs an essentialsX command to give the spawner. So it gets placed and once it gets mined it'll become a pig spawner. Fresh 1.13 world. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Sikatsu · Answer 4 · 2018-08-30T21:05:57.000Z

I used /ss give before, but changed it to an essentials command since i'm not sure till what point SilkSpawners supports 1.13+

Might indeed be essentials too, though.
Also, this might happen with more spawners but I only give out a pigman spawner.

Sikatsu · Answer 5 · 2018-09-02T07:27:32.000Z

Using /ss give has the same issue. Pigman spawners change into pig spawners.

Sikatsu · Answer 6 · 2018-09-05T14:15:13.000Z

I don't hear anyone about having issues with the LEGAL mob spawners when they mine and place them. Only the one from the vote chest which is an illegal one.

timbru31 · Answer 7 · 2018-09-05T13:54:17.000Z

@Sikatsu have you (or can you try) tried other mobs? Are those effected, too?

Sikatsu · Answer 8 · 2018-09-06T21:48:40.000Z

Found out this was an issue with essentials. It has been fixed using the experimental branch for 1.13.

Closing this issue.

timbru31 · Answer 9 · 2018-09-06T21:56:25.000Z

Awesome, thanks for letting me know.

…

Sent from my iPhone

On 6. Sep 2018, at 11:48 PM, Sikatsu ***@***.***> wrote: Found out this was an issue with essentials. It has been fixed using the experimental branch for 1.13. Closing this issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.