Lush cave finder release: Java and Bedrock comparisons

Our lush cave finder is available for Minecraft Java and Bedrock. Enter your seed to find nearby predicted lush cave areas, with coordinates and the heights where the model places the biome. You can search from estimated world spawn or from your own position.

Our initial comparisons on October 14, 2026 matched the Java 26.3 sample and exposed Bedrock differences: five extra lush predictions and six missed lush positions. We corrected the Bedrock finder’s predicted locations and height bands, then completed a separate comparison on three fresh seeds. The revised output had no extra or missed lush positions among the 11,520 positions compared. Those results support the selected cases; finder outputs remain model predictions.

What the finder gives you

Each result lists X, Y and Z, predicted lush height bands, distance and direction from your starting point, and an approximate area. A column means one X, Z position considered at different heights. Separate predicted lush bands are listed individually.

The map helps you see where the returned areas sit around your starting point. You can select a result, copy its coordinates or open it in the seed map at a predicted lush height. That view shows the biome at the chosen height; lush caves higher or lower can fall outside the displayed slice.

The supported checkpoints run from Java 1.18.2 to 26.3 and Bedrock 1.18.0 to 26.50. Choose a version the tool lists for your edition. The two editions use separate models, so checking a Java prediction does not establish the corresponding Bedrock result.

What the initial game comparisons found

The initial comparison used three seeds and 30 columns per edition. Java 26.3 predictions were compared with Java 26.3 generation; the Bedrock 26.50 model was compared with Minecraft Bedrock 1.26.52.

Edition and samples	Lush matches	Extra	Missed
Java: 2,880 cells	15	0	0
Initial Bedrock: 2,880 positions	17	5	6

Extra means the model predicted lush caves where the game did not; Missed means the reverse. Non-lush matches were 2,865 in Java and 2,852 in Bedrock.

Java compared stored biome cells; Bedrock compared the game’s biome at selected physical positions. Their different observation scopes do not establish an accuracy ranking between editions. Most samples were non-lush, so an overall match percentage would obscure the Bedrock errors.

Java’s stored-cell height bands matched at all nine returned columns compared with the game. The initial Bedrock finder did worse: seven of nine returned columns contained lush at the heights compared, and only three agreed on membership at every compared height. Those are the original implementation’s results, retained in the initial measurements.

Bedrock follow-up on fresh seeds

The revised Bedrock finder corrects its predicted lush-cave locations and heights. This correction applies to the lush cave finder; other Bedrock tools retain their own limits.

We first compared the revised predictions with the original 2,880 game observations. All 23 lush and 2,857 non-lush positions agreed. That is development evidence on known cases, kept separate from the fresh comparison below.

The fresh comparison used three previously unused seeds, 30 columns and 11,520 physical positions in Minecraft Bedrock 1.26.52, with the revised Bedrock 26.50 predictions.

Comparison and samples	Lush matches	Extra	Missed
Retained: 2,880 positions	23	0	0
Fresh: 11,520 positions	141	0	0

The fresh sample also had 11,379 non-lush matches. All nine returned columns contained lush caves, and their reported height bands matched at every height in those selected columns. An incomplete earlier follow-up is excluded from these totals. The repair and fresh measurements keep the phases and limits separate.

This is a small selected sample, not an accuracy rate across all Minecraft seeds. Agreement on known cases and fresh seeds does not prove the finder catches every lush pocket.

A lush biome is not an entrance

Biome data says which biome applies at a location and height. A position assigned to lush caves can still be solid rock. Matching that data does not establish an open cavern, greenery, water or a route you can walk through. Inspect a result in your world before treating it as an accessible cave.

The fresh Bedrock height comparison covers selected columns, not every biome boundary in the world. Java’s earlier stored-cell comparison does not establish final boundaries at individual blocks. Area sizes remain estimates, and small pockets between sampled positions can be missed. Complete nearest-area coverage, area estimates and the large-area filter remain unmeasured.

Use the version that generated your world

Choose the edition and version that generated your area. An upgraded world can contain chunks from different releases; our generation-version guidance explains this. The comparisons cover the named versions with default terrain settings; Java Large Biomes was off. Other supported checkpoints have not gained game evidence here.

Spawn is an estimate. For a search near your base or current position, enter your own X and Z instead. Keep the result’s heights with its horizontal coordinates when you return to the game.

For existing worlds with actual cave pictures, browse our Java lush cave seeds. Each seed page identifies the version and locations checked in game and keeps those checks separate from the map’s predictions.