Consumetheoats
- anabolic_veemo
- anabolic_veemo
- Europe/Stockholm
- Yes
- No
MCPE-52703
MC-253165For the past week the game has been crashing (A software error has occured) primarily when I try playing on a world or a server barely managing to get past the loading screen. The game also crashes when I sometimes go into the options, skin options or even during the Mojang loading screen. Basically wherever.
I have checked for corrupted data and I've even redownloaded the game twice. But effectively this has made it impossible for me to play at this point. So I'm at a loss about what to do about this.
More frequently than now my sugarcane farm, inspired by silentwhisperer, has come across a bug in the piston clock that moves the left side of the waterlogged stairs back and forth. So far it has only been the left side (from the lever side) but basically it creates a "reverse ghost block" that can act as air preventing any interaction. I cannot mine it and trying to will only remove the block directly after it. The piston will not push the block whatsoever either despite being within push limit.
The only way I've managed to fix it is by moving the opposite piston one block forward to push the whole row forward another block and thus bringing back the staircase. Initially I thought this was due to having the redstone repeater in the redstone clock powering the farm on 1 tick but I also tried it on 2 ticks and it soon broke. I'm not sure if it's a big with the repeaters and delays or not. I also rechecked the block limit and it's within the 12 block push limit.
This was never an issue in the previous 1.14.30 version as no matter how much I'd have the farm running, on 1 or 2 ticks, it never broke. My version updated yesterday and this was the only instance this had happened.
In terms of how to recreate, as mentioned before, the sugarcane farm by silentwhisperer is probably the best way to recreate this, or at least the piston clock mechanism itself. The farm I made is long enough for 20 blocks of sugarcane as opposed to silent's 22, which shouldn't effect it as I've also had this work with 10 blocks of sugarcane. I've uploaded short clips in 4 parts.
I've tested this multiple times with all variations, such as the source_entity, is_projectile and is_explosion conditions (which work fine on their own), and it seems as though fireballs don't trigger this when the victim entity is a Blaze. I've tested the fireball trigger with other mobs and it seems to work completely fine. This code also works fine in version 1.18.2.
{ "criteria": { "requirement": { "trigger": "minecraft:player_hurt_entity", "conditions": { "damage": { "type": { "direct_entity": { "type": "minecraft:fireball" } } }, "entity": { "type": "minecraft:blaze" } } } } }
This is the closest I'll find to the exact same problem I'm having. I literally can't even load up a world or do anything without it crashing.
Oh thank goodness it's not just me. That's literally the same thing that's happening to me. Could you try th milk bucket too? Because that's also buggy for me as well. I uploaded both videos.
Can confirm the same is happening for me. /debug stop doesn't return anything besides stopping the tick profiling. /debug function works perfectly fine however.