Recommended Free Tools
An iron farm usually stops for one of two reasons. Either the village it relies on no longer meets its edition’s spawn conditions, or golems are spawning somewhere your collection system never reaches. Which problem you have depends on whether you play Java or Bedrock, so confirm your edition and game version before changing anything.
Start by confirming your edition and version
Java and Bedrock use different iron golem rules. A repair that fixes a Java farm can leave a Bedrock farm less reliable, and the reverse is also true. Before following any fix, write down:
- Edition: Java Edition or Bedrock Edition.
- Exact game version or build: for example, the number shown on the title screen or in your launcher.
- Platform: PC, console, or mobile for Bedrock; the launcher profile for Java.
- Hosting: single-player, a dedicated server, or a Realm. Server restarts and updates can change behavior on the host, not just on your client.
- Design source: the tutorial or blueprint you copied. Many farms were built for an older release, so check the design’s stated version against yours.
Community tutorials are useful, but they may lag behind current releases. Treat their numbers as a starting point and verify them in your version.
Check whether the golems are spawning somewhere else
A farm can look dead when it is actually working. Golems that spawn outside the kill area or collection platform are never delivered to your hopper or trap, so the farm appears to produce nothing. Check this first, because it takes a few minutes and rules out a whole category of problems.
#1 Best Overall
- Walk the area around the farm, including nearby roofs, open ground, and any caves or ravines within the spawn area of the village.
- Look for iron golems standing on blocks you did not expect, especially on the outer edge of the village.
- Compare the spawn area with where the golems stand. Bedrock spawning is tied to a fixed volume around a village center (see below), so a golem standing outside your platform may be inside that volume.
- If you find golems in unexpected places, move the collection point or block off the other valid surfaces, then watch the next few spawn cycles before deciding the farm is broken.
Check villager and point-of-interest links
Villagers need the right links to beds and workstations, and those links can break without any visible change. Common causes include:
- A villager has been removed, killed, or replaced, and the new villager is not linked to a bed or job site.
- A bed or workstation was placed, broken, or moved nearby, changing which block a villager is attached to.
- Villagers moved outside the area where their workstation link is kept, or traded with a new workstation.
- A farm was rebuilt or extended, and the beds that define the village center are no longer where the design expects.
The game does not clearly show which bed currently defines the village center, according to the Minecraft Wiki’s iron golem farming tutorial. You will usually need to infer it from the layout: the center starts at the pillow of the first linked bed, so check the bed nearest your platform before assuming it is the anchor.
Bedrock Edition: the village rules
Bedrock farms depend on a linked village, not on a single trigger. The Minecraft Wiki’s iron golem farming tutorial lists the following village requirements. These figures come from that community-maintained page and may not match every current Bedrock release.
| Requirement | Value stated in the tutorial | What to check on your farm |
|---|---|---|
| Beds | At least 20 beds | Count beds linked to villagers, not just beds placed. |
| Villagers | At least 10 villagers | Confirm the count is still met after any removals or breeding. |
| Recent work | At least 75% of villagers worked at workstations the previous day | Look for villagers with lost or unclaimed job sites. |
| Bed links | All villagers linked to beds | Check every villager for a bed link, including new ones. |
| Active presence | Within a player’s simulation-distance volume | Stay close enough that the village is simulated while you test. |
| Spawn space | Valid space in the spawn volume | Clear obstructions and confirm the platform sits inside the volume. |
| Golem allowance | A limit on naturally generated or spawned village golems relative to villager count | Accept that spawning slows or stops once the allowance is reached. |
The spawn volume and the village center
The tutorial describes a 17×13×17 spawn volume around the village center, extending 8 blocks horizontally and 6 blocks vertically from the relevant point of interest. The center starts at the pillow of the first linked bed. It can move when villagers link or unlink from points of interest, or when villagers or points of interest are removed.
This is the most common hidden cause of a Bedrock farm that stops working after a change. If the center moves so that your platform falls outside the volume, golems can stop spawning on it even though the village still meets the population rules. The tutorial recommends clustering beds and extending platforms around the relevant outer bed pillows to keep the platform inside the volume.
Workstation links and bug reports
A Mojang Bug Tracker report describes Bedrock golems failing to spawn when villagers are not linked to workstations. The same report contrasts this with Java’s 1.16 change, which allowed golem summoning without professions. The report lists affected versions and no fix version at the time of writing, so treat it as a reported behavior for those builds, not a rule that applies to every current Bedrock release.
Two other Bedrock tracker reports describe a related set of link problems. One says villagers’ job-site claiming is connected with bed links. Another says villagers can keep a workstation link after moving outside a stated linking radius. These reports justify checking for stale or misassigned links if your farm broke after villagers moved or blocks changed. They do not show that every farm is affected.
Java Edition: the villager triggers
Java golem spawning is driven by a group of villagers reacting to an event, not by a population table. The Minecraft Wiki’s tutorial describes two village-based triggers:
- Gossip group: five villagers, with at least one gossiping.
- Panic group: three panicking villagers. Panic is commonly induced by a hostile mob such as a zombie.
Java villagers do not need professions for this, which is the main difference from the Bedrock workstation rule above.
The timing and spacing checks
| Condition | Value stated in the tutorial | Why a farm can fail it |
|---|---|---|
| Recent sleep | Villagers have slept within the last 20 minutes | Villagers stuck outside beds, or beds lost in a rebuild, stop meeting this. |
| Group radius | Within a 10-block radius | Spreading villagers across a wider area breaks the group. |
| Recent golem | No iron golem within a 16-block radius in the previous 30 seconds | A golem you just killed or that was just summoned nearby can block the next spawn. |
| Recent summon | A villager that recently summoned must meet the tutorial’s cooldown condition | Rapid retesting can keep the same villagers from triggering again. |
The tutorial presents these figures as mechanics values from a community page. Confirm them against your exact game version if you need precise timing.
Panic designs need the threat to stay visible
A panic-based farm depends on the villagers seeing a threat while still being able to satisfy the design’s sleep interruption requirements. If the threat is removed too early, or the villagers are not interrupted from sleep, the trigger may not fire. Check that the threat mob is still reachable and that the villagers are not stuck in a state where they cannot sleep or react.
Troubleshooting by symptom
| Symptom | Most likely cause | First check |
|---|---|---|
| Golems stand outside the platform | Spawn volume or village center has shifted, or the platform is outside the valid area | Locate the first linked bed and compare the 17×13×17 volume to your platform (Bedrock). |
| No golems at all, and village looks normal | Missing bed links or workstation links | Check every villager for a bed link and a job site (Bedrock). |
| Spawning stopped after a new villager arrived | New villager lacks a link, or the golem allowance is reached | Confirm the new villager is linked; count existing golems (Bedrock). |
| Panic farm stopped working | Threat removed too early, villagers not reaching sleep, or group spread out | Confirm three villagers are panicking within 10 blocks and have slept in the last 20 minutes (Java). |
| Gossip farm stopped working | Group below five villagers, or no gossiping villager | Count the group and confirm at least one villager is gossiping (Java). |
| Golems appear only when you are far away | Village is outside your simulation distance | Stay within simulation distance while testing (Bedrock). |
Recent changes that break a working farm
Most failures follow a change you made, even a small one. Check these events in the order they happened:
- Villagers were removed, killed, or traded away.
- Beds or workstations were placed, broken, or moved nearby.
- The farm was rebuilt, extended, or moved.
- The game was updated, or a server or Realm was restarted or reset.
If the farm stopped right after an update, check whether the behavior matches a tracker report for your build. Those reports are clues tied to specific versions, not evidence that every release behaves the same way. For a Bedrock farm, the link and spawn-volume checks above will catch most of these cases before you need to rely on a bug report.
Community posts sometimes repeat the Bedrock figures with less context. A user-submitted post on the Minecraft Feedback site from October 2022 describes the same bed and villager counts, but it is not an official statement from Mojang and should not be used as a rule for a current release.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
