HumanitZ Zombie Horde Events: Configuration & Strategy

HumanitZ Zombie Horde Events: Configuration & Strategy

Horde events are HumanitZ's central endgame challenge — scheduled or triggered zombie waves that converge on survivor positions with significantly higher density and aggression than standard ambient zombies. For server administrators, horde events are a powerful community engagement tool: a well-timed, well-scaled horde creates shared adrenaline moments that keep players logging in. A poorly configured horde wipes new players and kills server population. This guide covers the full configuration and practical advice for striking the right balance.

Horde Event Settings in GameServerSettings.ini

[HordeSettings]
# Enable scheduled horde night events
HordeNightEnabled=true

# In-game hour when horde night begins (0-23)
HordeStartHour=22

# In-game hour when horde night ends
HordeEndHour=5

# How many in-game days between horde nights
HordeFrequencyDays=1          ; 1 = every night | 3 = every 3 nights

# Multiplier on zombie count during horde (1.0 = standard, 2.0 = double)
HordeZombieMultiplier=2.0

# Speed boost applied to zombies during horde night
HordeSpeedMultiplier=1.3      ; 1.3 = 30% faster than normal

# Maximum additional zombies spawned during horde (adds to world cap)
MaxHordeZombies=200

# Enable special/rare zombie types during horde (screamers, tanks)
HordeSpecialZombiesEnabled=true
HordeSpecialZombieChance=0.05  ; 5% chance per horde zombie to be a special type

Noise-Triggered Horde Settings

[HordeSettings]
# Enable noise-triggered hordes (separate from scheduled horde night)
NoiseTriggerHordeEnabled=true

# Noise level (0.0–1.0) required to trigger a horde
# 0.3 = gunshots trigger hordes | 0.6 = only sustained noise triggers
NoiseTriggerThreshold=0.4

# Cooldown between noise-triggered hordes (seconds)
NoiseTriggerCooldown=600      ; 10-minute cooldown prevents constant waves

# Size of noise-triggered horde (fraction of MaxHordeZombies)
NoiseTriggerHordeSize=0.4     ; 40% of max horde size

Balancing Horde Difficulty by Server Type

🟢 New Player Friendly / Casual PvE

[HordeSettings]
HordeNightEnabled=true
HordeFrequencyDays=3          ; Every 3 nights gives time to prepare
HordeZombieMultiplier=1.3
HordeSpeedMultiplier=1.1
MaxHordeZombies=80
HordeSpecialZombiesEnabled=false
NoiseTriggerHordeEnabled=false

🟡 Balanced Community Server

[HordeSettings]
HordeNightEnabled=true
HordeFrequencyDays=1
HordeZombieMultiplier=1.8
HordeSpeedMultiplier=1.25
MaxHordeZombies=150
HordeSpecialZombiesEnabled=true
HordeSpecialZombieChance=0.04
NoiseTriggerHordeEnabled=true
NoiseTriggerThreshold=0.5
NoiseTriggerCooldown=900

🔴 Hardcore / Max Difficulty

[HordeSettings]
HordeNightEnabled=true
HordeFrequencyDays=1
HordeZombieMultiplier=3.0
HordeSpeedMultiplier=1.5
MaxHordeZombies=300
HordeSpecialZombiesEnabled=true
HordeSpecialZombieChance=0.10
NoiseTriggerHordeEnabled=true
NoiseTriggerThreshold=0.2     ; Even whisper-quiet play triggers hordes
NoiseTriggerCooldown=300

Admin-Triggered Hordes (Manual Events)

Admins can trigger a horde manually at any time, useful for organised community events:

# In-game chat (after /AdminAccess [password]):
/triggerhorde              — Starts a horde targeting current player noise sources
/triggerhorde 3.0          — Starts a horde at 3× multiplier
/stophorde                 — Immediately disperses an active horde

Server Performance During Hordes

Horde events dramatically spike CPU usage as hundreds of additional zombies enter active pathfinding simultaneously. Prepare your server:

• Set MaxHordeZombies to no more than 1.5× your server's comfortable idle zombie cap
• Schedule hordes during times when player count is moderate — a maximum horde with 40 players is significantly more CPU-intensive than with 10
• After a horde ends, the server briefly spikes during garbage collection as dead zombie entities are removed. This is normal; a brief lag spike lasting 1–2 seconds post-horde is expected

Using Hordes as a Community Tool

Regular horde nights are one of the most effective retention mechanics for HumanitZ communities. Best practices:

• Post the horde night schedule in your Discord so players plan around it
• Consider hosting special "mega horde" events with /triggerhorde 5.0 as organised community challenges with Discord voice coordination
• Reduce horde frequency on weekdays (every 3 nights) and increase on weekends (every night) to match your player population patterns
• Give in-game warning to players 30 minutes before horde night via the MOTD or admin broadcast so they return to their base in time

Professional Hosting

Keep your server rock-solid through the most intense horde nights. Host your HumanitZ server with Supercraft on hardware that handles peak zombie AI loads without dropping frames for your players.