What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Project Zomboid has two separate cheat systems. In a solo game, add -debug to Steam’s launch options and use the developer overlay. In multiplayer, use slash commands in chat or the server console, but only after your account has the required server access level. Turning on -debug does not make you an administrator on a server.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Project Zomboid servers with free DDoS protection and up to three free backups a day.
Solo debug menu versus multiplayer admin commands
Choose the method that matches your game mode. The debug menu is a local development and testing tool. Multiplayer commands are server-authorized operations controlled by access levels and capabilities.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →| Control path | Where it works | How you start it | Typical uses | Main risks |
|---|---|---|---|---|
| Solo debug overlay | Local single-player worlds | Add -debug in Steam launch options, then load a world |
Inspect tiles, test recipes and sandbox settings, spawn items, teleport while testing, and recover a disposable test save | Accidental save changes, instability, and confusion when testing a live save |
| Multiplayer administration | Dedicated or hosted multiplayer servers | Obtain a server role, then enter commands in chat or the server console | Grant items or XP, teleport players, toggle god mode, moderate users, spawn hordes, and save the server | Performance problems, rule violations, griefing, or damage to a shared world |
Build 42 changes make old command lists unreliable. The official game site currently lists Stable Build 42.21 and Unstable Build 42.21. Build 42’s multiplayer release is described as stress testing, and updates can disrupt an existing world. Treat every command list as version-sensitive: run /help on your server and confirm the role permissions after an update.
How to enable the Project Zomboid cheat menu in solo play
The solo “cheat menu” is the developer debug overlay. It is not a chat command system and does not grant rights on a remote server.
#1 Best Overall
- UPDATED CLASSIC: Dive into Zombicide: 2nd Edition, the thrilling update to the classic zombie-slaying game. Experience enhanced gameplay and new challenges in the zombie apocalypse.
- COOPERATIVE SURVIVAL: Join forces as Survivors in a world overrun by zombies. Work together to navigate through missions, complete objectives, and fight for survival.
- ADRENALINE-POWERED ACTION: With each zombie kill, increase your Adrenaline Points. Gain strength and skills but attract more zombies with your actions – a double-edged sword.
- INTENSE MISSIONS: Face a series of challenging missions, each requiring strategic planning, teamwork, and bravery. Can you accomplish your objectives while fending off the undead?
- SURVIVE OR BECOME ZOMBIE PREY: The stakes are high - will you emerge as a triumphant survivor or fall victim to the relentless zombie hordes?
- Open Steam and select Library.
- Right-click Project Zomboid, choose Properties, and stay on the General tab.
- Find Launch Options and enter
-debug, including the hyphen. - Close the Properties window, launch the game normally, and load a world.
- Use the developer overlay that appears to inspect the map and test the functions you need.
Use a copy of a save, or a newly created test world, before experimenting. The overlay can alter inventory, character state, map objects, recipes, and other world data. When testing is finished, quit the game, remove -debug from Launch Options, and restart before returning to a normal save.
What the debug overlay is good for
- Inspecting tiles and map objects while diagnosing a building or collision problem.
- Testing recipes, sandbox settings, lighting, and other Build 42 systems without spending in-game time.
- Spawning test items and moving a character to a location on a test map.
- Checking or restoring a damaged disposable test save.
- Reproducing a bug in a controlled world before reporting it.
Some debug controls behave like invincibility or can bypass normal progression, but they are intended for development and testing rather than ordinary survival play. Do not assume a debug toggle will carry over to multiplayer.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhy slash commands do nothing in solo play
Commands such as /godmode, /additem, and /teleport are server commands. A normal solo world does not provide the multiplayer command interpreter, so typing them into a chat box usually produces no result. Use the -debug overlay for local testing instead.
If you are playing a locally hosted multiplayer session, it is still the server’s access system—not the Steam launch option—that decides whether a command is accepted. A player can have -debug enabled and remain unauthorized.
How to become an admin on a Project Zomboid server
You need an existing server owner or administrator to grant access. On a dedicated server, the command can be entered in the server console without a leading slash. In in-game multiplayer chat, use the slash form:
/setaccesslevel "PlayerName" adminReplace PlayerName with the exact account or character name expected by that server. Quotation marks are safest when the name contains spaces. After the access level is changed, reconnect if the server requires it and test a harmless command.
Free tools Windows power users keep installed
One-click scans. No signup required.
Build 42 access levels
Build 42 documentation describes six access levels, including admin, moderator, overseer, gm, and observer (the sixth level is server-defined in the command documentation). These are not interchangeable labels: each level can expose a different capability set. A moderator may be able to manage players but not use every spawning or world-editing command, while an observer may have monitoring rights only.
Server configuration can change which commands a non-admin role may execute. If a command works for an administrator but not for a moderator, check the server’s capability configuration rather than repeatedly changing the command spelling.
Where to enter commands
- In-game chat: Prefix the command with
/, for example/godmode -true. - Server console: Enter the command itself; many console interfaces do not require the leading slash.
- Exact identity: Use the player name recognized by the server. Display names, Steam names, and character names can differ depending on the server setup.
Never paste an untested command into a live public server. Save first when possible, explain the change to other players, and use the least powerful access level that accomplishes the task.
Useful Build 42 commands
The Build 42 command reference reports 71 commands, six roles, and 35 skill names accepted by /addxp. The examples below are the commands most useful for testing, administration, and recovery. Availability can change between stable and unstable builds, so confirm with /help and your server’s permissions.
Recommended Free Tools
| Command | Example | What it does |
|---|---|---|
/additem |
/additem "rj" Base.Axe 5 |
Gives a player a specified item and quantity. The item uses its module and item identifier. |
/addxp |
/addxp "playername" carpentry=1000 -true |
Grants XP to a named perk. The final multiplier argument is optional; use a valid Build 42 skill name. |
/teleport |
/teleport "playername"/teleport "player1" "player2" |
Teleports you to a player, or moves one named player to another. |
/teleportto |
/teleportto 10600,9500,0 |
Moves the executing player to x,y,z coordinates. Confirm coordinates for your map and build. |
/godmode |
/godmode -true/godmode -false |
Turns invincibility on or off. The command reference also lists /godmod as an alias. |
/invisible |
/invisible |
Toggles the staff visibility state documented for the server command set. |
/noclip |
/noclip |
Toggles staff movement through obstacles where the role is allowed to use it. |
/createhorde |
/createhorde 50 "username" |
Creates a horde near the named player. Use small counts on a test server first. |
/kickuser |
/kickuser "username" |
Removes a player from the server. |
/banuser |
/banuser "username" |
Bans a player according to the server’s moderation settings. |
/save |
/save |
Requests a server save before maintenance or a planned restart. |
Item identifiers and XP names
/additem requires the internal module-and-item form, not the name shown on a handwritten list. The reference example uses Base.Axe. If an item fails, verify capitalization, punctuation, and the identifier for your installed build or mod set.
For /addxp, the perk name must be one of the server’s accepted skill names. Build 42 documentation lists 35 names. A malformed perk expression, an unsupported skill, or a role without XP privileges can make the command appear to do nothing.
Build 42 command limitations and volatility
The cited Build 42 reference notes that eight commands ship without in-game help text and three are disabled in that build. Consequently, a command may exist in a guide yet be unavailable on your server. Stable and Unstable branches can also diverge, and server-side mods may add, remove, or restrict commands.
Build 42 multiplayer was released for stress testing. The developer specifically warns: “Please do not use debug during MP games. This will impact negatively on server performance.” Keep -debug off during multiplayer sessions, especially on a shared or public server, and follow the owner’s rules.
Fixes when a command fails
Nothing happens in a solo world
- Confirm that you are not trying to use a server slash command in a normal solo session.
- For local testing, exit the world, add
-debugin Steam’s Launch Options, restart, and use the overlay.
Nothing happens in multiplayer
- Check whether you entered the command in chat (with
/) or in the server console (usually without it). - Confirm the exact player name, including spaces and capitalization.
- Verify that your account has the required access level and capability.
- Check spelling, quotation marks, argument order, and item or skill identifiers.
- Run
/helpto see whether the command is enabled in this build. - Reconnect after an access-level change if the server has not refreshed your permissions.
It works on one server but not another
That difference is expected when servers use different Build 42 branches, mods, role capabilities, or command restrictions. Ask the owner which branch is running and which role is authorized. Do not grant yourself a higher role simply because a guide shows admin.
Debug causes lag or instability
Remove -debug, restart the game, and return to a clean test copy. Do not enable it during multiplayer. If a shared world was altered, tell the server owner immediately and restore the most recent known-good backup rather than continuing to experiment.
When managed server hosting makes sense
If you need a persistent world for several players, a managed Project Zomboid server can provide a web control panel, scheduled restarts, backups, and access management. Hosting does not bypass administrator permissions: you still need to assign roles and use commands supported by the installed Build 42 branch. Compare backup controls, branch switching, mod support, console access, and player limits before choosing a provider.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesA safe workflow for testing cheats
- Create or copy a disposable world.
- For solo testing, enable
-debugonly for that session. - For multiplayer, have the owner assign the narrowest role needed.
- Test one command with a small quantity or low horde count.
- Save, record what changed, and notify other players.
- Disable debug, remove temporary permissions, and restart before normal play.
This separation keeps local experimentation from being mistaken for server authorization and limits the damage when a command, mod, or unstable update behaves differently than expected.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
