Stack composer

Started from #[ BR ]GROUPZ VANILLA+ | BBP | KOTH | CODELOCK | BUNKER | PVP |: the 21 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.

6 of 21 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

3 conflicts

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

Structural load

0.37% of a frame at 100 players

3.709 ms per second, all 15 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#

BaseBuildingPlussilencesAC-Mod-Pack3 methods

ActionDeployObject.OnFinishProgressServer event Vanilla's deploy completion (and earlier mods' hooks on it) no longer runs. BaseBuildingPlus.pbo::scripts\4_World\actions\vanilla\ActionDeployObject.c:8 Construction.IsColliding check AC-Mod-Pack's conditions on this check no longer apply. BaseBuildingPlus.pbo::scripts\4_World\overrides\Construction.c:62 Construction.IsCollidingEx check AC-Mod-Pack's conditions on this check no longer apply. BaseBuildingPlus.pbo::scripts\4_World\overrides\Construction.c:67

1 conflict on client-only classes (menus, HUD, notifications) — no server effect

NotificationSystem.GetNotificationData — CF 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

CF then VPPAdminTools then GameLabs then vanilla

MissionServer.OnUpdate

every server frame

CF then AC-Mod-Pack then vanilla

PlayerBase.SetActions

per event

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

DayZGame.OnRPC

per event

CF sometimes stops here then Dabs Framework then VPPAdminTools sometimes stops here then vanilla

PlayerBase.OnRPC

per event

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

ActionCarDoors.ActionCondition

per event

AC-Mod-Pack sometimes stops here then RaG_Vehicle_Pack sometimes stops here 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

BoatScript.EEHitBy

per event

AC-Mod-Pack then GameLabs then vanilla

CamoNet.SetActions

per event

BaseBuildingPlus then RaG_Vehicle_Pack then vanilla

CarScript.EEHitBy

per event

AC-Mod-Pack then GameLabs then vanilla

ItemBase.SetActions

per event

BaseBuildingPlus then MMG Base Storage NoCodeLock 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.

GameLabs

PlayerBase.OnScheduledTick

about 30× per player per second