Stack composer

Started from [UA] NIGHTMARE PvE test: the 33 mods it publishes to the Steam server browser (as of 2026-10-23), 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 Dabs Framework
3 NIGHTMARE not analyzed
4 NIGHTMARE_Dungeon_System not analyzed
5 GameLabs
6 Basic Map
7 DelaDuck's mods core module not analyzed
8 RaG_Core
9 TF SortZ - Fixed Edition not analyzed
10 MoonShining not analyzed
11 Buildings_from_Mihalych not analyzed
12 No Vehicle Damage Basic not analyzed
13 RaG_BaseBuilding
14 XZone STALKER Mutants
15 GK_PvZmoD_CustomisableZombies not analyzed
16 Map Assets - MutatedMods not analyzed
17 Hunter Mega Pack not analyzed
18 Paragon Storage
19 FC_Fish_Equip
20 Paragon Collectable items
21 Paragon Gear and Armor
22 Overlay Removal
23 DayZ-Expansion-Core
24 DayZ-Expansion-Chat
25 InventoryDump not analyzed
26 WindstridesClothingPack
27 BuilderItems
28 Trader
29 SNAFU Weapons
30 Search For Loot Improved not analyzed
31 Car Camera Controls by DelaDuck not analyzed
32 Workbench not analyzed
33 RZ_HPBAR not analyzed

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

Stall risks

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

Mods silencing mods

3 conflicts

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

Structural load

0.19% of a frame at 100 players

1.913 ms per second, all 18 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 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	8RaG_Core	all
23DayZ-Expansion-Core	1DayZ-Expansion-Core silences CF 1 method: 1 value	2DayZ-Expansion-Core silences RaG_Core 2 methods: 2 checks	3
all	1	2	3
3NIGHTMARE	Not analyzed, so what it silences is unknown. Queue it in the list above.
4NIGHTMARE_Dungeon_System	Not analyzed, so what it silences is unknown. Queue it in the list above.
7DelaDuck's mods core module	Not analyzed, so what it silences is unknown. Queue it in the list above.
9TF SortZ - Fixed Edition	Not analyzed, so what it silences is unknown. Queue it in the list above.
10MoonShining	Not analyzed, so what it silences is unknown. Queue it in the list above.
11Buildings_from_Mihalych	Not analyzed, so what it silences is unknown. Queue it in the list above.
	…and 9 more mods not analyzed yet.

The 2 pairs, largest first# ·

DayZ-Expansion-CoresilencesRaG_Core2 methods

Clothing.CanLoadItemIntoCargoClothingConditions check RaG_Core's conditions on this check no longer apply. 0_core_preload.pbo::4_World\Entities\ItemBase\Clothing.c:33 Clothing.CanReceiveItemIntoCargoClothingConditions check RaG_Core's conditions on this check no longer apply. 0_core_preload.pbo::4_World\Entities\ItemBase\Clothing.c:26

DayZ-Expansion-CoresilencesCF1 method

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

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

NotificationSystem.GetNotificationData — DayZ-Expansion-Core silences CF
NotificationSystem.GetNotificationData — DayZ-Expansion-Core silences Dabs Framework
InspectMenuNew.UpdateItemInfoLiquidType — DayZ-Expansion-Core silences RaG_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

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

MissionServer.OnUpdate

every server frame

Trader then CF then vanilla

PlayerBase.SetActions

per event

Trader then WindstridesClothingPack then DayZ-Expansion-Core then FC_Fish_Equip then vanilla

DayZGame.OnRPC

per event

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

Hammer.SetActions

per event

Paragon Storage then RaG_BaseBuilding then RaG_Core then vanilla

ActionCheckPulseTarget.ActionCondition

per event

Trader then DayZ-Expansion-Core then vanilla

ActionCollectBloodTarget.ActionCondition

per event