Stack composer

Started from [BR]INFINITY BADLANDS map/part/codelock PVP#badland novo: the 11 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.

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

Stall risks

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

Mods silencing mods

2 conflicts

Across 58 server-side methods hooked by two or more mods.

Structural load

0.34% of a frame at 100 players

3.404 ms per second, all 10 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#

AC-Mod-PacksilencesMMG Base Storage2 methods

Clothing.CanLoadItemIntoCargoClothingConditions check MMG Base Storage's conditions on this check no longer apply.

AC-Mod-Pack.pbo::AC-Scripts\4_World\AC\Modded\MgXlkLjXgvrpfzZp\鳜鑫癫鏖馕襦齉霰曦攘耱纛镴\AUX\6YTfy MQYj\{8AD10C31-2ADB-4296-A8F7-E4701232C972}\747DDFE.c:1

Clothing.CanReceiveItemIntoCargoClothingConditions check MMG Base Storage's conditions on this check no longer apply.

AC-Mod-Pack.pbo::AC-Scripts\4_World\AC\Modded\MgXlkLjXgvrpfzZp\鳜鑫癫鏖馕襦齉霰曦攘耱纛镴\AUX\6YTfy MQYj\{8AD10C31-2ADB-4296-A8F7-E4701232C972}\747DDFE.c:1

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

GameLabs then VPPAdminTools then CF then vanilla

MissionServer.OnUpdate

every server frame

AC-Mod-Pack then CF then vanilla

PlayerBase.OnRPC

per event

Hitmarker then AC-Mod-Pack sometimes stops here then BaseBuildingPlus then VPPAdminTools then vanilla

PlayerBase.SetActions

per event

AC-Mod-Pack then Advanced Weapon Scopes then BaseBuildingPlus then VPPAdminTools then vanilla

DayZGame.OnRPC

per event

FlipTransport then VPPAdminTools sometimes stops here then CF sometimes stops here then vanilla

PlayerBase.EEHitBy

per event

GameLabs then Hitmarker then AC-Mod-Pack then vanilla

ActionCloseFence.ActionCondition

per event

BaseBuildingPlus sometimes stops here then Code Lock then vanilla

ActionPackTent.ActionCondition

per event

AC-Mod-Pack sometimes stops here then Code Lock then vanilla

ActionPushCar.ActionCondition

per event

AC-Mod-Pack sometimes stops here then FlipTransport then vanilla

AnimalBase.EEHitBy

per event

GameLabs then Hitmarker then vanilla

BoatScript.EEHitBy

per event

GameLabs then AC-Mod-Pack then vanilla

CarScript.EEHitBy

per event

GameLabs then AC-Mod-Pack then vanilla

Stall risks#

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

VPPAdminTools

PlayerBase.CommandHandler

about 30× per player per second