Stack composer

Started from [BR]Brasil MW Vanilla 1PP: the 6 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.

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

Stall risks

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

Mods silencing mods

2 conflicts

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

Structural load

0.30% of a frame at 100 players

2.959 ms per second, all 4 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

CF then VPPAdminTools then vanilla

MissionServer.OnUpdate

every server frame

CF then AC-Mod-Pack then vanilla

DayZGame.OnRPC

per event

CF sometimes stops here then VPPAdminTools sometimes stops here then vanilla

PlayerBase.OnRPC

per event

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

PlayerBase.OnVariablesSynchronized

per event

AC-Mod-Pack then VPPAdminTools then vanilla

PlayerBase.SetActions

per event

AC-Mod-Pack then VPPAdminTools then vanilla

Stall risks#

6 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