I was making a blaze farm, and when one or several blazes got stuck between a sticky piston and a solid block, the server crashed ("Disconnected from server" it says). After that I am unable to connect to the server for about 1-2 min. When I am able to log in, same thing happens. I can't perform any actions for the few seconds I am logged in. My friends who are not nearby my blaze farm, can play normally, but if I log in the whole server crashes. My friend tested to see if he got close to the farm it would crash, and it did.
Linked issues
Comments 14
Whelp really wish I would have looked up information like this before I built my blaze grinder. Just activated it (proud of myself as it was my first blaze grinder) and next thing I knew I had disconnected. Thinking it was nothing as this has happened to me before, I waited a couple of minutes before trying to get back on and after getting back on I couldn't interact with anything. Then 20-30 seconds later I get kicked again.
So this is pretty cool. Can no longer play on that Realm until this issue has been fixed. As I can't get away from the spawner when I log back in.
Edit: Wanted to state that I play on the Bedrock Edition on both Windows 10 and Xbox One. It crashes on each platform.
If you are a owner of the realm and people cant get on because of this or you know the owner tell them to put the realm in peaceful let the person join then change it back to the desired difficulty. I have the same issue on my realm and this is the only way that i have found to fix it for now. The number of mobs is not the cause it it your crushers and the piston funnel that are the cause. Dont use the crushers and if a blaze gets stuck in the funnel hope that its not going to crash! Mojang Please patch this!
Been watching this since December to no avail 😞 Here's a new farm design that seems to work.
Do you have a blueprint (or description) of the blaze farm that crashes the server, if it's a special kind of farm.
I used the farm which can be shown in this video
https://m.youtube.com/watch?t=1043s&v=5Wx766O4tKQ
I'm having the same issue.