Stack composer

Started from [RU PVE Nasdara] GamersFamily: the 14 mods it publishes to the Steam server browser (as of 2026-10-20), 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.

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

Stall risks

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

Mods silencing mods

2 conflicts

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

Structural load

0.37% of a frame at 100 players

3.747 ms per second, all 11 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	3DayZ-Expansion-Core	all
3DayZ-Expansion-Core	1DayZ-Expansion-Core silences CF 1 method: 1 value		1
9RaG_BaseItems		1RaG_BaseItems silences DayZ-Expansion-Core 1 method: 1 check	1
all	1	1	2
12GF_MODPACK	Not analyzed, so what it silences is unknown. Queue it in the list above.
13GF_EQUIP_PACK	Not analyzed, so what it silences is unknown. Queue it in the list above.
14GF_CORE	Not analyzed, so what it silences is unknown. Queue it in the list above.

The 2 pairs, largest first# ·

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

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

2 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

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

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

MissionServer.OnUpdate

every server frame

TraderPlus then CF then vanilla

PlayerBase.EEItemDetached

every inventory move

WindstridesClothingPack then TraderPlus then vanilla

PlayerBase.SetActions

per event

WindstridesClothingPack then RaG_BaseItems then TraderPlus then VPPAdminTools then DayZ-Expansion-Core then vanilla

DayZGame.OnRPC

per event

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

ActionCollectBloodTarget.ActionCondition

per event