MINECRAFT GUIDES
How to Enable Cheats in Minecraft Without Following an Outdated Guide
The steps change depending on your edition, your world, and whether you actually have permission to use commands.
If you just searched “how to enable cheats in Minecraft,” you already know what’s waiting for you: eight tutorials, eight answers, and none of them working. One says open your world settings. Another says press Esc and look for a button that isn’t there. A third mumbles something about a server console you’ve never touched.
Nobody’s lying. They’re all just playing different games that happen to share a name.
That’s the actual problem. There isn’t one universal “enable cheats” path in Minecraft. It depends on whether you’re playing Java or Bedrock, whether the world is new or already exists, and whether you’re playing a single-player world, a Realm, or a server. And even after commands are enabled, permissions can still stop them from working. The good news is that the current versions are simpler than many older guides make them look — especially on Java, where existing worlds can now enable commands directly from World Options. This is the path through each situation, without mixing the two editions together.
First, know which Minecraft you’re playing
Look, I’m not trying to be condescending. This is the #1 reason every tutorial fails you, so it’s worth thirty seconds.
- Java Edition — the PC classic. If you bought it through the Minecraft launcher on a desktop and it runs on the Java runtime, this is you.
- Bedrock Edition — the one on Windows, consoles, and mobile, and the cross-play one. On Windows this is often the version that came with Game Pass.
If the launcher says “Minecraft for Windows,” that’s Bedrock, not Java, even though it’s on PC. I still mix these up and I play both. Anyway — from here on, the steps are completely different, so keep your version in mind.
Java: brand-new world
When you’re creating a Java world, it’s one setting: Create New World → Allow Commands → ON. Older guides may call this Allow Cheats, but current Java versions use Allow Commands in the world options. Once the world is created, enter the game and open the chat with / to start using commands. The exact label can vary by version, so if an older tutorial tells you to look for "Allow Cheats," don't assume the feature has disappeared — look for the commands setting instead.
Java: a world that already exists
This is where older Minecraft guides can send you in the wrong direction. If your Java world was created without commands, you do not need to delete it or open it to LAN just to enable commands in current versions.
In current Java versions, open the pause menu and go to:
Esc → World Options → Allow Commands → ON
The setting is available to the host of the world, so you can enable commands directly in an existing single-player world without turning it into a LAN game. Minecraft 26.2 added the Allow Commands control to the World Options screen specifically for this purpose. Minecraft Java Edition 26.2 release notes
That also means several pieces of older advice are now outdated. The familiar Open to LAN → Allow Cheats → Start LAN World method was historically used to enable commands temporarily in an existing Java single-player world, but it is no longer the normal route for the current version. Open to LAN still exists, but its current purpose is mainly to configure what other players can do when they join your LAN world.
One important exception: Hardcore worlds do not have the Allow Commands option. The current Java version specifically removes the Game Mode and Allow Commands controls from Hardcore worlds.
Bedrock: the easier, more expensive version
On Bedrock, this is actually simpler — and one decision carries a permanent cost most guides skip.
New world: Create New → Game Settings → Cheats → Activate Cheats. Confirm the warning, done.
Existing world: No LAN trick needed. Pause → Settings → Game → Cheats → Activate Cheats. Or edit the world from the list, same place. That’s the whole difference from Java — you can flip it on for an existing world directly, no session tricks.
The cost: once you activate cheats in a Bedrock world, that world can no longer earn achievements. It’s not simply disabled while cheats are active; turning cheats back off does not restore achievement eligibility for that world. Microsoft’s current Bedrock command documentation explicitly warns that enabling cheats disables achievements for that world.
Get Willanlima’s stories in your inbox
Join Medium for free to get updates from this writer.
So before you hit that toggle, decide what the world is for. If it’s mainly for Creative building, testing, or experimenting with commands, the trade-off may not matter. If it’s your main Survival world and achievements matter to you, keep a separate world for commands instead.
One important distinction: Java and Bedrock don’t use the same achievement system. Java uses Advancements, while Bedrock uses Achievements tied to its platform system. So the warning that “enabling cheats disables achievements” should not be applied to both editions as if they worked identically. The permanent achievement restriction described above is specifically the Bedrock behavior.
You enabled cheats. Your commands still don’t work. Why?
Turning cheats or commands on is only part of the permission chain. If a command still refuses to run, check player permissions and the type of world you’re actually playing.
- Java single-player: If you’re the host and commands are enabled in World Options, commands should be available. If they aren’t, check that commands are actually enabled in the current world.
- Bedrock: Cheats must be enabled, and the player may also need the Operator Commands permission. Microsoft specifically notes that this permission is required to run commands in chat and access command blocks, particularly on existing worlds or for other players.
- Someone else’s server or Realm: You need sufficient permissions from the owner or administrator. Enabling a setting on your own client cannot give you permissions you don’t have.
- Your own Java server: You generally need an appropriate operator/permission level. On a server you control, an administrator can grant OP with
op YourUsername, after which commands that require that permission level become available.
So if you see a “cheats enabled but commands don’t work” problem, don’t keep toggling the same switch. First determine whether you’re dealing with a single-player world, Bedrock player permissions, or server-side operator permissions.
Cheats aren’t creative mode
Quick note, because it changes how you’ll use all this: cheats = the ability to run commands. Creative mode = one of the things those commands can do. You can stay in survival and still use commands, and you can be in creative with cheats off. Separate dials.
Once commands are enabled, these are some of the most useful examples. Minecraft: How to Use Commands
/gamemode creative
/give @s diamond 64
/gamerule keepInventory true
/tp @s 100 80 100
/time set dayThese cover the most common reasons people enable commands in the first place: changing game mode, getting test items, adjusting survival rules, teleporting, or changing the time of day. If you’re following a command guide, make sure it matches your Java or Bedrock edition, because some commands and their syntax differ between versions.
If you want lighter changes than Creative mode
Enabling commands isn’t the only way to change how demanding a Survival world feels, but it is the official in-game route. If you only want a narrower change — such as making survival less punishing without switching the whole world to Creative — third-party trainers are another option on PC.
For example, Minecraft Bedrock Edition trainer options include features such as Infinite health, Fill hunger, No hunger, and Easy block breaking. These are different from Minecraft’s built-in commands because they come from an external tool rather than the game’s command system.
This is separate from enabling cheats in Minecraft, and third-party trainers are not an official Minecraft feature. If you use one, check that it supports your game version and use it only in worlds where you’re comfortable modifying the gameplay.
The whole thing, compressed
- Java new world → Create New World → Allow Commands → ON.
- Java existing world → World Options → Allow Commands → ON. No Open to LAN required in current versions. Hardcore worlds are an exception because the option is unavailable.
- Bedrock new or existing world → Settings → Game → Cheats → Activate Cheats. Enabling cheats permanently removes that world’s eligibility for achievements.
- Multiplayer → you also need the appropriate operator/player permissions; the exact setup depends on whether you’re using a server, Realm, or LAN world.
- Commands enabled but not working → check player/operator permissions and make sure the instructions match your edition.
That’s the whole maze. The main thing to remember is that Java and Bedrock handle commands differently, and older Java guides may still send you to Open to LAN even though current versions let the host enable commands directly from World Options. If you only want to make Survival less punishing, built-in commands are the simplest official option; third-party tools are a separate route, not another way to enable Minecraft’s own cheats.
Image Credits & Fair Use Disclaimer: Images © Mojang Studios, XMODhub, and respective owners. Used for editorial commentary under fair use where applicable.
