7 Days to Die serverconfig.xml gerador

7 Days to Die utiliza XML, o que significa que é o único config aqui que vai recusar-se a carregar sobre um único carácter extraviado - geralmente um que está no teu nome do servidor.

Começar com um preset

Definições Visuais

Formato xml
Identity

Name in the server browser. An ampersand here must be escaped — an unescaped one breaks the whole XML file and the server falls back to defaults.

Short description in the browser.

Website link shown with the server.

Base port. The game uses TCP here and UDP on this port plus the two above it.

Gameplay

0 is easiest, 5 hardest. Affects damage dealt and taken.

Real minutes per in-game day.

In-game hours of daylight per day.

Experience rate as a percentage, not a multiplier — 100 is normal.

0 nothing, 1 everything, 2 toolbelt only, 3 backpack only.

Days between Blood Moons. 0 disables them entirely.

Loot quantity as a percentage.

Days before containers refill. 0 disables loot respawn.

World

Navezgane for the hand-built map, or RWG for a random world generated from the seed below.

Seed for random world generation. Only used when GameWorld is RWG.

Random world size. Larger maps take much longer to generate and use considerably more memory.

Save name. Changing it starts a fresh save rather than renaming the existing one.

Land claim blocks per player.

Size in blocks of the protected area around a claim.

Players & Access

Join password.

Slot limit.

Slots held back for players with the required permission level.

Performance

Zombies per player during a Blood Moon. This sets your server's peak load — it is the number to lower if horde night causes trouble.

Server-wide zombie cap. One of the strongest performance levers here.

Server-wide animal cap.

Caps how far clients may render, which limits how much the server must stream.

Network

2 is public, 1 friends only, 0 hidden and joinable by address.

RCON & Query

Telnet console. Also what external tools use to read the player list, since the standard query does not provide names.

Telnet port. Never expose it publicly without a password.

Telnet password. An empty password with telnet enabled is an open console.

Built-in web dashboard.

Web dashboard port.

serverconfig.xml

<?xml version="1.0"?>
<ServerSettings>
  <property name="ServerName" value="Spawnly 7DTD"/>
  <property name="ServerDescription" value="Survive the horde"/>
  <property name="ServerWebsiteURL" value=""/>
  <property name="ServerPort" value="26900"/>
  <property name="ServerVisibility" value="2"/>
  <property name="ServerPassword" value=""/>
  <property name="ServerMaxPlayerCount" value="8"/>
  <property name="ServerReservedSlots" value="0"/>
  <property name="GameWorld" value="Navezgane"/>
  <property name="WorldGenSeed" value=""/>
  <property name="WorldGenSize" value="6144"/>
  <property name="GameName" value="SpawnlyWorld"/>
  <property name="GameDifficulty" value="2"/>
  <property name="DayNightLength" value="60"/>
  <property name="DayLightLength" value="18"/>
  <property name="XPMultiplier" value="100"/>
  <property name="DropOnDeath" value="1"/>
  <property name="BloodMoonFrequency" value="7"/>
  <property name="BloodMoonEnemyCount" value="8"/>
  <property name="MaxSpawnedZombies" value="64"/>
  <property name="MaxSpawnedAnimals" value="50"/>
  <property name="ServerMaxAllowedViewDistance" value="12"/>
  <property name="LootAbundance" value="100"/>
  <property name="LootRespawnDays" value="30"/>
  <property name="LandClaimCount" value="3"/>
  <property name="LandClaimSize" value="41"/>
  <property name="TelnetEnabled" value="false"/>
  <property name="TelnetPort" value="8081"/>
  <property name="TelnetPassword" value=""/>
  <property name="WebDashboardEnabled" value="false"/>
  <property name="WebDashboardPort" value="8080"/>
</ServerSettings>

Como funciona a sintaxe do serverconfig.xml

Cada definição é um elemento de propriedade com um nome e um atributo de valor. Como é um verdadeiro XML, os caracteres que têm significado em XML não podem aparecer literalmente nos teus valores: uma ampersand num nome do servidor tem que ser escrita como a sua sequência de escape, e também as aspas e os ângulos dentro dos valores entre aspas. Este gerador escapa-os para ti.

O erro que custa horas às pessoas

Uma ampersand não escapada não produz um erro útil. O analisador XML falha, o servidor recua para os seus padrões incorporados e obténs um servidor a funcionar sem nenhuma das tuas definições e sem nenhuma explicação óbvia. Se nada do que configuraste se aplicou, procura pontuação no teu nome do servidor primeiro.

Suporte e Ajuda