Don Nichols

How has this not been addressed yet? We're now in 1.14, with 1.15 currently in beta. If Mojang has no intention on either fixing this or making it fully functional, then why did they re-implement the structure block in the first place? It makes no sense

I'm not exactly sure what the best way is to explain how to reproduce, but I can give a personal example. I built a roller coaster loop and a corkscrew as accurately as I could using minecart physics. They both require slime blocks to launch the carts, first vertically followed by horizontally. Previously, they worked flawlessly. Now, without even adjusting any repeaters, it's a complete gamble whether or not you'll get launched properly. It's possible it has to do with pistons rather than repeaters, but even still, the timings are still off without me doing anything

Issue has been fixed by the pack creator

Added a screenshot of the issue. Still unsure why this happens. And my manifest.json file is in the proper format, so idk what's wrong

Experiencing the same issue. Yet the cape button was available yesterday. Weird...

Still seems to happen in 1.13

Can confirm as of official 1.13 release

Apparently, this isn't fully true. If I just remove the bottom texture, for some reason, it reappears. It only seems to turn black if I remove other parts of the boot texture, neither of which makes any sense

Seems to have returned as of 1.12

If this is working as intended, please explain why it's necessary for leather boots to do this and no other armor type, as it makes no sense

The trapdoor thing is normal. They changed the creeper's hitbox to 1.8 blocks so it can spawn in that space to catch up with Java. Except they messed up and made the same change to all 2 block tall mobs. So, on one hand, yes, this is a bug. On the other hand, it's a result of adding an intended feature

Helpful to know, if I knew where in the edit section to change it

Except I'm using /clear to prevent duplicate items. Also, as I said, this method is to try and replicate Curse of Binding, since MCBE doesn't have it yet. Not only can you not remove it, it gets cleared from your inv (or cursor, if you're using a mouse/controller) when you try to do so.

Still an issue, not sure why this hasn't been looked at. Allowing the command to work up to 360 allows specific ry ranges to work. There's no way this is working as intended, as this is how it worked when it was first implemented. If it is, please change it back.

This happens to me when I'm the only one in the world, including when I'm the host.

Still seems to be an issue. Not even sure if Mojang is even working to fix it at this point.

I will go ahead and confirm that. It just took way too long, and I posted this well before I got one, and well into my fishing session. Apologies for my premature report.

Definitely occurs with 32x resource packs. Please fix this, Mojang, this is a big problem (no pun intended).

I added a picture of an auto sorting system that uses this mechanic. It isn't filtering the items like it's supposed to. The hoppers aren't pulling items down to sort like they're supposed to. If a hopper below is able to take an item, it's supposed to pull that item down before the top hopper pushes it, even if said hopper is powered. It's only supposed to lock from pushing, not pulling. At least, that's what I had assumed. Did this sorting system originally work due to a bug?

Instead of removing it due to being a bug, why not add it back in as a feature? It was useful. And it's not like it was really breaking anything. It's more like things ended up breaking due to it being removed.