Affects Version/s: Minecraft 1.13.2
Fix Version/s: None
Environment:Windows 10 and latest Java Version.
Put the summary of the bug you're having here
What I expected to happen was...:
When I used the commands /setblock, /clone, or /fill to remove a mob spawner, I expected there to be no traces that the spawner had ever exsisted.
What actually happened was...:
However, the particles generated by the spawner stayed behind and didn't go away until relog.
Steps to Reproduce:
1. Place an active mob spawner
2. Remove it using /setblock, /clone, or /fill
3. Witness what I'm talking about here