Bishwoty

Still an issue in 1.14.4

It is possible that the colors for dark prismarine and prismarine are switched. Prismarine shows up dark on maps despite its color being very close to prismarine bricks.

This isn't fixed, as Fabian said the portals now turn you 180° (enter portal facing east, and you'll come out the other side facing west)

Confirmed, shipwrecks, ocean ruins, and buried treasure all trigger at approx y=90ish

Strange thing about the igloo I discovered, it could only grant me the advancement if I was way above the igloo (approx 30 blocks at y=91), but not inside. Perhaps the triggers are still working, but their position is not aligned with the actual structure?

Can confirm this also affects igloos, but I couldn't get it to fail on end cities or woodland mansions. Also confirmed for 1.13

Confirmed for 1.13-pre10

Did a little extra testing, and found that this bug appears to only affect structures that were detected by feature: temple. I also discovered that the game now recognizes these structures as "desert_pyramid" and "jungle_pyramid", and using these names instead doesn't crash the game. The actual trigger for this crash is any miss-spelled or non existent structure name crashes the game. This bug is not actually as serious as I thought, as it only happens on incorrectly made advancement files. This is still a bug though, as what should happen is the game gives an error in the game output log and not load the advancement, like it does with any other mistake. Below I've attached an example criteria that will trigger this bug.

"criteria": {
    "find_structure": {
        "trigger": "minecraft:location",
        "conditions": {
            "feature": "incorrect_structure_name"
        }
    }
}

Confirmed for 1.13-pre8 for shipwreck, ocean ruins, and buried tresure.

Can confirm, I just got this crash as well.

Confirmed for 1.13-pre8. I am concerned this bug won't be fixed before the release of 1.13. Is there any way to bring the devs attention to this bug? I would consider it a pretty serious bug as it causes a complete game crash.

Still an issue in 1.13-pre7

confirmed for 1.13-pre6 and 1.13-pre7

Just found this is probably a duplicate MC-125051, which is marked as resolved, which is why I didn't find it before I made this report.

This still happens in Minecraft 1.13-pre6. This probably is caused by advancements triggered by some/all structures (only tested for desert temples).

Oh I see the description is broken for @e and @s and confused me, sorry!

I would like to add that this seems to mainly affect advancements triggered by going into structures. If you are near a desert temple with an advancement that is granted by going in it, game crashes. My bug report, MC-127741. Hope this helps narrowing down the issue.

Note: The above screenshot is of the CodeCrafted pack with the custom model removed.

I am still able to reproduce the bug in 1.12.2, z-fighting still occurs. The CodeCrafted pack has found a workaround, they made a custom model for the redstone dot. The original issue still persists though, in that without a custom model, the redstone dot, and lines are still z-fighting.