In Version 3.0, difficulty choices in 7 Days to Die are handled as Sandbox presets rather than the older six-name difficulty scale. Choose or edit a preset from the New Game or load-game settings, then tune combat, time, loot, death, spawning, airdrops and Blood Moon rules independently. For a seven-day challenge, change one setting at a time, keep a written record of the values or code, and treat Game Stage, Loot Stage, XP and loot abundance as separate systems.
Prefer not to run the server on your own PC? Godlike.Host offers hosted 7 Days to Die servers with free DDoS protection and up to three free backups a day.
What changed: difficulty names versus Sandbox presets
The familiar difficulty ladder—Scavenger, Adventurer, Nomad, Warrior, Survivalist and Insane—still appears in older guides and may remain visible in some installations. Official documentation says difficulty settings were converted to Sandbox presets in Version 3.0. That means the labels and the way a preset is represented can differ between builds. A code copied from an older guide may not match the format accepted by your current game.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
7 Days to Die – Console Edition Survival Bundle - PlayStation 5 | $47.00 | Buy on Amazon |
| 2 |
|
7 Days to Die – Console Edition - Xbox Series X | $44.99 | Buy on Amazon |
| 3 |
|
7 Days to Die (PS4) | $23.01 | Buy on Amazon |
| 4 |
|
7 Days to Die - PlayStation 4 | $36.21 | Buy on Amazon |
| 5 |
|
7 Days to Die - Xbox One (Renewed) | $39.07 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Use the labels as historical vocabulary, not as a promise that every current menu has those exact entries. Before applying a code, open the relevant settings screen and confirm the labels, preset names and code format shown by your installed build. If a guide and your menu disagree, the installed build is the authority.
What a preset actually controls
Difficulty is primarily a combat-pressure choice: the documented difficulty axis changes enemy strength. It is not a single master switch for every progression system. The game exposes separate controls for player and AI block damage, loot abundance, loot respawn, time, death consequences, Blood Moon behavior, spawning, airdrops, map markers and cheat access.
#1 Best Overall
- Explore – Huge, rich environments, with unique biomes and worlds up to 100 square kilometres in size.
- Craft – Handcraft and repair weapons, clothes, armour, tools, vehicles, with hundreds of recipes and schematics.
- Build – Design your fort with traps, electricity, auto turrets, and gadgets to survive in a fully destructible and mouldable world.
- Cooperate or Compete – Work together to build settlements or against each other in a wasteland where zombies and outlaws rule the land.
- A must-have for collectors and fans of Open-World Survival Horror, the 7 Days to Die – Console Edition Survival Bundle includes the following: An exclusive Artbook with over 100 pages showcasing never-before-seen illustrations of the zombie apocalypse, a CD featuring the haunting Original Soundtrack (OST) of the game, a double-sided poster, Fine art prints x3, Sticker sheets x 3, the physical game, and a collectible tuck-in box housing all the contents.
A useful way to think about a Sandbox preset is as a starting bundle of values. You can accept it, then adjust individual values to fit a solo world, a co-op group or a deliberate challenge. Record the final values rather than relying only on the preset name.
Where to enter a Sandbox code or edit a preset
Settings are selected from the main menu before the world loads. The exact labels can move between versions, but the documented workflow is the same: start a new game or select an existing game, open its Game Settings panels, choose the world and preset, and review the individual controls before launching.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Open the main menu. Choose New Game for a new seven-day run, or select the saved game you want to configure and choose its load/settings option.
- Select the world and game mode. Keep the map and other core choices stable if you are trying to learn how a setting affects the first week.
- Open the Game Settings panels. Locate the current difficulty/Sandbox preset control and any field for a Sandbox code in your build.
- Enter or select the preset. If your version accepts a code, enter it exactly as displayed or supplied. Do not assume that a code from a different version uses the same syntax.
- Audit the individual values. Review difficulty, 24-hour cycle length, daylight length, player and AI block damage, loot abundance, loot respawn, death penalty, drop-on-death, Blood Moon count, enemy spawning, airdrops, cheat mode and map markers.
- Launch only after recording the configuration. A screenshot or written list of values lets a co-op group reproduce the challenge and lets you identify which change caused a later result.
Game Mode documentation confirms that difficulty and settings can be changed from the main menu before loading. For a world already in progress, availability of each setting can depend on the installed version and whether the world is local or server-hosted; check the actual panel instead of assuming every option is editable.
Choosing a starting difficulty for the first seven days
If the group is learning the game, start with Adventurer or the equivalent current Sandbox preset documented as the default. It supplies a reference point without requiring you to guess how an extreme setting changes the opening. Experienced players can start higher, but the same rule applies: preserve the map and core settings so you can distinguish a difficulty effect from a world-generation or timing effect.
| Legacy label | Historical position | How to treat it in Version 3.0 |
|---|---|---|
| Scavenger | Easiest | Legacy name; verify whether your build exposes it or maps it to a Sandbox preset. |
| Adventurer | Default in the documented Game Mode material | Use as a baseline only after confirming the current preset label. |
| Nomad | Intermediate | Legacy name; do not assume its current code or exact values. |
| Warrior | Harder | Legacy name; inspect the actual preset values. |
| Survivalist | Very hard | Legacy name; verify current availability and code format. |
| Insane | Hardest | Legacy name; use only when the current build confirms the corresponding preset. |
The table describes the historical ordering, not a current Version 3.0 code list. Difficulty changes enemy strength; it does not, by itself, determine how much loot you find, how quickly you level or how large the first Blood Moon becomes.
A practical seven-day setup
The goal of a first-week configuration is not to make every outcome predictable. It is to control the major pressures while leaving enough consistency to learn from each day. Adjust one axis at a time and write down the value before and after the change.
Rank #2
- Explore – Huge, rich environments, with unique biomes and worlds up to 100 square kilometres in size.
- Craft – Handcraft and repair weapons, clothes, armour, tools, vehicles, with hundreds of recipes and schematics.
- Build – Design your fort with traps, electricity, auto turrets, and gadgets to survive in a fully destructible and mouldable world.
- Cooperate or Compete – Work together to build settlements or against each other in a wasteland where zombies and outlaws rule the land.
- Farm or Hunt – Plant gardens for sustainable resources or head out to the wilderness and hunt over a dozen unique animals.
Before Day 1: establish a baseline
- Select the world and a baseline preset, such as Adventurer or its current equivalent.
- Keep the map, core game mode and other foundational choices unchanged for the run.
- Decide whether the run is meant to preserve normal achievements. If so, leave cheat mode and Creative/Debug access disabled.
- Record the preset name, code if one is shown, and every custom value you changed.
This baseline matters because changing difficulty, XP and loot simultaneously makes the first week impossible to diagnose. If the opening feels too easy or too hard, you want one identifiable cause.
Days 1–2: reduce an immediate combat or supply problem
If the opening is too punishing, change one variable: player damage, enemy damage or loot abundance. Player and AI block-damage controls affect how quickly characters and enemies damage blocks; combat difficulty and block damage are related pressures but are not interchangeable. Loot abundance changes the supply available in containers, not the enemy progression calculation.
Do not raise XP and loot abundance together during this test. XP changes the speed of level-based progression, while loot abundance changes the availability of items. Separating them tells you whether the problem is character power or material supply.
Days 3–4: tune time and the supply loop
Use the 24-hour cycle length and daylight length to change time pressure. Longer days provide more time for building and exploration before darkness; a different daylight length changes how that time is distributed. Airdrop frequency and loot-respawn interval affect how often supplies re-enter the world. None of these settings guarantees a particular level, quest pace or stockpile by Day 7.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →- Need more building time? Increase the practical length of the day rather than changing several combat values at once.
- Running out of supplies? Examine loot abundance and the respawn interval separately.
- Want a faster resupply loop? Shorter respawn intervals increase container refresh opportunities, but they do not replace progression or exploration.
- Want more information between trips? Review airdrop frequency and map-marker settings independently.
Days 5–6: prepare for the first Blood Moon
Check Blood Moon count, enemy spawning, AI Blood Moon block damage and the death/drop rules before the event. Lowering the horde count or reducing its structural damage directly changes the event. Drop-on-death and the selected death penalty change what a failed defense costs, so decide those rules before you build your fallback plan.
XP deserves special attention here. A higher XP multiplier can move a player toward a higher Game Stage sooner. That can increase the pressure of the event even when the named difficulty is unchanged. If you want a gentler first horde, changing the Blood Moon controls or combat damage is more direct than assuming that extra loot will compensate.
Rank #3
- Unlimited hours of gameplay
- Explore - Huge, unique and rich environments, offering the freedom to play the game however you want
- Craft - craft and repair weapons, clothes, armour, tools, vehicles, and more
- Build - Take over a ruin, or build from the ground-up. Design your fortress to include traps and defensive positions to survive the undead
- Cooperate or Compete - Includes two player split screen mode, with support for up to 4 players online, in Player versus Player, co-op survival, or co-op creative modes
Day 7: record the result before changing anything
After the first Blood Moon, write down the final preset/code and each custom value. Note the 24-hour cycle, daylight, loot and respawn values, XP multiplier if applicable, death and drop rules, Blood Moon settings and whether cheat or Creative access was enabled. For a shared challenge, save a copy of this list before experimenting with a new configuration.
Game Stage, Loot Stage and XP are different systems
Game Stage is a calculated value representing progression and survival skill. It is based on player level and adjusted days alive, and it controls the size and composition of sleeper, screamer/scout, special-purpose and Blood Moon hordes.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Loot uses a separate variable called Loot Stage. Loot is not controlled by Game Stage. A high loot setting can increase supply availability without making hordes weaker, and a high Game Stage can increase enemy pressure without guaranteeing better container contents.
| Setting or value | What it changes | What it does not establish |
|---|---|---|
| Difficulty/Sandbox preset | Enemy-strength pressure and the bundled starting values defined by the preset. | It does not, by itself, determine Game Stage or Loot Stage. |
| XP multiplier | How quickly level-based progression is reached. | It does not directly increase container loot. |
| Loot abundance | Supply availability in loot containers. | It does not make Blood Moon enemies weaker. |
| Loot respawn | How often containers can refresh under the game’s rules. | It does not set player level or Game Stage. |
| Player/AI damage values | Combat and block-damage pressure. | They do not define the loot table. |
| Blood Moon controls | Event timing, count and structural pressure. | They do not replace the underlying Game Stage calculation. |
This separation explains several common surprises. Increasing loot does not automatically make the first horde easier. Increasing XP can make the first horde arrive with a stronger Game Stage sooner. Lowering a named difficulty does not necessarily slow level progression or alter container quality.
Changing settings after a world has started
The main-menu Game Settings workflow is the documented route for changing difficulty and related options before loading. Whether a particular value can be changed safely after a world exists depends on the installed build and hosting mode. If the setting is exposed in the load-game panel, change one value, load the world, and verify the result. If it is absent, do not assume that editing an unrelated file or applying an old code will work.
For a fair seven-day challenge, treat a mid-run change as part of the rules. Record the day, the old value and the new value. In co-op, tell every player before loading so nobody mistakes a changed death rule or Blood Moon count for a gameplay bug.
Rank #4
- Explore & Craft - Huge, unique and rich environments, offering the freedom to play the game any way you want while you craft and repair weapons, clothes, armor, tools, vehicles, and more.
- Build - Take over a ruin, or build from the ground-up. Design your fortress to include traps and defensive positions to survive the undead - the world is fully destructible and moldable.
- Cooperate or Compete - Includes two player split screen mode, with additional online multiplayer modes and features to be revealed in the near future.
- Create - Unleash your creativity and build the ultimate world by yourself friends. Enjoy unlimited access to nearly 400 in-game items and 1,200 unique building blocks in creative mode.
- Improve - Increase your skills in a multitude of active and passive disciplines. 7 to Die is the only true survival RPG with nearly 50 multi-tiered skill and perk groups.
Dedicated-server settings and administration
Dedicated servers expose a configuration route in addition to the client menus. The documented server configuration reference includes these properties:
| Property | Purpose |
|---|---|
GameDifficulty |
Difficulty value; the cited reference uses a 0–5 range. |
BlockDamagePlayer |
Player block-damage setting. |
BlockDamageAI |
AI block-damage setting. |
BlockDamageAIBM |
AI Blood Moon block-damage setting. |
XPMultiplier |
Experience gain multiplier. |
DayNightLength |
Length of the full day/night cycle. |
DayLightLength |
Length of daylight within the cycle. |
DropOnDeath |
What is dropped on player death, according to the server’s accepted values. |
BuildCreate |
Build/creation access control in the server configuration. |
The reference’s field names and ranges are version-sensitive. Version changes can move settings between server configuration and newer preset or code systems, so validate the active build before editing a template.
A safe server-change procedure
- Stop the server cleanly and keep a backup of the active configuration.
- Confirm the game/server version and compare the available property names with the current configuration reference for that version.
- Change one property or one tightly related group, such as the three block-damage values.
- Start the server and verify the loaded values in-game or through the server’s available administration output.
- Tell connected players what changed and record the date, old value and new value.
Do not copy a GameDifficulty number into a newer preset/code field without checking the version. A numeric range documented for one server configuration format is not proof that the same number is accepted everywhere.
Using the command console
The in-game command console can retrieve game information and statistics, alter settings, spawn items and control time. Use the built-in help command first; it confirms the syntax supported by the installed build. Where supported, getgamestat (also abbreviated ggs) reports current game statistics.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches- Open the console using the key or control assigned by your platform and keyboard layout.
- Run
helpand read the command syntax shown by your build. - Use
getgamestatorggswhere supported to inspect current game information. - Make only the change you intend, then verify the result rather than chaining several commands.
- Close the console and record the command, value and in-game day for a reproducible configuration history.
Console syntax and permissions can differ between local games and dedicated servers. An older command example is not a guarantee that the same command, alias or parameter exists in your build.
Creative and achievement consequences
Creative access can bypass the normal looting loop. The Creative Menu documentation warns that enabling it when creating the world prevents achievements in that world. Keep Creative/Debug access for a separate test world, construction exercise or troubleshooting session if achievements and normal progression matter in the survival world.
Best Value
- Explore & Craft - Huge, unique and rich environments, offering the freedom to play the game any way you want while you craft and repair weapons, clothes, armor, tools, vehicles, and more.
- Build - Take over a ruin, or build from the ground-up. Design your fortress to include traps and defensive positions to survive the undead - the world is fully destructible and moldable.
- Cooperate or Compete - Includes two player split screen mode, with additional online multiplayer modes and features to be revealed in the near future.
- Create - Unleash your creativity and build the ultimate world by yourself friends. Enjoy unlimited access to nearly 400 in-game items and 1,200 unique building blocks in creative mode.
- Improve - Increase your skills in a multitude of active and passive disciplines. 7 to Die is the only true survival RPG with nearly 50 multi-tiered skill and perk groups.
- Survival challenge: leave cheat mode and Creative/Debug disabled from world creation.
- Base-design test: create a separate world so unrestricted building does not contaminate the challenge rules.
- Troubleshooting: reproduce the problem in the test world, then return to the recorded survival configuration.
Troubleshooting common preset and difficulty problems
The old six difficulty names are missing
This is expected if your build uses Version 3.0’s Sandbox terminology. Look for the current preset controls and verify the code format displayed by the game. Do not infer that a missing legacy label means the difficulty system has disappeared.
A code is rejected or produces unexpected values
Check the game version, capitalization and every character in the code. Compare the result with the individual settings panel. Codes and labels are version-sensitive; a code made for an older build may not map cleanly to a current preset system.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchMore loot did not make the horde easier
That behavior is consistent with the separate systems. Loot abundance and Loot Stage affect supply, while Game Stage and Blood Moon settings govern enemy pressure. Adjust the Blood Moon count, damage or spawning controls if the event itself is the problem.
The first Blood Moon became harder after increasing XP
XP can move a player toward a higher Game Stage sooner. Because Game Stage controls horde size and composition, the event may intensify even though the difficulty preset is unchanged. Test XP separately from combat and loot settings.
Players disagree about what changed
Compare the written preset/code, the individual Game Settings values and the server configuration. Record changes by in-game day and make one adjustment at a time. On a dedicated server, confirm that the server—not only a client menu—loaded the new value.
Quick Recap
A compact decision framework
- New player or mixed-skill group: choose Adventurer or the current default-equivalent Sandbox preset, then leave most values unchanged through Day 1.
- Combat is the problem: change player/enemy damage or Blood Moon controls, not loot abundance.
- Time is the problem: adjust the 24-hour cycle and daylight length.
- Supplies are the problem: adjust loot abundance or respawn separately and keep XP constant.
- The first horde arrives too strong: inspect XP, Game Stage and Blood Moon settings before lowering every difficulty value.
- Achievements matter: avoid Creative/Debug access in the survival world.
- You administer a server: validate property names and ranges against the active version, back up the configuration and change one field at a time.
Seven-day configuration checklist
- Version and platform recorded.
- Current Sandbox preset name and code recorded, if shown.
- Map and core game mode fixed for the test.
- Difficulty, player damage and AI damage reviewed.
- 24-hour cycle and daylight length reviewed.
- Loot abundance and respawn interval reviewed independently.
- Death penalty and drop-on-death rules understood by every player.
- Blood Moon count, enemy spawning and AI Blood Moon block damage checked before Day 7.
- XP multiplier recorded because it can influence Game Stage timing.
- Creative/Debug status confirmed.
- Dedicated-server fields backed up and version-checked, if applicable.
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.
