Stack composer

Started from SURVIVORS [PvP| TACTICAL| LOOT| VANILLA| COMMVANILLA]: the 20 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.

1 CF
2 Dabs Framework
3 NovaDayZNRGSkyfallRNCDayOneSaviorsRGDZavrFreshSpawnsArenaPVPHinexUSD not analyzed
4 Code Lock
5 HUNTERMod not analyzed
6 HUNTERChernarus not analyzed
7 MMG - Mightys Military Gear
8 VPPAdminTools
9 VanillaPlusPlusMap
10 WindstridesClothingPack
11 Forward Operator Gear
12 Forward Operator Gear Pack Retextures not analyzed
13 CarCover
14 Advanced Weapon Scopes
15 Vanilla Sleeping Bags not analyzed
16 Peek Doors not analyzed
17 Dead Ahead not analyzed
18 CJ187-LootChest
19 A-6 Secure Containers
20 Tactical Flava

7 of 20 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

None

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

Structural load

0.30% of a frame at 100 players

3.018 ms per second, all 13 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

VPPAdminTools then CF then vanilla

PlayerBase.EEItemAttached

every inventory move

Tactical Flava then Forward Operator Gear then WindstridesClothingPack then vanilla

PlayerBase.EEItemDetached

every inventory move

Tactical Flava then Forward Operator Gear then WindstridesClothingPack then vanilla

PlayerBase.SetActions

per event

Advanced Weapon Scopes then WindstridesClothingPack then VPPAdminTools then MMG - Mightys Military Gear then vanilla

DayZGame.OnRPC

per event

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

PlayerBase.CanReceiveAttachment

per event

Tactical Flava sometimes stops here then Forward Operator Gear sometimes stops here then vanilla

PlayerBase.OnVariablesSynchronized

per event

Tactical Flava 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

about 30× per player per second