The Sift is an announced Minecraft dimension, but the game you are playing matters. Mojang's September 2026 Minecraft Live recap describes it in Minecraft Dungeons II and says it is coming to Java and Bedrock in 2027. Those are separate releases.
This article separates that announcement from server advertising and community speculation. The illustration above is an imagined editorial scene, not an official screenshot or a guide to building a working portal.
What Mojang has confirmed
The September 2026 Minecraft Live recap introduces the Sift through Dungeons II, describing rifts and an interconnected world. It also announces the dimension for Minecraft Java and Bedrock the following year. That announcement establishes the games involved and a year; it does not provide a complete Java or Bedrock server deployment guide.
| Information you find | What it can establish | What it cannot establish alone |
|---|---|---|
| Official Dungeons II material | What is shown or described for that game. | That the same mechanic works in a Java survival world. |
| The Java and Bedrock announcement | Mojang's stated plan to bring the dimension to those editions. | A precise release day, final portal recipe or plugin compatibility. |
| A community server event | What that server has built or configured. | That it contains the official future dimension. |
| A fan concept or theory | An idea someone would like to explore. | A confirmed feature or release commitment. |
What this means when choosing a server
If a listing advertises “Sift gameplay,” read the description before installing anything. Ask whether it means a custom event world, a mod, a data pack or an officially supported game feature. The name on a banner is not enough to identify the implementation.
Request the edition, exact game version and any required downloads. A Java server address is not a Dungeons II multiplayer invitation. If a server requires a modpack, use the pack release linked by its owner and check that the installation instructions identify the same version. Do not assume a video of one game demonstrates what happens after connecting to a different game's server.
- For ordinary multiplayer: browse the Java or Bedrock directory and compare the features available now.
- For an event: check its start and end dates, inventory rules and whether the event world will be deleted.
- For upcoming official content: use Mojang's release notes to confirm availability in the exact build, then check the server owner's supported versions.
Details that need their own confirmation
A release announcement should not be expanded into an invented recipe or technical checklist. Before publishing instructions for the Java or Bedrock Sift, verify the access method, required version, world-generation behavior and any experimental settings from the relevant official release documentation.
Likewise, do not promise that an existing world must be reset or that no migration work will be needed. Those decisions depend on the final implementation, your server software and your own world policy. An early trailer cannot answer every operational question.
When sharing news with your community, link the announcement and label the remaining questions openly. A small “confirmed / awaiting details” list is more useful than a countdown based on a guessed date. If the official plan changes, update that note and explain the change instead of silently preserving an outdated promise.
Planning an inspired event without misleading players
You can run an exploration event while waiting for a future release, provided the description accurately calls it a custom event. Build the activity around a goal you control: a mapped expedition, a cooperative scavenger hunt or a temporary build challenge. Avoid presenting invented mobs or portal rules as official Sift mechanics.
- Define the experience. Write one sentence describing what players actually do, such as exploring a custom map to collect three marked objectives.
- Separate progress. Decide whether inventories, currency and deaths affect the main survival world. Publish the rule before players enter.
- Provide a reliable exit. Test returning to the normal world with a regular account, including after a disconnect.
- Keep rewards predictable. Use a commemorative item or a modest fixed reward. Explain whether it can be claimed once per player.
- Publish the end date. Tell builders whether structures survive after the event and give them time to take screenshots or move allowed items.
Prepare a staff note covering stuck players, lost items and an emergency shutdown. An event can be small and still feel considered when players know the objective and trust the rules. A large unfamiliar map without those details often creates more support work than adventure.
Sift questions
Does the announcement mean I can build a Sift portal in any Java world?
No. An announcement for a future release is not an instruction for an existing build. Check official notes for the precise version before trying a recipe or changing a world.
Are Dungeons II features automatically Java and Bedrock features?
No. Treat each game's documentation separately. Similar names or settings do not establish matching mechanics, multiplayer systems or release dates.
Should a server advertise the Sift before it supports it?
It can discuss plans, but its listing should distinguish planned features from playable ones. Describe a custom event as custom, and only claim official support after verifying the actual release and server setup.
Before changing a persistent world for any new release, use the separate-world testing workflow and keep a tested restore path.