A guardian farm is the biggest build most players will ever attempt, on either edition. Before committing real time to one on Bedrock, it's worth knowing exactly which parts of the Java build translate and which don't. The honest answer is that most of the underlying mechanics are the same structure wearing a different engine, and this guide says so plainly rather than manufacturing differences to justify its own existence.
Our Java guardian farm guide covers the drain-versus-funnel decision and build sequence in full. This is the Bedrock companion: what's genuinely different, what isn't, and what that means for your build.
Who this is for: players who already have a base and decent gear on Bedrock and want an ongoing supply of prismarine-family blocks or top-tier XP. If you only want prismarine once, mining an existing monument by hand is far less work than building a farm. See why Java farm designs fail on Bedrock for the wider pattern this article is part of.
The honest scale, before anything else
A guardian farm is the single biggest build category on this site, on both editions, and most players should not start one as a first automated farm. It means locating and mapping an entire ocean monument, killing three dangerous mobs while fighting a debuff that cripples your mining, then either draining a huge volume of water or precision-tuning underwater flow, all before a spawn platform exists. Nothing about Bedrock shrinks this project; if anything, Bedrock's own spawning behavior, covered below, makes a drained platform even more load-bearing than on Java.
Build this when you specifically want an ongoing supply of prismarine, prismarine bricks, dark prismarine, sea lanterns, and top-tier sustained XP, and you're ready to spend real time on it. If you want prismarine once, mine the monument by hand instead.
The monument is the farm, and that part is identical
Per the Minecraft Wiki's Guardian page and Ocean Monument page, guardians on both editions spawn only within the water inside the generated ocean monument structure, nowhere else. The monument's base footprint is 58x58 blocks on both editions; Bedrock's roof always generates at a fixed Y=56, which Java doesn't pin to a specific level.
That means the core premise of the build carries over unmodified: you cannot relocate or shrink the spawn requirement, and the reason this is a 58x58-footprint project rather than a small spawner box is the same on both editions.
There is no way around this on either edition. The spawn region is fixed to wherever the monument generated. Any Bedrock farm design, drained or not, has to work within that same 58x58 footprint.
Where spawning actually differs: structure-based placement on Bedrock
This is the one mechanical difference that actually changes how you'd approach the build, and it's a real one, not manufactured. Per the Minecraft Wiki's Guardian page:
- Java guardians spawn using the general hostile-mob spawning algorithm, and spawning fails 95% of the time under open-sky conditions above sea level, part of why enclosed monument interiors are viable spawn spaces at all.
- Bedrock guardians use structure-based spawning in 25 predetermined columns within the monument, built into the structure rather than the general algorithm. The wiki notes Bedrock guardians usually do not, or possibly never, spawn directly near a player, and their continued spawning is unaffected by removal of the monument structure.
The practical difference: a Java platform design reasons about light level, sky exposure, and Y-level relative to sea level to make spawns land where you want them. A Bedrock platform works with a fixed set of 25 predetermined spawn columns baked into the structure, not a general open-water spawn check. Reusing a Java platform's light-and-sky logic on Bedrock doesn't get you the outcome that logic was built for, since Bedrock isn't running that algorithm. Build around where the 25 columns actually sit in your monument, not around Java-style spawn-condition optimization.
This is the mechanic to verify before finalizing a Bedrock platform layout: locate where your monument's predetermined spawn columns actually fall, rather than assuming a Java-style drained flat platform automatically maximizes spawns the same way.
Elder guardians, Mining Fatigue, and how players deal with it: identical
Say plainly that these mechanics don't differ, because they don't. Every ocean monument on both editions generates with exactly three elder guardians, fixed in position: one in the top room, one in each wing. They do not respawn once killed on either edition.
Mining Fatigue works the same core way on both editions too, per the Minecraft Wiki's Guardian page: elder guardians apply Mining Fatigue III at a 50-block radius, lasting 5 minutes once applied, reapplying roughly every 60 seconds on Java for as long as an elder guardian stays alive in range. Bedrock differs only in the reapplication trigger: rather than a fixed 60-second cycle, it inflicts any currently unafflicted player within range immediately, which functions the same way in practice since either version keeps you effectively unable to mine near a living elder guardian.
The two ways players deal with it are the same on both editions: drink milk to clear the effect and buy a window to work, or kill all three elder guardians first, which permanently removes the source. The latter is what every serious build eventually needs, since digging out a 58x58 structure under a recurring debuff isn't realistic on either edition.
Guardians in general fire a laser that deals 6 damage plus 2 magic damage on Normal difficulty after a 4-second charge, identical on both editions per the wiki. Bring Water Breathing and Night Vision, and prioritize the three elder guardians before serious digging, regardless of which edition you're on.
Drops: a real Bedrock gap on fish
Per the Minecraft Wiki's Guardian page, regular guardian drops differ between editions in a way worth knowing before you plan the farm's output:
- Java guardians can drop prismarine shards, prismarine crystals, raw cod, raw salmon, pufferfish, and tropical fish, with Looting scaling those quantities.
- Bedrock guardian drops are limited to prismarine shards, prismarine crystals, and raw cod only. The wiki attributes the missing fish variety to a known Bedrock issue (MCPE-57215): Bedrock guardians do not drop the wider fish selection Java's do.
If part of your reason for building this is a varied fish supply, that output is narrower on Bedrock. Raw cod still drops, so the farm still functions as a food source, just not the variety Java's drop table offers.
| Mechanic | Java Edition | Bedrock Edition |
|---|---|---|
| Monument spawn restriction | Only within monument water | Only within monument water (same) |
| Monument footprint | 58x58 blocks | 58x58 blocks (same) |
| Guardian spawning method | General hostile-mob algorithm, sky/light dependent | Structure-based, 25 predetermined columns |
| Elder guardian count and position | 3 fixed: top room + 2 wings | 3 fixed: top room + 2 wings (same) |
| Mining Fatigue effect | Level III, 50-block radius, ~60s reapply | Level III, 50-block radius, immediate reapply |
| Laser damage | 6 + 2 magic on Normal | 6 + 2 magic on Normal (same) |
| Guardian drops | Prismarine shards/crystals + several fish types | Prismarine shards/crystals + raw cod only |
| XP per kill | 10 (guardian), 10 (elder guardian) | 10 (guardian), 10 (elder guardian) (same) |
Drain versus no-drain: does the decision differ on Bedrock?
The two broad approaches are the same on both editions: drain and platform (pump or bucket out the monument, build a flat spawn platform, get the cleanest and highest-ceiling spawns at the cost of the largest labor investment) or an in-place funnel using bubble columns and water flow, less draining but lower and fussier throughput.
Where Bedrock adds a real consideration is simulation behavior away from the player, which matters for any farm you expect to run unattended. Per the Minecraft Wiki's Simulation Distance page, Bedrock's simulation distance is a world option that directly governs mob spawning and despawning, defaulting to 4 chunks (adjustable 4 to 12). Java's simulation distance instead defines a square region of ticking chunks around the player as a video setting, with a considerably larger default (commonly 10 to 12, up to 32). Outside that ticked region on either edition, nothing spawns and nothing moves.
The practical upshot: a Bedrock farm at the lower default simulation distance gives you less headroom to be far from the platform before spawning stops. This favors a drained, compact platform on Bedrock even more than on Java, since it concentrates all viable spawn space within a smaller radius that stays inside a modest simulation distance, whereas an undrained, sprawling funnel across the full 58x58 footprint is more likely to have parts fall outside a tighter Bedrock range. Raising the setting (up to 12) closes some of that gap, at a real performance cost, particularly on Realms or weaker hardware.
If you're deciding between drain-and-platform and in-place funnel specifically on Bedrock, the smaller default simulation distance is a point in favor of draining: it keeps your entire spawn area inside a radius more likely to stay simulated, rather than spread across the monument's full footprint.
Building it on Bedrock
- Locate a monument and mark its 58x58 bounds, identical to a Java build.
- Kill the three elder guardians first. Positions and Mining Fatigue are the same as Java; no shortcut on either edition.
- Locate the predetermined spawn columns rather than assuming a Java-style light-and-sky platform maximizes Bedrock spawns.
- Choose drain-and-platform or in-place funnel, leaning toward draining given Bedrock's smaller default simulation distance.
- Kill and collect, expecting raw cod as your only fish drop rather than Java's wider table.
- Set simulation distance deliberately (up to 12 if hardware allows) rather than leaving the 4-chunk default if the farm runs unattended.
Pros
- The core premise (monument-only spawning, 58x58 footprint, 3 fixed elder guardians, Mining Fatigue, laser damage, XP per kill) is identical to Java, so the elder-guardian fight and general build logic carry over directly
- Structure-based spawning on Bedrock is deterministic once you find the 25 columns, rather than depending on sky exposure and light level
Cons
- Bedrock drops are limited to prismarine shards, crystals, and raw cod; Java's wider fish selection is absent (MCPE-57215)
- Bedrock's smaller default simulation distance makes an undrained, sprawling farm more likely to under-simulate parts of the monument
- No published prismarine-per-hour or XP-per-hour figure exists for either edition
- Among the largest single builds in the game on either edition; realistically multi-session
Common mistakes
Assuming Bedrock spawning works like Java's light-and-sky algorithm. It doesn't; Bedrock uses 25 predetermined structure-based spawn columns. Locate them instead of optimizing for Java-style conditions.
Not killing the elder guardians first. Identical requirement on both editions; Mining Fatigue III within 50 blocks makes serious digging impractical until all three are dead.
Expecting the same fish variety Java drops. Bedrock is limited to raw cod; don't plan around tropical fish or pufferfish there.
Leaving simulation distance at Bedrock's default while running an undrained, sprawling farm away from the platform. The smaller 4-chunk default makes this more likely to under-simulate spawns than the same choice on Java.
Underestimating the drain. A 58x58 footprint is a large multi-session job on either edition.
Frequently asked questions
Do guardians spawn the same way on Bedrock and Java?
No, this is the real difference. Java uses the general hostile-mob spawning algorithm, dependent on light level, sky exposure, and Y-level relative to sea level. Bedrock uses structure-based spawning in 25 predetermined columns built into the monument itself, per the Minecraft Wiki's Guardian page. Build a Bedrock platform around locating those columns, not Java-style spawn-condition optimization.
Is the ocean monument the same size on Bedrock?
Yes. Both editions generate a 58x58-block footprint, and guardians only spawn within that structure's own water on either edition. Bedrock additionally always generates its roof at a fixed Y=56, which Java doesn't pin to a specific level.
Do I still need to kill the three elder guardians on Bedrock?
Yes, identical to Java. Three elder guardians generate per monument, one in the top room and one per wing, applying Mining Fatigue III within 50 blocks on both editions. Kill all three before serious digging; milk clears the effect temporarily in the meantime.
Does Bedrock drop the same fish as Java from guardians?
No. Java guardians can drop raw cod, raw salmon, pufferfish, and tropical fish alongside prismarine shards and crystals. Bedrock drops only prismarine shards, crystals, and raw cod, a known limitation (MCPE-57215) documented on the Minecraft Wiki's Guardian page.
Should I drain the monument on Bedrock, or is an in-place funnel fine?
Both work on either edition, but Bedrock's smaller default simulation distance (4 chunks versus Java's larger default, per the Minecraft Wiki's Simulation Distance page) favors draining and a compact platform if the farm runs while you're away, since a sprawling undrained farm is more likely to fall outside a tighter simulation range.
Is a Bedrock guardian farm worth building?
Only if you want an ongoing supply of prismarine-family blocks and top-tier sustained XP, and you're ready to commit real, multi-session time. If you just want prismarine once, mining the monument by hand is far less work. Most players should not start this as their first automated farm.
This guide is a Bedrock-specific companion to our Java guardian farm guide. See Java vs Bedrock in 2026 for the wider edition gap and redstone differences on Bedrock if your design leans on redstone sorting. Part of our Minecraft farm guides collection.
Sources & further reading:
