Stack composer

Started from Barely Alive | PvP Zones | Trader | Helis | AirDrops | Keycards: the 30 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.

2 of 30 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 71 server-side methods hooked by two or more mods. 2 more on client-only UI classes, listed separately.

Structural load

0.39% of a frame at 100 players

3.889 ms per second, all 28 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#

VPPAdminToolssilencesInediaInfectedAI1 method

SurvivorBase.EOnFrame event · T1 InediaInfectedAI'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 — Dabs Framework silences CF
MissionGameplay.OnKeyRelease — VPPAdminTools silences Trader

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.

MissionServer.OnUpdate

every server frame

PVEZ Reloaded then Trader then CF then vanilla

CarScript.OnUpdate

every server frame

InediaInfectedAI then FlipTransport then vanilla

DayZGame.OnUpdate

every server frame

VPPAdminTools then CF then vanilla

PlayerBase.EEItemAttached

every inventory move

InediaInfectedAI then Forward Operator Gear then vanilla

PlayerBase.EEItemDetached

every inventory move

InediaInfectedAI then Forward Operator Gear then vanilla

DayZGame.OnRPC

per event

VPPAdminTools sometimes stops here then PVEZ Reloaded RPC send world scan then FlipTransport then Dabs Framework then CF sometimes stops here then vanilla

PlayerBase.OnRPC

per event

VPPAdminTools then InediaInfectedAI then PVEZ Reloaded then CookZ then BaseBuildingPlus then vanilla

PlayerBase.SetActions

per event

VPPAdminTools then InediaInfectedAI then MuchCarKey then Trader then BaseBuildingPlus then vanilla

ActionTogglePlaceObject.ActionCondition

per event

DNA Keycards sometimes stops here then CannabisPlus sometimes stops here then BaseBuildingPlus sometimes stops here then vanilla

CarScript.SetActions

per event

RUSForma_vehicles then Gas-Pump-Refueling then FlipTransport then vanilla

Wrench.SetActions

per event

RUSForma_vehicles then MuchCarKey then FlipTransport then vanilla

ActionCloseDoors.ActionCondition

per event

InediaInfectedAI then DNA Keycards 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.

PVEZ Reloaded

PlayerBase.OnScheduledTick

about 30× per player per second