The bug
Since 18w50a, an unnamed villager called 'entity.minecraft.villager.none' will randomly be spawned using the /summon command or spawn eggs.
How to reproduce
Place a command block with the following command
/summon villager ~ ~0.5 ~Place a button on the side of the block
Keep pressing the button until the command output mentions the internal name path
Analysis
This villager is separate from the existing and named "Nitwit", and is not the new named, GUI-less "Mason" either, as can be observed from the command output in the screenshot.
It can be summoned directly using:
summon villager ~ ~0.5 ~ {VillagerData: {profession: "minecraft:none", level: 1}}Linked issues
is duplicated by 17
relates to 2
Attachments
Comments 11
This villager can also be summoned using:
/summon villager ~ ~ ~ {VillagerData:{profession:"minecraft:none",level:*doesn't matter which level*,type:"minecraft:none"}}Relates to MC-140961, as it is another case where villagers have a chance to have a profession of "none".
Might be related to MC-140868, as {{}}this villager is certainly "unemployed", and "minecraft:village/plains/villagers/unemployed.nbt" might refer to it.
With 18w50a, babies villagers have no profession (minecraft:none) as their profession after they grew up.
From above comments and other discussions I understand this type of villager is intended to exist, so I modified the description. It still is a bug that this type can randomly be summoned, so I refocused the description on that.
Unable to test in 19w11a, as ALL villagers spawned are now without profesion. Both from spawn egg as well as from commands.
@Jack_McKalling It is intended, as villagers need a working stations for them to receive a profession.
This issue should be resolved as WAI.
I can reproduce