[MC-137463] Infinite flame particles for naturally and command generated monster spawner

The bug

Naturally generated mob spawners will not stop displaying particles upon being broken.

How to reproduce

Create a new world with the following or give yourself a spawner, and place it.

Seed: -2508081674438795683
Coordinates: /tp @s 321.30 22.00 3.03 -124.99 17.67

Break the spawner.
→ ❌ Upon being broken, particles stay generating.

Linked issues

is duplicated by 27

MC-137489 Particles Resolved

MC-137663 Mob Spawner Particles Multiplied Resolved

MC-137677 Spawner particles do not always disappear when destroying Pillager or Illager Beast spawners. Resolved

MC-137720 Mob Spawner Particle Error Resolved

MC-137732 Spawner particles double when unloaded Resolved

22 more links

relates to 1

MC-141215 Silverfish spawner destroyed but silverfish still spawn (server only) Resolved

Attachments

Comments 20

Earl W Foote 2018-10-25T20:30:39Z

I can confirm that I too have had this happen in 18w43b.

tryashtar 2018-12-17T20:29:07Z

Reopening because this has been reported by others after 18w44a – MC-140182, MC-141202, MC-141215

Jason C Rogers 2018-12-17T20:56:42Z

I broke one spawner and the flames disappeared, but the spawner still activated periodically. When it activated, the flames briefly appeared.

[Mod]Les3awe 2018-12-18T10:32:28Z

I cannot reproduce.
In what version was the world created?

Jason C Rogers 2018-12-18T11:50:06Z

World created in 18w50a server.

Seed: 1458142510

Two locations I have tested:

-5784 29 -5212 Endermite spawner in portal room.

-2082 39 -4682 Endermite spawner in portal room.

Spawner destroyed, but continues to spawn endermites. Flames show up when spawning mites even though spawner block is gone.

My screenshot is on MC-141215

10 more comments

[Mod]Les3awe 2018-12-18T13:09:54Z

Only affect the world created in the server?
Or also affect the singleplayer?

Jason C Rogers 2018-12-18T13:22:54Z

I just created single player world with above seed.

-5784 29 -5212 endermite spawner did NOT create in portal room.

-2082 39 -4682 I destroyed endermite spawner. It apppears to not continue to spawn. (correctly)

This may be a server issue?

[Mod]Les3awe 2018-12-18T14:54:02Z

Reopened MC-141215.
Please update the description in MC-141215.

tryashtar 2018-12-24T00:05:07Z

Silverfish are not the only affected spawner:

MC-141417 – cave spider
MC-141202 – cave spider
MC-140182
MC-138848 – regular dungeon

It's clear that the issue can no longer be reproduced everytime, but it is not fixed, nor is it server-only. MC-141215 can probably be kept open separately if it really is only for servers.

tryashtar 2018-12-24T07:41:25Z

@unknown, respectfully, it doesn't matter if you can't reproduce it. The fact is that plenty of people can, so it should stay open.

Brad 2018-12-24T20:34:35Z

These particles are also produced indefinitely when you break a spawner.

Keny Mylankca 2018-12-25T09:45:06Z

Hey ah, this bug is still reproducable at sometimes. Please look into it once again! Thanks.

Enderman 2018-12-25T15:39:05Z

Can someone add 18w48a, 18w48b and 18w49a from the affect versions list please. I understood what can still reproduce this bug waiting 10 seconds before destroying the spawner and when you destroy the spawner the flame particles are still show. Please upgrade the ticket. And not confirmed for command generated monster spawner.

Sulnus 2019-01-13T12:43:02Z

I found something that may be related. If you /fill a area with air, and a spawner is located in the area filled, the flame particels will still be there after the spawner is gone. I have no prof of this happening every time, but the one time it happend, the flames would not go away, until I updated the blocks near it. I updatet it with flodding it with water, and today I never see the particels

Oval 2019-01-19T00:56:36Z

@unknown, that is MC-46094.

TheBoy358 2019-02-07T15:57:15Z

Confirmed in 19w06a I am too naive

TheBoy358 2019-02-13T20:46:19Z

Confirmed in 19w07a.

TheBoy358 2019-02-22T13:52:31Z

Seem to be fixed in 19w08b.

Adrian Östergård 2019-03-19T13:02:56Z

Is this still an issue in 19w11b?

TheBoy358 2019-03-19T16:34:48Z

I was unable to reproduce this bug since 19w08a.