Stack composer

Started from XAIPOEBLIVO | NASDARA 3PP | VANILLA+ | RU PVP: the 18 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 VPPAdminTools
4 XPECoreTemp not analyzed
5 RaG_Core
6 RaG_BaseBuilding
7 Basic Territories
8 FlipTransport
9 AutoRun not analyzed
10 VanillaPlusPlusMap
11 CargoSorting not analyzed
12 GameLabs
13 Tactical Flava
14 Zens Notes
15 Zenarchist's Core Mod not analyzed
16 Ear-Plugs
17 Area Announcements not analyzed
18 Item Info not analyzed

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

Stall risks

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

Mods silencing mods

None

Across 44 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.715 ms per second, all 12 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

GameLabs then VPPAdminTools then CF then vanilla

DayZGame.OnRPC

per event

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

ActionDeployObject.ActionCondition

per event

Zens Notes then Basic Territories then vanilla

ActionDismantlePart.ActionCondition

per event

Basic Territories then RaG_BaseBuilding sometimes stops here then vanilla

BaseBuildingBase.EEHitBy

per event

GameLabs then Basic Territories then vanilla

CarScript.EEHitBy

per event

GameLabs then RaG_Core then vanilla

Hammer.SetActions

per event

RaG_BaseBuilding then RaG_Core then vanilla

PlayerBase.OnRPC

per event

RaG_Core then VPPAdminTools then vanilla

PlayerBase.OnVariablesSynchronized

per event

Tactical Flava then VPPAdminTools then vanilla

Weapon_Base.SetActions

per event

Tactical Flava then RaG_Core then vanilla

Stall risks#

8 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.
Timer created inside a hot hook. Registers a timer each time the hook runs. Timers that are never cleaned up pile up in the queue the server walks every frame; the analysis cannot see the cleanup, so read the code.

VPPAdminTools

PlayerBase.CommandHandler

about 30× per player per second