Stack composer

Started from PROJECT ZARYA S.T.A.L.K.E.R. RP |https://discord.gg/WQGDSbVFwJ: the 21 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 VPPAdminTools
2 CF
3 Dabs Framework
4 ProjectZarya not analyzed
5 STALKER: DayZone | Map Public not analyzed
6 BuildEverywhere not analyzed
7 TOP Guns not analyzed
8 Tactical Flava
9 RUSForma_vehicles
10 Ear-Plugs
11 STALKER Equipment
12 STALKER Equipment ReTex not analyzed
13 XZone GasMasks not analyzed
14 Syndicate Items Pack
15 Syndicate Equips Pack not analyzed
16 [CnG]UAZ_452
17 [CnG]VAZ_2109 not analyzed
18 KAMAZ not analyzed
19 DayZ Editor Loader
20 BuilderItems
21 Project Zarya - Travnik Pack not analyzed

10 of 21 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 23 server-side methods hooked by two or more mods. 1 more on client-only UI classes, listed separately.

Structural load

0.28% of a frame at 100 players

2.836 ms per second, all 11 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

DayZGame.OnRPC

per event

Dabs Framework then CF sometimes stops here then VPPAdminTools 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