How to enable cheats on a Minecraft Bedrock server?

Want faster building, easy testing, or full admin control? Turn on cheats on your Minecraft Bedrock server in minutes. Need stability? Check our optimized Minecraft hosting.

Prerequisites

• Access to your Oxygenserv panel (login and password)
• An existing Minecraft Bedrock server (not Java)
• Permission to stop/restart the server
• Your in-game name and ideally your XUID (we’ll show how to find it)
• A recent world backup (in case you want to roll back)

Step-by-step

1. Cleanly stop the server
   Log in to the Oxygenserv panel and open the “Console” tab. Click the red “Stop” button and wait for “Server stopped” in the logs. If the button doesn’t react, refresh and try again. Don’t continue until the server is fully stopped.
2. Enable cheats in server.properties
   Go to “Files” and open server.properties in the editor. Find allow-cheats=false and change it to allow-cheats=true (exact spelling). Click “Save” at the top right. Note: enabling cheats disables achievements on this world.
3. Restart to apply changes
   Back in “Console”, click the green “Restart” button. Watch for “Server started” in the logs. If a syntax error shows up, reopen server.properties and fix any extra spaces or characters. Give it 10–20 seconds after startup before joining.
4. Grant yourself operator (OP) to run commands
   Two options, use what works for you:
   a) Try via console: type op YourName (no slash). If you get “Unknown command”, use option b).
   b) Use permissions.json:
   – Join the server once to generate your XUID, then open the logs folder and check latest.log. Look for a line with your name and an XUID (e.g., 253546...).
   – Open permissions.json and add: [{"permission":"operator","xuid":"253546..."}]. If entries exist, add another JSON object, keeping commas and quotes correct.
   – Save and restart. If you see “Failed to parse permissions.json”, fix the JSON (commas, quotes, brackets).
5. Run cheat commands (in-game or via console)
   In-game (as OP), open chat and use slash commands like /gamemode creative YourName, /time set day, /give YourName diamond 64, /tp YourName 0 100 0, /effect give YourName regeneration 30 1. From the panel console, run the same commands without / (e.g., gamemode creative YourName). If you get “You do not have permission”, confirm you’re set to operator and allow-cheats=true is active.

Tips & optimization

– Back up before enabling cheats; achievements will be disabled for this world.
– Handy gamerules: /gamerule keepinventory true, /gamerule doDaylightCycle false, /gamerule doMobSpawning false as needed.
– Keep a dedicated admin account as operator, leave players as member in permissions.json to prevent abuse.
– Use console for global actions (e.g., time set day) and chat for quick tests.
– Default Bedrock port is 19132 UDP; useful for network checks.

FAQ

Cheats still don’t work with allow-cheats=true. What now?

Check 1) the server actually restarted, 2) your account is operator in permissions.json (or op YourName succeeded), 3) you use / in-game and no / in console. If permissions.json fails to load, fix JSON syntax.

Can I re-enable achievements later?

No, not on this world. To earn achievements again, set allow-cheats=false and start a new world or restore a pre-cheat backup.

How do I remove operator from a player?

Edit permissions.json and change "operator" to "member" for their XUID, then restart. Or use deop Name if your version supports it.

Console vs in-game commands?

In-game requires OP and uses /command. In the panel console you run commands without /, and they apply server-wide even if you’re not online.

You’re set to manage your Bedrock world like a boss. Test, tweak, have fun—and keep full control of your server.

Related articles

• Introduction to the world of Minecraft servers
• How do you choose the right features for your Minecraft server?
• 10 must-have plugins for your Minecraft server