Stack composer

Started from NoCo Gaming's Modded Badlands |Wiped 10/15/26|PVE|Air Drops|: the 28 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.

1 CF
2 VPPAdminTools
3 DayZ-Expansion-Core
4 DayZ-Expansion-Missions
5 DayZ-Expansion-Licensed
6 Krak3nsAmmoStacks100 not analyzed
7 InventoryPlusPlus
8 UsefulSuppressors not analyzed
9 UniversalSuppressor not analyzed
10 Gas-Pump-Refueling
11 Combinable Items not analyzed
12 Stack_paper not analyzed
13 nocogamingflags not analyzed
14 nocogaming serverpack not analyzed
15 nocogamingstartergear not analyzed
16 nocogamingcustom not analyzed
17 MMG - Mightys Military Gear
18 Dabs Framework
19 GameLabs
20 RaG_BaseItems
21 RaG_Core
22 RaG_Hunting_Cabin
23 BodyBags
24 CookZ
25 SIX-DayZ-Auto-Run
26 DodgeRam3500 not analyzed
27 InventoryInCar not analyzed
28 Name Tags not analyzed

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

Stall risks

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

Mods silencing mods

3 conflicts

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

Structural load

0.44% of a frame at 100 players

4.371 ms per second, all 16 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.

3 methods across 3 pairs. Read across: the mod on the left silences the mod at the top. Both in load order. 1 2–4 5–14 15+ methods

silences →	1CF	3DayZ-Expansion-Core	23BodyBags	all
3DayZ-Expansion-Core	1DayZ-Expansion-Core silences CF 1 method: 1 value			1
20RaG_BaseItems		1RaG_BaseItems silences DayZ-Expansion-Core 1 method: 1 check	1RaG_BaseItems silences BodyBags 1 method: 1 check	2
all	1	1	1	3
6Krak3nsAmmoStacks100	Not analyzed, so what it silences is unknown. Queue it in the list above.
8UsefulSuppressors	Not analyzed, so what it silences is unknown. Queue it in the list above.
9UniversalSuppressor	Not analyzed, so what it silences is unknown. Queue it in the list above.
11Combinable Items	Not analyzed, so what it silences is unknown. Queue it in the list above.
12Stack_paper	Not analyzed, so what it silences is unknown. Queue it in the list above.
13nocogamingflags	Not analyzed, so what it silences is unknown. Queue it in the list above.
	…and 6 more mods not analyzed yet.

The 3 pairs, largest first# ·

DayZ-Expansion-CoresilencesCF1 method

NotificationRuntimeData.GetIcon value CF's value here is replaced. core_scripts.pbo::3_Game\DayZExpansion_Core\Client\Notifications\NotificationRuntimeData.c:29

RaG_BaseItemssilencesBodyBags1 method

PlantMaterial.CanPutAsAttachment check BodyBags's conditions on this check no longer apply. For PlantMaterial instances, through its ancestor ItemBase. rag_baseitems_scripts.pbo::4_World\rag_baseitems_scripts\Modded\PlantMaterial.c:3

RaG_BaseItemssilencesDayZ-Expansion-Core1 method

PlantMaterial.CanPutAsAttachment check DayZ-Expansion-Core's conditions on this check no longer apply. For PlantMaterial instances, through its ancestor ItemBase. rag_baseitems_scripts.pbo::4_World\rag_baseitems_scripts\Modded\PlantMaterial.c:3

2 conflicts on client-only classes (menus, HUD, notifications) — no server effect

NotificationSystem.GetNotificationData — Dabs Framework silences CF
NotificationSystem.GetNotificationData — Dabs Framework silences DayZ-Expansion-Core

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 DayZ-Expansion-Core sometimes stops here then VPPAdminTools then CF then vanilla

DayZGame.OnRPC

per event

Dabs Framework then DayZ-Expansion-Core sometimes stops here then VPPAdminTools sometimes stops here then CF sometimes stops here then vanilla

PlayerBase.OnRPC

per event

SIX-DayZ-Auto-Run sometimes stops here then CookZ then RaG_Core then VPPAdminTools then vanilla

PlayerBase.SetActions

per event

RaG_BaseItems then MMG - Mightys Military Gear then DayZ-Expansion-Core then VPPAdminTools then vanilla

Hammer.SetActions

per event

RaG_Hunting_Cabin then RaG_Core then RaG_BaseItems then vanilla

AnimalBase.EEHitBy

per event

GameLabs then DayZ-Expansion-Core then vanilla

CarScript.EEHitBy

per event

RaG_Core then GameLabs then vanilla

Hatchet.SetActions

per event

RaG_Hunting_Cabin then RaG_BaseItems then vanilla

MotorbikeScript.EEHitBy

per event

GameLabs then DayZ-Expansion-Core then vanilla

PlayerBase.OnVariablesSynchronized

per event

DayZ-Expansion-Missions then VPPAdminTools then vanilla

ZombieBase.EEHitBy

per event

GameLabs then DayZ-Expansion-Core then vanilla

Stall risks#

5 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