Minecraft Sift Versions: Java, Bedrock & Dungeons II

Start with the game, not the keyword

Sift versions are easiest to understand when you separate the product, release channel, game build, and any mod file. A search result may use the same dimension name for Dungeons II, vanilla Minecraft, and a fan project. Those results do not describe a single installable feature. The first useful compatibility question is therefore which game you are actually launching.

For Java players, the launcher profile and its mod loader are essential context. Bedrock players need information that explicitly applies to Bedrock rather than a Java archive. Dungeons II players need guides for the separate dungeon-crawling game. Choosing the correct branch prevents the rest of the research from starting with an incorrect assumption.

This comparison describes Sift versions using evidence checked on September 27, 2026. It is a dated reference rather than an automatically updated release service. If you need a quick answer for a specific installation, the version checker uses the same reviewed records and links you to the next relevant guide.

Compare Sift versions by edition

Branch	Evidence in this snapshot	Practical next step
Dungeons II	Sift announced; game launch scheduled for September 29, 2026	Check the official product and launch information
Java vanilla	Inclusion announced for 2027	Follow official release and snapshot notes
Bedrock vanilla	Included in the 2027 announcement	Follow official release and Preview notes
Mielon’s mod	Specific Java file combinations are listed	Match the file, game version, loader and dependencies
Wellspring	A specific NeoForge alpha file is listed	Review its alpha instructions and exact file

The important difference is the type of evidence. An announcement describes a plan. A file listing identifies something an author distributes. A playtest would describe observed behavior under recorded conditions. Comparing Sift versions means preserving those differences instead of using one broad “available” label for all of them.

None of the rows establishes that every device, server, modpack, or region is supported. Read the linked source when that detail affects your next decision. A simple comparison is useful precisely because it makes the remaining checks visible.

Four details that identify an installation

Write down the game title first. Then record the exact game version, including punctuation. Next, identify the release channel or loader. Finally, include the mod filename and release when applicable. These four details are usually enough to distinguish the main Sift versions discussed on this site without sharing your account details, computer username, or entire configuration directory.

For example, a Java profile using Minecraft 26.3 with Fabric and a named Mielon release is more specific than “latest Minecraft.” The latter can change whenever a launcher updates. It also fails to distinguish the latest game release from the latest file for a particular mod branch. A guide written around “latest” can therefore become ambiguous very quickly.

Preserve the exact details when asking another player to reproduce a result. If they use a different loader or neighboring game version, they are testing a different setup. This is not needless formality: it is what makes advice about Sift versions repeatable rather than a collection of apparently contradictory anecdotes.

A project tag is not a file guarantee

Mod project pages often summarize several releases with game-version and loader tags. Those summaries help people discover the project, but they do not prove that every listed loader works with every listed game version. The file page is the more precise evidence for an installation decision.

The reviewed Mielon records include a 26.3 Fabric file, a 26.2 Fabric file, and a 1.21.1 NeoForge file. Our checker treats those as separate combinations. It does not manufacture a 26.3 Forge match by combining unrelated project tags. For Wellspring, the reviewed alpha file is tied to 26.1.2 and NeoForge. The author’s file pages remain the place to investigate additional releases.

This distinction makes our Sift versions table deliberately conservative. A missing match means that the reviewed dataset has no verified combination, not that the author has never supported it. Follow the project links before concluding that your installation is impossible. The mod guides explain how to compare a filename and its supporting requirements.

Dependencies across Sift versions

A matching file is only one part of a working installation. A loader release, supporting library, or other dependency can affect whether the game starts. Some dependencies are required; others are optional enhancements. Confusing the two can lead you to install unnecessary software or miss a component the mod actually needs.

When reviewing Sift versions, read dependency instructions for the exact game branch. Do not assume that a requirement written for 26.2 applies unchanged to 26.3, or that a NeoForge library can be substituted into a Fabric profile. When our research has not verified the full dependency set, the tool says so rather than presenting a complete-looking checklist.

A clean test profile is helpful because it reduces the number of variables. First confirm the basic game, loader, chosen file, and required dependencies. Add unrelated modifications only after you have a useful baseline. This is general troubleshooting advice, not a claim that we tested every possible combination or that a listed file guarantees compatibility with your existing world.

Release channels need separate evidence

A future vanilla announcement does not establish that a Java Snapshot or Bedrock Preview already contains the dimension. Conversely, failing to verify a preview is not proof that no preview exists. The appropriate answer is that the reviewed evidence does not settle the question. That is why test-channel results use an unverified state.

The same care applies when an announced launch date passes. Our treatment of Sift versions does not promote a schedule to a confirmed release merely because the calendar changed. The official distribution channel and actual release notes must support that update. A saved page should continue to identify the date its records were checked.

If you encounter newer evidence, compare its publication date, product, and channel with the record here. A console store announcement, a Java snapshot note, and a mod author’s release can all be accurate while describing different events. The updates timeline provides the context for interpreting those events without merging them into one date.

Choose between Sift versions

Use Sift versions as a decision aid. If your goal is official gameplay, follow the correct product’s current announcements. If your goal is a fan implementation, identify an exact mod file and review its requirements. If your goal is to understand the setting, you can read the dimension overview without changing your game installation at all.

Before following a portal guide, match its edition and project to your setup. A procedure can be accurate for its intended audience and useless for another. Keep that distinction in mind when comparing comments that claim the same guide both works and fails. The missing context may be more important than the procedure itself.

Finally, revisit Sift versions when the underlying evidence changes, not simply whenever a headline uses the word “new.” A useful update should add a verified file, establish a released build, clarify a dependency, or document a tested mechanic. That standard keeps this comparison focused on decisions a player can actually make and avoids turning uncertain release coverage into false certainty.