Minecraft Status Effects Wheel for Java Edition 26.2
The Minecraft status effects wheel chooses one of the 40 effects registered
in Minecraft Java Edition 26.2. Use it to plan a challenge video, assign test
cases for a datapack, create a minigame condition, or break a tie when a group
wants one random gameplay modifier. Every slice has equal weight, so the result
is a transparent picker—not a claim about how often an effect occurs in-game.
The scope matters. A status effect is not always a potion. Speed and Strength
have familiar potions, while Glowing, Hero of the Village, Mining Fatigue,
Raid Omen, Trial Omen, Wind Charged, and several others come from different
mechanics or commands. Calling the whole set “potions” would be convenient but
incorrect. This page therefore uses the registry-level status-effect boundary.
How the 40-effect list was verified
The list was checked against the English effect.minecraft.* translation keys
inside Mojang's official Java 26.2 client, downloaded through the official
version manifest. That mechanically produces 40 unique names, including the
newer Breath of the Nautilus effect. Mojang's
Java 26.2 release notes
establish the release boundary and its June 16, 2026 release date.
Snapshots are deliberately excluded. Mojang currently lists 26.2 as the latest
stable Java release while 26.3 snapshots are still changing. Bedrock Edition
also has different version numbers and may expose a different set. If you play
another edition or install mods, edit the wheel instead of treating this list as
universal forever.
Set a fair random-effect challenge
- Choose the trigger. Spin after a death, completed advancement, elapsed
interval, mined block count, or finished round. - Choose the target. Decide whether the result affects one player, every
player, a mob, or the next arena encounter. - Set duration and strength. Write one duration and amplifier rule before
the first spin. A level that is amusing for Speed can make another effect
disruptive or unplayable. - Create an exclusion rule. Remove effects that cannot work in the chosen
mode, that require unavailable commands, or that would end the activity too
early. Do this before seeing a result. - Keep a run log. Record the spin, start time, duration, and outcome so a
multiplayer group or video audience can follow the rules.
Use a copy of the world when testing unfamiliar commands. Instant Damage,
Wither, Levitation, Blindness, and similar results can destroy a run or strand a
player when applied with extreme values. The wheel does not execute a command,
select an amplifier, or protect a Realm; it only chooses a label.
Adapt the wheel for maps, classrooms, and development
For a survival-friendly pool, remove command-only or context-specific results
and keep effects your players can obtain under the map's rules. For a command
lesson, pair each result with a separate task to look up its namespaced ID and
write a valid /effect command for the installed version. For QA, enable
elimination mode and test every effect once against the same entity setup.
Weights can model a designed challenge pool, but they are not Minecraft's
official probabilities. Keep every weight at 1 for a fair random selection, or
raise only the effects your rules intentionally need more often. Share the
configured URL after editing so every participant sees the same pool.
For a broader activity that changes objectives rather than status conditions,
use the Minecraft Challenges Wheel. The Minecraft status effects wheel is the better fit when the decision is specifically which
Java 26.2 effect should shape the next test, round, or gameplay segment. Review
the version label whenever Mojang publishes a stable release, then update the
pool from the shipped registry instead of guessing from old potion guides.