Menu
 

HumanitZ Zombie Horde Events: Configuration & Strategy

HumanitZ Zombie Horde Events: Configuration & Strategy

Besides the zombies that roam the map, HumanitZ sends events at the players: groups of zombies, or human bandits, that raid your location. For a server admin these events are a strong community tool. A well-timed raid gives a group a shared fight to talk about; a raid that is too strong for a new server wipes the newcomers and empties it.

This page covers the settings and commands that actually control events, taken from REF_GameServerSettings.ini and RCONCommands.txt, the reference files shipped with the dedicated server, checked against the 1.1A build of 20 October 2026. HumanitZ has no scheduled horde night, no noise threshold and no [HordeSettings] section: guides that show those describe settings the server does not read.

🧟 Raid Events

The game spawns zombie or bandit events that target player locations. One setting, AIEvent, decides how often.

📻 Admin Events

Over RCON an admin can send a zombie or bandit event at any player, with a power value that sets how many come and of what types.

Event Frequency

[World Settings]
; How often the game spawns zombie or human raids on your location:
; 0 = disabled, 1 = low, 2 = default, 3 = high, 4 = insane.
AIEvent=2

The server confirms the value in its log at start, as AI event set to Default for 2. Set 0 for a builder server where raids are unwelcome, and 3 or 4 for a group that wants constant pressure.

Days Passed Drives the Events

The RCON reference states that the number of game days passed controls zombie events. An admin can set that counter:

setdayspassed 30      ; set the world's day count, which the game uses for zombie events

Use it with care: it changes event behaviour for the whole server at once, and the reference does not spell out the scale. Change it in small steps and watch the next few events.

Triggering an Event Yourself

Events can be sent over RCON, which makes them the tool for organised community nights:

eventzombie 76561198012345678 5    ; zombie event that targets all players
eventbandit 76561198012345678 5    ; the same with bandits
settime 2300                       ; set the time, here 11 pm, for a night fight

The first argument is a player's Steam ID, which the RCON command Players lists. The second is the power, which controls how many zombies come and which types. Start low on a new server and raise it event by event.

There is no chat command that starts or stops a horde. To end a fight that went wrong, the RCON command suspendspawners true despawns all AI and pauses the spawners; suspendspawners false resumes normal spawning.

Settings That Shape Every Fight

[World Settings]
; Zombie difficulty: 0 very easy, 1 easy, 2 default, 3 hard, 4 very hard, 5 nightmare.
ZombieDiffHealth=1
ZombieDiffSpeed=2
ZombieDiffDamage=3
; 2 = twice as many zombies, 0.5 = half.
ZombieAmountMulti=1
; Zombie dogs appear mainly at night.
ZombieDogMulti=1
; Minutes before zombies respawn. 0 disables respawning.
ZombieRespawnTimer=90
; Added in 1.1: zeeks only die from a headshot or a destroyed brain.
HeadshotOnlyMode=false
; Day and night length in real minutes.
DayDur=40
NightDur=20

Balancing by Server Type

🟢 New Player Friendly / Casual PvE

[World Settings]
AIEvent=1
ZombieDiffSpeed=1
ZombieAmountMulti=0.8
ZombieDogMulti=0.5

🟡 Balanced Community Server

[World Settings]
AIEvent=2
ZombieDiffSpeed=2
ZombieAmountMulti=1
ZombieDogMulti=1

🔴 Hardcore / Max Difficulty

[World Settings]
AIEvent=4
ZombieDiffHealth=3
ZombieDiffSpeed=3
ZombieAmountMulti=1.5
ZombieDogMulti=1.5
HeadshotOnlyMode=true
NightDur=30

Server Performance During Events

An event adds AI on top of the zombies already roaming, and AI is the main CPU cost of a HumanitZ server. A high AIEvent level together with a raised ZombieAmountMulti stacks both. Raise one at a time and watch CPU during the next event. The performance guide covers the population settings in detail.

Using Events as a Community Tool

  • Announce admin events in your Discord so players can plan to be online.
  • Pair settime 2300 with eventzombie for a night raid, then let the normal cycle resume.
  • Use the RCON command admin to broadcast a warning to everyone a few minutes before you start.
  • Keep AIEvent moderate on weekdays and run the big fights as announced weekend events.

New Server Tip: start the first week at AIEvent=1 or 2 and run admin events with a low power value. A crushing early raid can empty a new server before its community forms.

Professional Hosting

On Supercraft AIEvent, the zombie difficulty settings and headshot-only mode are fields in the server's configuration screen. RCON is enabled on every HumanitZ server, and its port and password are in GameServerSettings.ini in the file manager's Config folder. Host your HumanitZ server with Supercraft on hardware that holds up through the big fights.

Tired of fighting this issue every patch?

Run a managed Humanitz server with us. We handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in minutes, multiple datacenter regions, no contract.

See Humanitz hosting plans →
Top