Villagers spawn without a profession
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 by18
Created Issue:
Summoning villager randomly spawns 'entity.minecraft.villager.none'
The new villagers added in 18w50a include an unnamed villager called 'entity.minecraft.villager.none'. This villager is separate from the existing and named "Nitwit", and is not the new named, GUI-less "Mason" either.
How to reproduce:
- Place a command block with button on top, and insert command:
summon minecraft:villager ~ ~.5 ~
- Keep pressing the button until chat outputs:
[@: Summoned new entity.minecraft.villager.none]
The new villagers added in 18w50a include an unnamed villager called 'entity.minecraft.villager.none'. This villager is separate from the existing and named "Nitwit", and is not the new named, GUI-less "Mason" either.
How to reproduce:
- Place a command block with button on t
op, and insert command:summon minecraft:villager ~ ~.5 ~
- Keep pressing the button until chat outputs:
[@: Summoned new entity.minecraft.villager.none]The new villagers added in 18w50a include an unnamed villager called 'entity.minecraft.villager.none'. This villager is separate from the existing and named "Nitwit", and is not the new named, GUI-less "Mason" either.
How to reproduce:
- Place a command block with button on the side, and insert command:
summon minecraft:villager ~ ~.5 ~
- Keep pressing the button until chat outputs:
[@: Summoned new entity.minecraft.villager.none]
The new villagers added in 18w50a include an unnamed villager called 'entity.minecraft.villager.none'. This villager is separate from the existing and named "Nitwit", and is not the new named, GUI-less "Mason" either.
How to reproduce:
- Place a command block with button on the side, and insert command:
summonminecraft:villager ~ ~.5 ~
- Keep pressing the button until chat outputs:
[@: Summoned new entity.minecraft.villager.none]The new villagers added in 18w50a include an unnamed villager called 'entity.minecraft.villager.none'. This villager is separate from the existing and named "Nitwit", and is not the new named, GUI-less "Mason" either.
How to reproduce:
- Place a command block with button on the side, and insert command:
summon villager ~ ~0.5 ~ {VillagerData: {profession: "minecraft:none", level: 1}}
- Press the button
The new villagers added in 18w50a include an unnamed villager called 'entity.minecraft.villager.none'. This villager is separate from the existing and named "Nitwit", and is not the new named, GUI-less "Mason" either.
How to reproduce:
- Place a command block with button on the side, and insert command:
summon villager ~ ~0.5 ~ {VillagerData: {profession: "minecraft:none", level: 1}}
- Press the button
The bug
Since 18w50a an unnamed villager called 'entity.minecraft.villager.none' will randomly be summoned when using:
summon villager ~ ~0.5 ~How to reproduce
- Place a command block with the above command
- 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}}
is duplicated by
I got one by breeding two villagers yesterday (like the duplicated issue).
is duplicated by
relates to
Summoning villager randomly spawns 'entity.minecraft.villager.none'Spawning villager randomly spawns 'entity.minecraft.villager.none'
The bug
Since 18w50a an unnamed villager called 'entity.minecraft.villager.none' will randomly be summoned when using a spawn egg or the following command:
summon villager ~ ~0.5 ~How to reproduce
- Place a command block with the above command
- 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}}
The bug
Since 18w50a an unnamed villager called 'entity.minecraft.villager.none' will randomly be s
ummoned when using a spawn egg or the following command:summon villager ~ ~0.5 ~How to reproduce
- Place a command block with the above command
- 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}}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}}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
Spawning villager randomly spawns 'entity.minecraft.villager.none'Villagers spawn without a profession
is duplicated by
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-140938, as it is another case where villagers have a chance to have a profession of "none".
Those aren't green-robed villagers. Those are villagers with their profession defined as minecraft:none.
Baby villagers growing up with no profession probably isn't intended. Additionally, they don't have a name defined (similarly to MC-140938), further proving that they aren't intended to have no profession.
This bug probably occurs because the baby villagers are trying to randomize the Profession tag, which no longer exists in favor of the VillagerData tag
Thank you for your report!
However, this issue has been closed as a Duplicate of MC-140961 and MC-140938.
It has been linked to this report. If you have additional information, please add it to the duplicated report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
This villager profession is supposed to exist for baby villagers (so they don't have a profession), but the translation string for this profession is missing, as such, making a command say baby villager names, makes them show up as entity.minecraft.villager.none, rather than "Unemployed Villager" or similar.
This is not MC-140938, as that's about them appearing randomly when using /summon, and spawn eggs, this is purely about the name.
Steps to reproduce:
- Grab a villager spawn egg
- Spawn a villager
- Use the spawn egg on the villager (to make a baby villager)
- Run /execute as @e[type=villager] run say @s
- Observe [entity.minecraft.villager.none] entity.minecraft.villager.none
Thank you for your report!
However, this issue is a Duplicate of MC-140938.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
However, this issue is a Duplicate of MC-140938.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
However, this issue is a Duplicate of MC-140938.
If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Duplicate of MC-140938. This is now intended since villagers could select their profession based on certain utility blocks in 19w11a.
Intended. From MC-140938:
All villagers spawn without a profession, then they pick profession based on available job site blocks.
Cannot reproduce that villagers will only spawn "plain" under all conditions. They spawn the correct biome respective skin when using spawn egg.
Also duplicate of MC-140938
As of 1.14, villagers are supposed to spawn without a profession (or rather, their profession is "unemployed") and they will switch to a profession once they find a workplace. See MC-140938:
All villagers spawn without a profession, then they pick profession based on available job site blocks.
– [Mojang] Agnes Larsson
From MC-140938:
All villagers spawn without a profession, then they pick profession based on available job site blocks.
From MC-140938:
All villagers spawn without a profession, then they pick profession based on available job site blocks.
Duplicate of MC-140938. If you want villagers with a profession, place down a "workstation" block nearby.
Possibly intentional. Villagers will pick their profession based off of available job sites (MC-140938).
Thank you for your report!
We're tracking this issue as MC-140938, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as working as intended, which means this is not considered a bug and won't be fixed. Please do not leave a comment on the linked ticket.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues in Discord or Reddit


I can reproduce
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.
Also occurs with spawn eggs.
Present in 19w08a with either spawn eggs or commands.
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.
Understood.
I request to close this ticket as "Works As Intended" due to changed mechanics.
All villagers spawn without a profession, then they pick profession based on available job site blocks.