Stack composer

Started from RDCH DeV: the 18 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 GameLabs
3 VPPAdminTools
4 RaG_Core
5 DayZ-Expansion-Core
6 Dabs Framework
7 RDCH Core not analyzed
8 Code Lock
9 BaseBuildingPlus
10 SHOTSx3_Universal_130_Compat not analyzed
11 RaG_BaseItems
12 Forward Operator Gear
13 SNAFU Weapons
14 RDCH Admin Gear not analyzed
15 DayZ-Expansion-Book
16 DayZ-Expansion-Groups
17 RDCH KillGuard not analyzed
18 RDCH Sibnic Helicopters (Community Repack) not analyzed

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

Stall risks

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

Mods silencing mods

4 conflicts

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

Structural load

0.35% of a frame at 100 players

3.517 ms per second, all 13 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.

4 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 →	1CF	4RaG_Core	5DayZ-Expansion-Core	all
5DayZ-Expansion-Core	1DayZ-Expansion-Core silences CF 1 method: 1 value	2DayZ-Expansion-Core silences RaG_Core 2 methods: 2 checks		3
11RaG_BaseItems			1RaG_BaseItems silences DayZ-Expansion-Core 1 method: 1 check	1
all	1	2	1	4
7RDCH Core	Not analyzed, so what it silences is unknown. Queue it in the list above.
10SHOTSx3_Universal_130_Compat	Not analyzed, so what it silences is unknown. Queue it in the list above.
14RDCH Admin Gear	Not analyzed, so what it silences is unknown. Queue it in the list above.
17RDCH KillGuard	Not analyzed, so what it silences is unknown. Queue it in the list above.
18RDCH Sibnic Helicopters (Community Repack)	Not analyzed, so what it silences is unknown. Queue it in the list above.

The 3 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

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

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

NotificationSystem.GetNotificationData — Dabs Framework silences CF
NotificationSystem.GetNotificationData — Dabs Framework silences DayZ-Expansion-Core
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 VPPAdminTools then GameLabs then CF then vanilla

DayZGame.OnRPC

per event

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

PlayerBase.SetActions

per event

RaG_BaseItems then BaseBuildingPlus then DayZ-Expansion-Core then VPPAdminTools then vanilla

PlayerBase.OnRPC

per event

BaseBuildingPlus then RaG_Core then VPPAdminTools then vanilla

ActionAttachToConstruction.ActionCondition

per event

BaseBuildingPlus sometimes stops here then RaG_Core sometimes stops here then vanilla

ActionBuildPart.ActionCondition

per event

BaseBuildingPlus sometimes stops here then DayZ-Expansion-Core sometimes stops here then vanilla

ActionCloseFence.ActionCondition

per event

BaseBuildingPlus sometimes stops here then Code Lock then vanilla

ActionPackTent.ActionCondition

per event

Code Lock then DayZ-Expansion-Core sometimes stops here then vanilla

ActionTogglePlaceObject.ActionCondition

per event

BaseBuildingPlus sometimes stops here then DayZ-Expansion-Core sometimes stops here then vanilla

ActionUnmountBarbedWire.ActionCondition

per event

BaseBuildingPlus sometimes stops here then DayZ-Expansion-Core sometimes stops here then vanilla

AnimalBase.EEHitBy

per event

DayZ-Expansion-Core then GameLabs then vanilla

CarScript.EEHitBy

per event

RaG_Core then GameLabs then vanilla

Stall risks#

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

GameLabs

PlayerBase.OnScheduledTick

about 30× per player per second