Stack composer

Started from [EU] SurvivorZ | Nasdara | Hardcore-Survival | 1PP | PvP: the 24 mods it publishes to the Steam server browser (as of 2026-10-22), put back into load order — servers publish the list last-loaded first. Mods loaded with -servermod= are never published, so they are not here; add them if you know them.

Add a mod

Start from a live server

Your stack in load order, earliest first. Drag a row, or use the arrows, to reorder.

1 MBM_DuneBuggy not analyzed
2 TP_Apoc_Mustang not analyzed
3 Nasdara_VehicleFuelFix not analyzed
4 Nasdara_SunstrokeIcon not analyzed
5 SurvivorZ_Nasdara_Serverpack not analyzed
6 DayZ-Expansion-Licensed
7 DayZ-Expansion-Core
8 Dabs Framework
9 DayZ-Expansion-Vehicles
10 Terje Compatibility VPP not analyzed
11 Terje Start Screen not analyzed
12 Terje Medicine not analyzed
13 Terje Core not analyzed
14 Terje-Skills
15 Infected Horde Audio Limiter not analyzed
16 RaG_Infected_Hordes not analyzed
17 RaG_BaseItems
18 RaG_Core
19 RaG_BaseBuilding
20 InediaInfectedAI
21 CF
22 VPPAdminTools
23 GameLabs
24 KZ_MegaModDump not analyzed

12 of 24 mods not analyzed yet — left out of the composition below. Open a mod's page to request its analysis.

Stall risks

6 in hot hooks

File I/O on hot paths, timers created per event, and per-player-per-frame hooks across the stack. These can stall a frame regardless of the load figure. See all 6 below.

Mods silencing mods

3 conflicts

Across 108 server-side methods hooked by two or more mods. 2 more on client-only UI classes, listed separately.

Structural load

0.41% of a frame at 100 players

4.141 ms per second, all 12 mods combined. Hook dispatch and timers only — not what the hooks do inside. Methodology.

Who silences whom#

A later-loaded mod overrides a method without super(), so the earlier mod's code on that method — and vanilla's — never runs. Whether that is a bug or the whole point of the mod is the author's call; this shows the structure, not intent.

3 methods across 3 pairs. Read across: the mod on the left silences the mod at the top. Both in load order. 1 2–4 5–14 15+ methods

silences →	7DayZ-Expansion-Core	20InediaInfectedAI	all
17RaG_BaseItems	1RaG_BaseItems silences DayZ-Expansion-Core 1 method: 1 check		1
21CF	1CF silences DayZ-Expansion-Core 1 method: 1 value		1
22VPPAdminTools		1VPPAdminTools silences InediaInfectedAI 1 method: 1 event	1
all	2	1	3
1MBM_DuneBuggy	Not analyzed, so what it silences is unknown. Queue it in the list above.
2TP_Apoc_Mustang	Not analyzed, so what it silences is unknown. Queue it in the list above.
3Nasdara_VehicleFuelFix	Not analyzed, so what it silences is unknown. Queue it in the list above.
4Nasdara_SunstrokeIcon	Not analyzed, so what it silences is unknown. Queue it in the list above.
5SurvivorZ_Nasdara_Serverpack	Not analyzed, so what it silences is unknown. Queue it in the list above.
10Terje Compatibility VPP	Not analyzed, so what it silences is unknown. Queue it in the list above.
	…and 6 more mods not analyzed yet.

The 3 pairs, largest first# ·

CFsilencesDayZ-Expansion-Core1 method

NotificationRuntimeData.GetIcon value DayZ-Expansion-Core's value here is replaced. scripts.pbo::3_Game\CommunityFramework\Notification\NotificationRuntimeData.c:38

RaG_BaseItemssilencesDayZ-Expansion-Core1 method

PlantMaterial.CanPutAsAttachment check DayZ-Expansion-Core's conditions on this check no longer apply. For PlantMaterial instances, through its ancestor ItemBase. rag_baseitems_scripts.pbo::4_World\rag_baseitems_scripts\Modded\PlantMaterial.c:3

VPPAdminToolssilencesInediaInfectedAI1 method

SurvivorBase.EOnFrame event · T1 InediaInfectedAI's work on this event never runs. For SurvivorBase instances, through its ancestor PlayerBase. VPPAdminTools.pbo::4_World\VPPAdminTools\Entities\SurvivorBase.c:42

2 conflicts on client-only classes (menus, HUD, notifications) — no server effect

NotificationSystem.GetNotificationData — CF silences Dabs Framework
NotificationSystem.GetNotificationData — CF silences DayZ-Expansion-Core

Hot hooks shared across the stack#

The engine calls the last-loaded mod first; each super() hands on to the mod before it, ending at vanilla. Badges show what each mod's override calls inside — that body work, not the chain itself, is what costs frame time.

DayZGame.OnUpdate

every server frame

GameLabs then VPPAdminTools then CF then DayZ-Expansion-Core sometimes stops here then vanilla

PlayerBase.SetActions

per event

VPPAdminTools then InediaInfectedAI then RaG_BaseItems then Terje-Skills then DayZ-Expansion-Vehicles then DayZ-Expansion-Core then vanilla

AnimalBase.EEHitBy

per event

GameLabs then InediaInfectedAI sometimes stops here then Terje-Skills then DayZ-Expansion-Core then vanilla

DayZGame.OnRPC

per event

VPPAdminTools sometimes stops here then CF sometimes stops here then Dabs Framework then DayZ-Expansion-Core sometimes stops here then vanilla

PlayerBase.EEHitBy

per event

GameLabs then InediaInfectedAI sometimes stops here then Terje-Skills then DayZ-Expansion-Vehicles then vanilla

ZombieBase.EEHitBy

per event

GameLabs then InediaInfectedAI sometimes stops here then Terje-Skills then DayZ-Expansion-Core then vanilla

Hammer.SetActions

per event

RaG_BaseBuilding then RaG_Core then RaG_BaseItems then vanilla

PlayerBase.OnRPC

per event

VPPAdminTools then InediaInfectedAI then RaG_Core then vanilla

ActionForceConsume.ActionCondition

per event

InediaInfectedAI then DayZ-Expansion-Core then vanilla

ActionForceConsumeSingle.ActionCondition

per event

InediaInfectedAI then DayZ-Expansion-Core then vanilla

ActionGiveBloodTarget.ActionCondition

per event

InediaInfectedAI then DayZ-Expansion-Core then vanilla

ActionInjectTarget.ActionCondition

per event

InediaInfectedAI then DayZ-Expansion-Core then vanilla

Stall risks#

6 places where one mod's code can hold up a frame by itself, whatever the load figure says. Each is a pattern found in the code, not a measurement: how much it costs depends on what the hook does inside. Most severe first, then in load order.

Per-player, per-frame hook. Runs for every player on every tick, so whatever it does inside is multiplied by the population.

DayZ-Expansion-Core

DayZPlayerImplement.CommandHandler

about 30× per player per second