Stack composer

Started from Axis|PVE Only|Chernarus|Trader: the 24 mods it publishes to the Steam server browser (as of 2026-10-21), 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 VPPAdminTools
2 CF
3 Carim not analyzed
4 BuildEverywhereV2 not analyzed
5 RaG_Core
6 Server_Information_Panel
7 BuilderItems
8 RaG_BaseItems
9 RaG_BaseBuilding
10 RaG_Vehicle_Pack
11 BLR Trader not analyzed
12 No-Vehicle-Damage
13 fx-earplugs not analyzed
14 MuchCarKey
15 DayZ Editor Loader
16 Dabs Framework
17 Basic Territories
18 200 Max Ammo Stack not analyzed
19 Workshop 3719916265 not analyzed
20 Tactical Flava
21 GasMasksOnly
22 RaG_Infected_Hordes not analyzed
23 PokerMod not analyzed
24 Workshop 3749126415 not analyzed

9 of 24 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

None

Across 52 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.667 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.

✓ No server-side conflicts: every method two or more of these mods hook preserves super() end to end.

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

NotificationSystem.GetNotificationData — Dabs Framework silences CF

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

Server_Information_Panel then CF then vanilla

PlayerBase.SetActions

per event

MuchCarKey then RaG_Vehicle_Pack then RaG_BaseItems then VPPAdminTools then vanilla

DayZGame.OnRPC

per event

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

Hammer.SetActions

per event

RaG_BaseBuilding then RaG_BaseItems then RaG_Core then vanilla

WoodAxe.SetActions

per event

RaG_Vehicle_Pack then RaG_BaseBuilding then RaG_BaseItems then vanilla

ActionDismantlePart.ActionCondition

per event

Basic Territories then RaG_BaseBuilding sometimes stops here then vanilla

FirefighterAxe.SetActions

per event

RaG_BaseBuilding then RaG_BaseItems then vanilla

Hatchet.SetActions

per event

RaG_BaseBuilding then RaG_BaseItems then vanilla

PlayerBase.OnRPC

per event

RaG_Core then VPPAdminTools then vanilla

PlayerBase.OnVariablesSynchronized

per event

Tactical Flava then VPPAdminTools then vanilla

Shovel.SetActions

per event

RaG_Vehicle_Pack then RaG_BaseItems 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