Stack composer

Started from TitanUS2|Nasdara|Tappers|Modded|: the 22 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 of 22 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

1 conflict

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

Structural load

0.40% of a frame at 100 players

3.968 ms per second, all 21 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.

The one pair#

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

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 GameLabs then DayZ-Expansion-Core sometimes stops here then CF then vanilla

ItemBase.EEItemLocationChanged

every inventory move

GameLabs then DayZ-Expansion-Market sometimes stops here then vanilla

PlayerBase.SetActions

per event

Titan Vehicles then BS KeyRoom then VPPAdminTools then MuchCarKey then DayZ-Expansion-Market then DayZ-Expansion-Core then BaseBuildingPlus then vanilla

DayZGame.OnRPC

per event

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

ActionPushObject.ActionCondition

per event

MuchCarKey sometimes stops here then FlipTransport then DayZ-Expansion-Core sometimes stops here then vanilla

ActionBuildPart.ActionCondition

per event

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

ActionCloseFence.ActionCondition

per event

BaseBuildingPlus sometimes stops here then Code Lock then vanilla

ActionCoverHeadTarget.ActionCondition

per event

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

ActionForceConsume.ActionCondition

per event

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

ActionForceConsumeSingle.ActionCondition

per event

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

ActionGagTarget.ActionCondition

per event

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

ActionHandcuffTarget.ActionCondition

per event

DayZ-Expansion-Market sometimes stops here then DayZ-Expansion-Core sometimes stops here 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.

DayZ-Expansion-Core

DayZPlayerImplement.CommandHandler

about 30× per player per second