Project Zomboid Debug Mode and Admin Commands

Players search “Project Zomboid cheats,” “console commands,” and “admin panel” for the same two tools: Steam’s -debug launch flag for solo testing, and chat commands for dedicated-server staff. They are not the same system. Mixing them up is why a host types /godmode in a single-player world and nothing happens, or why a co-op friend enables debug and suddenly the whole save feels unfair.

This page is the Build 42 Early Access reference for both paths. It is a testing and hosting guide, not a permission slip to ruin a public server. Project Zomboid remains Early Access on Steam and GOG; command names can shift after a support update, so treat labels as directional and confirm them in your client after a hotfix such as 42.20.3.

Solo: enable debug from Steam

Debug is a launch option, not an in-game settings toggle.

1. In your Steam library, right-click Project Zomboid → Properties.
2. Open General → Launch Options.
3. Type -debug (include the hyphen).
4. Close the window and start the game normally.

A debug / developer overlay becomes available after you load a world. From there you can inspect tiles, spawn items, toggle god-like flags, and jump around a test map. Use this on a throwaway save. Debug is how creators verify sandbox settings, recipe changes after Build 42, and whether a generator actually wired. It is a poor way to “beat” a first week you wanted to learn.

To leave debug: delete -debug from Launch Options and restart. Leaving the flag on for a valued season invites accidental clicks and habit rot—you stop scouting loot routes because spawn-menu muscle memory took over.

GOG and non-Steam launches use the same idea: add -debug to the shortcut or launcher arguments. If the overlay never appears, you typed the flag on the wrong install or started from a desktop shortcut that ignores Steam properties.

What debug is for

Good uses:

• Confirm a sledgehammer destroy target on a copy of your base layout.
• Test radio presets and AEBS text without waiting for the top of the hour.
• Reproduce a crash or lighting bug to film for The Indie Stone, as 42.20.3 notes still request profiler clips for some out-of-memory cases.
• Teach a friend hotwire steps on a quiet lot before a real Louisville run.

Bad uses:

• Spawning a warehouse of guns on a hardcore permadeath character, then asking the wiki why the run “felt empty.”
• Enabling debug on a public server without the host’s written OK.
• Treating item IDs from a Build 41 spreadsheet as gospel—Build 42 renamed and split many items.

Multiplayer: chat commands, not a hidden console

There is no separate Quake-style console for most players. On a server you open chat (default T) and type a slash command. Rights come from access level, not from -debug.

Typical staff ladder (names can vary slightly by build):

• none — regular survivor.
• gm / overseer — limited tools on some hosts.
• moderator — kick, teleport help, chat control.
• admin — full item, time, weather, and ban tools.

A server owner grants rights with a command in the form /setaccesslevel "PlayerName" admin (quotes help when the name has spaces). Do this from the server console or an existing admin character. Never publish the host password in Discord screenshots.

Useful admin commands survivors actually ask for:

• /additem Base.Crowbar — spawn by item ID; wrong IDs silently fail or give the wrong object.
• /godmode / /invisible / /noclip — movement and damage flags for staff, not for hiding in PvP without a rule.
• /teleport / /teleportto — rescue a stuck player after a basement clip.
• /kickuser / /banuser — last resort after voice warnings.
• /save — force a world write before a host reboot.
• /servermsg — announce a restart so nobody is mid-helicopter on the street.
• Weather and time commands — use sparingly; sudden noon-to-midnight swings wreck agriculture and sleep schedules.

If a command does nothing, you are not admin, chat is bound to another key, or you are in single-player. Pair this page with Dedicated Servers and Servers and Co-op before you experiment on a season save.

Co-op etiquette

Agree in writing: is this a vanilla hardcore season, a builder sandbox, or a creative test map? Spawning nails for a community wall is different from spawning katanas. Pin the rule in the Discord topic the same way you pin the 42.20.3 build number. Admins who join when the server is full (a 42.20.3 host feature) should still announce themselves—silent godmode on a full box looks like a cheater.

Mods and debug

Workshop tools sometimes add extra spawn UIs. Those mods must match your mod list hash. A debug overlay plus an outdated cheat mod is a common crash cocktail after a stable hotfix. Disable extra admin mods first when you file a vanilla bug.

Common mistakes

• Putting -debug in the game’s in-game options instead of Steam launch options.
• Expecting /additem to work in solo without debug or a hosted local server.
• Spelling item IDs with spaces (sledge hammer) instead of Base.Sledgehammer.
• Leaving godmode on, then dying of boredom because nothing threatens the safehouse.
• Using debug to skip Getting Started and then blaming Build 42 for “being confusing.”

Debug and admin tools are power tools. They save hours when you are testing wiring, map clips, or staff rescue. They delete the game’s tension the moment you use them as a lifestyle. Keep -debug off your main character, keep admin chat logged, and go back to First Week Survival when you want the real Knox County loop.