husky2490

Can confirm in 1.19

MCP's version is pointing to asset files that don't exist and exits w/o a stacktrace before the game even loads

Tell whoever is in charge of this site that this shows up as "Confirmation Status: None" on mobile but "Confirmation Status: Confirmed" on the desktop version.

I might volunteer for code analysis. The earliest I can start is Wednesday. If someone else wants to do it before then, be my guest.

This is going to be my last post for a while (I'm done with all of these stupid PE bugs). The in game file size in my previous comment might be caused by MCPE-23462, MCPE-25613, MCPE-7749, etc. Still no explanation for exported file size differences

This is starting to feel like a mega-report but I have no idea how to break it up. In a recent setup with sand, I created a copy of the testing world, made two sand pillars to near build limit in front of the machine and a hole to the void for the sand to fall into after being pushed and then saved. I created a copy of that and ran the test in the copy to compare file sizes afterwards and killed all entities before saving. In game it said there was an additional 1.2MB in the copy world and after exporting there was a 25kB difference between the two worlds with no difference between them other than running the machine to remove a sand pillar and removing all entities afterwards.

Confirmed in part for 1.2.13. Definitely behaves differently, note blocks don't crash the game anymore, and trickery is needed to reproduce. See v2 of testing world

Also increases your world size by 840 kB!

has anyone tested if this crashes servers too?

Did a user named "bug" get silently deleted or is there something wrong with my notifications? I was going to reply to them.

I don't know what I just did but I transmuted a piston into stone

All three basic behaviors confirmed for latest update

Edit: It seems even the crash caused by the note block is inconsistent as there is the only one of 5 crashes with a certain exception code and different crashes list different failing modules and only happens most of the time, when it feels like it.

Further Testing

Can break: (assume "no drop" unless stated otherwise)

• Bedrock

• Extended piston arms (piston base will turn into drop)

• Extended pistons

• Diamonds

• Trapdoors

• Doors (upper half: drop item, lower half: no drop)

• 2-tall flowers

• Beds

• Item frames w/ items

• Jukebox (drops music disk only, stops playing)

• Chest (pushes forward, then drops only its contents)

• Mob heads (drops as item)

• Monster eggs (no silverfish, I did change the difficulty)

• Dragon egg

• Torches

• Hoppers (drops contents only)

• Flower pots (drops flower only)

• Growing Netherwart

• Growing crops

• Signs

• Banners (lower half, ground mounted only)

• Pressure plates

• Slime blocks

• Rails

• Glass panes

• Ladders

• Shulker boxes

• Droppers (drops contents only)

• Redstone blocks

• Terracotta

• Glazed terracotta

• Note blocks

• Mob Spawners

• Stone walls

• Packed ice

Moves:

• Chests (piston does not break)

• Slime blocks with or without other blocks

• Redstone blocks

• Terracotta

• Glazed terracotta

• Note blocks?

• Stone walls

• Packed ice

Deals damage to:

• Shulkers

Only breaks piston:

• Observers

Crash the game:

• Note blocks (I give up trying to figure out what's going on)

• Pistons

Transmute:

• Pistons

⚠️ Revision to the book: Glitch usually occurs within the first few cycles, causes of variation are still unknown. Piston seems to prefer moving the block when piston and/or block is on the left.

I was making a dedicated world and found that adding signs changed its behavior, so an instructional book will have to do.

I didn't notice anything about the flying speed, but the glitch was active upon loading the world. Should I post this there?

Picture of the initial setup of the machine:

Stroke-by-stroke analysis:
Stroke 1 (back stroke): piston moves with the machine.
Stroke 2 (forward stroke): piston moves with the machine.
Stroke 3: piston moves with the machine.
Stroke 3.5: piston extends.
Stroke 4: piston retracts and arm clips into quartz block, unknown behavior upon clipping.
Stroke 5: piston retracts and deletes quartz block

The same machine in a slightly different configuration showing another bug (might be related)

Does this count? (I was sent here by a mod)

For those who can't load it. It's a crazy slime block contraption where a sticky piston facing perpendicular to the direction of movement and an observer powering it are moved side to side by two regular pistons powered by redstone blocks on top of the contraption. There are two quartz blocks lined up side by side so the sticky piston should always have something in front of it. I remove the redstone block that is stopping the machine. Here's what the piston does on each stroke of the machine.

Stroke 1 (back stroke): nothing.
Stroke 2 (forward stroke): piston extends and stays put.
Stroke 2.5: piston retracts.
Stroke 3: nothing.
Stroke 3.5: piston extends.
Stroke 4: piston remains extended and stays put, then begins to retract.
Stroke 4.5: piston continues retracting.
Stroke 5: nothing.
Stroke 5.5: piston extends.
Stroke 6: piston remains extended and stays put.
Stroke 6.5: piston retracts.
Stroke 7: nothing.
Stroke 7.5: piston extends.
Stroke 8: piston partially retracts, leaves first block in place, and moves with the machine, it's arm clipping into the second quartz block. It then extends again.
Stroke 8.5: the piston seems extended with it's arm completely inside the quartz block in front of it.
Stroke 9: both the piston and the quartz block move with the machine. The behavior of the piston head is unclear but it seems extended.
Stroke 9.5: the piston drops as an item.

Are you sure? That issue deals with pistons crashing the game. Is the moving of blocks sideways also included in that issue?

What do you mean?