Stack composer
Started from Calantar Zone: the 23 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.
Your stack in load order, earliest first. Drag a row, or use the arrows, to reorder.
- 1 SlowerMetabolism not analyzed
- 2 Zenarchist's Catch Rain not analyzed
- 3 Search For Loot Improved not analyzed
- 4 Realistic Weapons not analyzed
- 5 Realistic Suppressors not analyzed
- 6 More Durable Clothing - Extra not analyzed
- 7 First Aid Kit on Belt not analyzed
- 8 Immersive Placing Update not analyzed
- 9 MetroWatch 1.27 not analyzed
- 10 AmmoStackBullet
- 11 Car Radio not analyzed
- 12 MWGSM_Trader not analyzed
- 13 Rejects Quest Mod not analyzed
- 14 VVN_Greenhouse_Codelock not analyzed
- 15 TP_Apoc_SUV not analyzed
- 16 Combined Repair Tools not analyzed
- 17 G_Coin not analyzed
- 18 Storage Containers
- 19 TP_Apoc_Mustang not analyzed
- 20 Better Batteries not analyzed
- 21 VVN_Old_refrigerator not analyzed
- 22 MBM_ApocalypticPAZ not analyzed
- 23 DayZ-Guitar not analyzed
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.
Across 0 server-side methods hooked by two or more mods.
0.000 ms per second, all 2 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.
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.
No per-frame or high-rate hook is shared by two or more of these mods.
Everything else#
All 0 server-side methods hooked by two or more mods
vanilla → earliest mod → … → latest mod (dispatch enters at the latest). struck = suppressed by a later chain break; ✂ = no super(); "(cond)" = super() only on some paths.
| method | tier | chain (load order) |
|---|
4 methods hooked by only one of these mods
No cross-mod interaction is possible here; a ✂ still means vanilla's behaviour on that method is replaced.
| method | tier | mod |
|---|---|---|
Edible_Base.ProcessDecay |
— | Storage Containers ✂ |
ModItemRegisterCallbacks.RegisterHeavy |
— | Storage Containers |
ModItemRegisterCallbacks.RegisterOneHanded |
— | Storage Containers |
ModItemRegisterCallbacks.RegisterTwoHanded |
— | Storage Containers |
A conflict shows that code is skipped, not that an author made a mistake — overhaul mods replace systems on purpose. Long chains are cheap: one link costs about 25 ns per dispatch. What costs frame time is the work inside each hook, which is why the badges are there. Everything here comes from the mods' code alone; nothing was measured on a server. Methodology.