muzikbike
Assigned
Reported
View all
MC-312731
Mapping and shading on Programmer Art repeater/comparator models is corrupted
Unconfirmed
MC-312730
Mapping and shading on Programmer Art repeater/comparator models is corrupted
Unconfirmed
MCPE-243657
End gateways are completely invisible when held by endermen
Unconfirmed
MC-312598
You can create a black/untextured shield using only commands
Works As Intended
MC-312596
You can give yourself a missing texture banner with commands with no resource packs
Confirmed
MCPE-243614
Heads held by endermen are invisible
Community Consensus
MCPE-243613
Copper golem statues held by endermen are invisible
Community Consensus
MCPE-243612
Shulker boxes held by endermen are completely invisible
Community Consensus
MCPE-243611
Chests held by endermen are completely invisible
Community Consensus
MCPE-243593
End portals held by endermen are completely invisible
Unconfirmed
Comments
Can confirm.
In 26.4 snapshot 4 changes were made to ice, frosted ice and the newly implemented brittle ice such that they would cull the other blocks if adjacent to each other. This is fundamentally the same issue as what this ticket describes, with the only difference being the blocks involved (as well as the missing cullface arguments on the beacon model).
With that mentioned, I think it’s probably worth reevaluating the Won’t Fix resolution of this ticket and that of MC-266071, since it’s been five years and a lot of things can change in that amount of time.
26.4 snapshot 4 makes a change to ice blocks that permits them (ice, frosted ice, brittle ice) to cull each other despite being different block IDs, such that these internal planes are eliminated. Despite this, copper grates, which suffer from the exact same issue, still show these internal faces:
With this specific change in mind, I think this ticket’s Won’t Fix resolution is worthy of re-evaluation.
How did paintings fix this then? They used to be affected by a similar issue, but no longer are.
It would depend on what data pack is active on the server, would it not? This is why invalid painting variants, wolf variants, and so on can’t be created with commands.
Can indeed confirm this to be fixed:
Screenshots since they didn’t want to attach at time of reporting:
269884 should have been MC-269984. I have no idea why this new site refuses to allow the editing of comments to amend issues like these.
Since this was closed, the very similar issues MC-94413, MC-182820, MC-200484, MC-217628 and MC-217629 were all fixed, and the ticket MC-269884 reopened. The newly-made tickets MC-312372 and MC-312373 were also triaged as Important the day after they were made. There is also the historical precedent set by the fixings of MC-5991 and MC-33384.
With the above information in mind, is it at all possible for this ticket’s Won’t Fix resolution to be reviewed, and this ticket reopened?
This issue still affects 26.52, and is also still not a duplicate:
…and, from what I can see, also leash knots.
The handle that corresponds to the plane of symmetry clearly should be the “middle”, should it not?
I believe this also affects cushions.
“Fixed” in 26.3 snapshot 3, since “shade” no longer exists. The ticket MC-312498 details the current behaviour.
Can someone explain how this counts as a feature request? End portals can be placed just fine, despite not being obtainable as an item. I’d fully expect end gateways to work in the exact same way. In JE, both can be placed.
This ticket should be reopened if there is no good explanation as to why this distinction exists.
Are these tickets still relevant following OIT’s implementation, or not?
No idea why this submitted twice despite me just pressing the Next Image button.