The blaze spawner in the nether is covered in flames, as in there are flame particles inside the block to the extent that you can no longer see the cage, or spinning blaze. This is creating massive FPS drops. (usual FPS is 180, however near the spawner it drops to 4...)
Tried breaking it and replacing with a new spawner, the issue is recreated.
See attached screenshot for reference.
edit: When breaking the spawner, flames persist (see 2018-07-05_21.53.45.png) until world has been restarted. Only then will the flames disappear...
edit: Added a picture of being inside the block of flames.
edit: Found the cause! There is a redstone contraption around the spawner that uses a clock, and every pulse of redstone more flames get added to the spawner. If the contraption is never turned on, the spawner behaves normal.
Attachments
Comments 6
When breaking the spawner, flames persist (see 2018-07-05_21.53.45.png) until world has been restarted. Only then will the flames disappear...
If you used "/fill" or "/clone" to break the spawner, then this is "MC-46094 - Using fill/clone which replaces mobspawner and keeps its fire particle".
If you used "/fill" or "/clone" to break the spawner, then this is "MC-46094 - Using fill/clone which replaces mobspawner and keeps its fire particle".
We were playing in survival when this happened, however removed it by breaking it in creative. Did not use any commands.
What redstone contraption is causing the spawner flames to generate?
Multiple pistons getting powered by a redstone clock to push the blazes into a funnel for a farm.
Is this still an issue in the most recent versions (currently that is 1.13.2, or the latest snapshot 18w48b) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
Same issue present (On the same server). Using included Java JRE 1.8.0_51 64bit on an i7-5820K and Radeon RX Vega 56,