mojira.dev

Don Nichols

Assigned

No issues.

Reported

MC-266488 Snapshot Not Loading Skins Cannot Reproduce MCPE-76996 Redstone Honeycomb Farms Inconsistent Duplicate MC-181620 Unable To Reel In Fish Duplicate MCPE-63301 Add-Ons Outputting Multiple Items Delete Extra Items Incomplete MCPE-62623 Repeater Timings Broken Incomplete MCPE-61214 Add-Ons Not Working Incomplete MCPE-61089 Can't Swim In Shallow Water Duplicate REALMS-2586 Rain Passes Through Blocks in 3rd Person Duplicate MCPE-55807 Can't Add Multiple Target Selector Tags Cannot Reproduce MCPE-55799 Structure Block Doesn't Remember Bounding Box Settings Duplicate MCPE-54725 Particle Command Doesn't Work Duplicate MCPE-53335 Custom Skin Packs Not Appearing Duplicate MCPE-52367 Transparent Texture on Leather Boot Bottom Turns Black Incomplete MCPE-50352 Selector Argument in /tellraw Doesn't Work Invalid MCPE-49174 Banner Preview Appears Black In Loom Using Faithful Invalid MCPE-49012 Player.json Files Override Each Other Cannot Reproduce MCPE-47750 Hoppers Don't Fill Past First Slot Duplicate MCPE-47512 Unable to Join Friends World Duplicate MCPE-47120 Mending Doesn't Always Get XP Duplicate WEB-1305 Bug Site Search Bar Not Useful Invalid

Comments

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...

I'd like to confirm that the particle command does in fact work. What's listed online doesn't work, so don't rely on that. Mega_Spud stated in a previous comment that you'll need to download the default resource and look in the Particles folder, and they are right. In that folder are a bunch of json files. You'll need to open them as text files. In one of the top lines will be something like "minecraft:particle", for example, "minecraft:arrow_spell_emitter". This is what's needed to run the command

Still seems to happen in 1.13

I'm having a fairly similar issue. It only seems to remember custom skins for me. Any custom character or skin pack skin always gets reset

On top of that, all 5 skin slots are reset as well. The 2 on the far ends always delete themselves, and the remaining 3 always reset to either Steve or Alex at random, with at least 1 of each every time

Also worth noting, the skin bug from 1.12 actually remembered your skin on occasion, maybe a 60% chance to reset, if I had to estimate. In 1.13, however, any skin pack skin or custom character, for me at least, has been reset 100% of the time. So if anything, this bug was worsened, not fixed

Can confirm as of official 1.13 release

How has this not been fixed yet? Map makers could definitely make great use of this. Please move this up in priority

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.