Stack composer

Started from The Burg: the 22 mods it publishes to the Steam server browser (as of 2026-10-19), 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 CF
2 Mecklenburg_2026 not analyzed
3 Dabs Framework
4 VPPAdminTools
5 DayZ-Expansion-Bundle
6 DayZ-Expansion-Licensed
7 UnlimitedALe not analyzed
8 DinkyItemsPlus
9 MB Cassette Albums not analyzed
10 Trader
11 Better HUD not analyzed
12 CarPack not analyzed
13 DayZ Motorsports Vehicle Overhaul not analyzed
14 NO FOG not analyzed
15 DigZ_SkeltonZ_ARMOR not analyzed
16 GoreZ
17 AJs Creatures V2 not analyzed
18 dbo_spiders
19 Buca Weapons not analyzed
20 DZNC_Zombies not analyzed
21 Zombie Kids 4.0 not analyzed
22 ZombieSpawnTool not analyzed

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

Stall risks

8 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 8 below.

Mods silencing mods

2 conflicts

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

Structural load

0.56% of a frame at 100 players

5.636 ms per second, all 9 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.

2 methods across 2 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 →	1CF	5DayZ-Expansion-Bundle	all
4VPPAdminTools		1VPPAdminTools silences DayZ-Expansion-Bundle 1 method: 1 event	1
5DayZ-Expansion-Bundle	1DayZ-Expansion-Bundle silences CF 1 method: 1 value		1
all	1	1	2
2Mecklenburg_2026	Not analyzed, so what it silences is unknown. Queue it in the list above.
7UnlimitedALe	Not analyzed, so what it silences is unknown. Queue it in the list above.
9MB Cassette Albums	Not analyzed, so what it silences is unknown. Queue it in the list above.
11Better HUD	Not analyzed, so what it silences is unknown. Queue it in the list above.
12CarPack	Not analyzed, so what it silences is unknown. Queue it in the list above.
13DayZ Motorsports Vehicle Overhaul	Not analyzed, so what it silences is unknown. Queue it in the list above.
	…and 7 more mods not analyzed yet.

The 2 pairs, largest first# ·

DayZ-Expansion-BundlesilencesCF1 method

NotificationRuntimeData.GetIcon value CF's value here is replaced. core_scripts.pbo::3_Game\DayZExpansion_Core\Client\Notifications\NotificationRuntimeData.c:29

VPPAdminToolssilencesDayZ-Expansion-Bundle1 method

SurvivorBase.EOnFrame event · T1 DayZ-Expansion-Bundle'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 — DayZ-Expansion-Bundle silences CF
NotificationSystem.GetNotificationData — DayZ-Expansion-Bundle silences Dabs Framework

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

DayZ-Expansion-Bundle sometimes stops here then VPPAdminTools then CF then vanilla

MissionServer.OnUpdate

every server frame

Trader then CF then vanilla

DayZGame.OnRPC

per event

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

PlayerBase.SetActions

per event

Trader then DayZ-Expansion-Bundle then VPPAdminTools then vanilla

ActionCheckPulseTarget.ActionCondition

per event

Trader then DayZ-Expansion-Bundle then vanilla

ActionCollectBloodTarget.ActionCondition

per event

Trader sometimes stops here then DayZ-Expansion-Bundle then vanilla

ActionDefibrilateTarget.ActionCondition

per event

Trader sometimes stops here then DayZ-Expansion-Bundle then vanilla

ActionDeployObject.ActionCondition

per event

Trader sometimes stops here then DayZ-Expansion-Bundle then vanilla

ActionDetach.ActionCondition

per event

Trader sometimes stops here then DayZ-Expansion-Bundle sometimes stops here then vanilla

ActionDisinfectTarget.ActionCondition

per event

Trader sometimes stops here then DayZ-Expansion-Bundle sometimes stops here then vanilla

ActionForceConsume.ActionCondition

per event

Trader sometimes stops here then DayZ-Expansion-Bundle sometimes stops here then vanilla

ActionForceConsumeSingle.ActionCondition

per event

Trader sometimes stops here then DayZ-Expansion-Bundle sometimes stops here then vanilla

Stall risks#

8 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.

VPPAdminTools

PlayerBase.CommandHandler

about 30× per player per second