Matt Sturgeon

Has anyone actually reproduced this bug in a Fortress generated in 20w21a? I suspect this bug is actually fixed but testers are experiencing MC-184740 because they used worlds generated before 20w21a.

changin this would be hard, cos of they way they fixed MC-173115.

That change could be re-worked. Perhaps, rather than having a list of blocks mobs can't spawn in, you could have a whitelist and/or blacklist of mobs that can spawn within a given block.

Admittedly not as neat as a single list, but perhaps more flexible.

Another option would be to have the list contain either a blockid string, or an object containing more detailed information, for example:

[
   "minecraft:rails",
    {
        "block": "minecraft:wither_rose",
        "exceptions": [
            "minecraft:wither_skelleton"
        ]
    }
]

This has the advantage of a single simple list for most cases, with optional flexibility when needed. The same system could be also adopted for the existing "cannot spawn on top of" system for magma blocks.

> which will help with iron farms now 😃

Well in that case this bug will likely be fixed within the next few hours 😂

Yes MC-11944 was about using buckets to remove portal, end_portal and end_gateway blocks (either by clicking on an adjacent block or by using a dispenser).

Don't know why it can't be accessed now, it was public when I posted the above comment.

I assumed this was WAI, since enchanted bows can be used to craft dispensers.

It was previously suggested in MC-117563 that the dispenser recipe should click in but not move named or enchanted bows, as it is more problematic to accidentally destroy a nice bow than to accidentally craft a dropper.

To me, showing the dispenser recipe as "unavailable" when you still can craft a dispenser (using named/enchanted bow) is misleading.

Worked fine here on Linux (nvidia, proprietary drivers)

@SunCat after some further investigation, reported as MC-117758

Why is this WAI? Other coloured blocks are in the recipe book. Other non-stackable items are in the recipe book. Whats the issue with adding Shulker Boxes?

In 1.12-pre5 this is NOT fixed for case 1, where all materials are in the crafting grid and none are in the inventory.

When all materials are in the crafting grid, the recipe shows as unavailable, clicking on the recipe empties the crafting grid and shows a "template" (greyed out/transparent) recipe instead. At this point the recipe becomes available and acts normally, since all materials were moved into the inventory.

You should be using a text editor (like Notepad) not a word processor (like MS Word) to edit the function file.

Using a program like Word will add hidden formatting to the file that is not understood by Minecraft. A text editor like Notepad edits the raw file data, which is what you need to do for minecraft functions (and most programming).

Also, since 1.12-pre4, commands within functions must omit the /, so your function file should look like this:

# I like diamonds!
give @s minecraft:diamond

Not:

# I like diamonds!
/give @s minecraft:diamond

Finally, this is a bug tracker for reporting issues in the game, not asking for help or technical support.

@Marcono1234: in his screenshots he has made the file under the data/functions folder, it looks like he just mistyped it in his bug report

Related to MC-117563 and MC-116905

Is there a work around using /advancemt? Something like

/advancement revoke @s only minecraft:recipes/*

or

/advancement revoke @s under minecraft:recipes

Or maybe, since /recipe grants recipe advancements when giving recipes, it should also revoke them when taking recipes?

The file will be located in your ".minecraft" folder, under "crash-reports". It will have a similar filename to the screenshots.

To attach it, use the same method as attaching screenshots (drag the file onto the bug report's "attachments" section)

Can someone explain why this is WAI? To me it clearly sounds like a bug, not a design choice.

Surely revoking a recipe should have the same result as having never earned the recipe?

Duplicate of MC-117628

I haven't been able to reproduce this yet on 1.12-pre4

Looks like a duplicate of MC-117628

Duplicate of MC-117628

I would agree this is probably WAI - doMobSpawning affects natural spawning - not manual spawning such as /summon and spawn eggs.

To me, throwing an egg is manual spawning, since you have to use the egg to spawn the chicken.

I am able to reproduce on 1.12-pre4.

Particles appear but no cracks.