← modperf · analyzed mods

SchanaModParty_119fix

Fixed version of Schana Mod Party - fixed client crash when player relog Original mod: https://steamcommunity.com/sharedfiles/filedetails/?id=2075831381 or another fork: https://steamcommunity.com/sharedfiles/filedetails/?id=2534883520 Source: https://github.com/schana/dayz-mod-party Enjoy -Hunterz-

Workshop 2885347864 · mod updated 2022-11-11 · analyzed 2026-10-03 06:34 UTC · history · 23 script files

CharacterMechanics Workshop tags, chosen by the author

Stall risks
None found

No file I/O on hot paths, no timers created per event, no per-player-per-frame hooks.

Compatibility
Chain-safe

Every server-visible override preserves its chain.

Structural footprint 1.1
A
clean
Heavier than 95% of 328 scripted mods analyzed.

0.112% of each server frame at 100 players (1.123 ms/s). Counts hook dispatch and timers only, not what the hooks do inside. Methodology.

Where this mod sits

Structural load of the 328 scripted mods analyzed, lightest on the left. This mod's bar is lit; 7 others share it. Ranked list.

20
40
60
  • 24 mods
    0.0000022 to 0.0000046 ms/s · grade A
  • 7 mods
    0.0000046 to 0.00001 ms/s · grade A
  • 1 mod
    0.00001 to 0.000022 ms/s · grade A
  • 1 mod
    0.000022 to 0.000046 ms/s · grade A
  • 37 mods
    0.0001 to 0.00022 ms/s · grade A
  • 26 mods
    0.00022 to 0.00046 ms/s · grade A
  • 33 mods
    0.00046 to 0.001 ms/s · grade A
  • 22 mods
    0.001 to 0.0022 ms/s · grade A
  • 13 mods
    0.0022 to 0.0046 ms/s · grade A
  • 10 mods
    0.0046 to 0.01 ms/s · grade A
  • 5 mods
    0.01 to 0.022 ms/s · grade A
  • 18 mods
    0.022 to 0.046 ms/s · grade A
  • 17 mods
    0.046 to 0.1 ms/s · grade A
  • 41 mods
    0.1 to 0.22 ms/s · grade A
  • 26 mods
    0.22 to 0.46 ms/s · grade A
  • 28 mods
    0.46 to 1 ms/s · grade A
  • This mod
  • 10 mods
    2.2 to 4.6 ms/s · grade B
  • 1 mod
    4.6 to 10 ms/s · grade B to C
A316
B11
C1
D0
E0
ms/s, log scale: each labelled step is ten times the one before. Letter grade and mods holding it below the axis.
Where the load comes from

Repeating timers carry 100% of this mod's structural load. 1.123 ms/s in all.

Lifecycle hooks · <0.1%
2 hooks · 0.000004 ms/s
100%Repeating timers · 100%
8 timers · 1.1 ms/s
Lifecycle hooksrun when an entity is created, loaded or deleted 2 hooks 0.000004 ms/s <0.1% MissionBase.OnInit, MissionServer.OnInit
Repeating timersstay in the timer queue, which is walked every frame 8 timers 1.1 ms/s 100% 2 × every 16 ms, every 1 s, every 10 s and 4 more

Counts how often each hook is dispatched and how many timers stay alive, not what the code inside does. Some rates are order-of-magnitude estimates; the methodology lists which.

What this report can tell you

Which vanilla methods the mod hooks, which of them drop the chain, how often each hook fires, and which risky calls sit inside hot hooks.

What it cannot

How long hook bodies take, network cost, or engine-side load. Measured across live fleets, most server lag comes from the engine and world state, not mod script chains — a light footprint does not clear a mod of lag, and a heavy one does not convict it. Methodology.

Everything else

All 9 overrides

Surface is the dispatch tier the rubric can price (— = unpriced); server is whether the override exists on a dedicated server; super() shows whether the vanilla chain is preserved on a server.

methodsurfaceserversuper()where
BasicMapController.OnMarkerSave — yes ✓ SchanaModParty.pbo::game\basicmapintegration\basicmapcontroller.c:3
BasicMapController.OnMarkerDelete — yes ✓ SchanaModParty.pbo::game\basicmapintegration\basicmapcontroller.c:14
MissionBase.OnInit T3 yes ✓ SchanaModParty.pbo::mission\mission\missionbase.c:3
MissionBase.CreateScriptedMenu — yes ✓ SchanaModParty.pbo::mission\mission\missionbase.c:8
MissionGameplay.OnMissionStart T3 yes ✓ SchanaModParty.pbo::mission\mission\missiongameplay.c:6
MissionGameplay.OnInit T3 yes ✓ SchanaModParty.pbo::mission\mission\missiongameplay.c:24
MissionGameplay.OnMissionFinish T3 yes ✓ SchanaModParty.pbo::mission\mission\missiongameplay.c:34
MissionGameplay.OnUpdate T0 yes ✓ SchanaModParty.pbo::mission\mission\missiongameplay.c:42
MissionServer.OnInit T3 yes ✓ SchanaModParty.pbo::mission\mission\missionserver.c:2
Dispatch surfaces and timers the grade prices
surfacetierrate (Hz)rate sourcems/s
MissionBase.OnInitT3 0.1placeholder0.0000
MissionServer.OnInitT3 0.1placeholder0.0000

Repeating timers

period (ms)residency ms/sfiring ms/swhere
160.1400 0.001550SchanaModParty.pbo::game\schana_party_marker.c:22
160.1400 0.001550SchanaModParty.pbo::game\schana_party_nametag.c:37
5000.1400 0.000050SchanaModParty.pbo::mission\gui\schana_party_menu.c:47
10000.1400 0.000025SchanaModParty.pbo::game\schana_party_marker_manager_client.c:16
20000.1400 0.000012SchanaModParty.pbo::game\schana_party_manager_client.c:20
100000.1400 0.000002SchanaModParty.pbo::game\schana_party_manager_server.c:21
150000.1400 0.000002SchanaModParty.pbo::game\schana_party_manager_client.c:21
300000.1400 0.000001SchanaModParty.pbo::game\basicmapintegration\schanapartybasicmapapi.c:64

Includes 0.000 ms/s from placeholder-rated surfaces.

Load-order constraints (CfgPatches)

What each PBO declares: its addon identity and the addons it requires to be loaded first (requiredAddons). A partial load-order signal from the mod's own metadata.

SchanaModParty.pbo

  • SchanaModParty — requires SchanaModPartyDefine, JM_CF_Scripts

SchanaModPartyDefine.pbo

  • SchanaModPartyDefine requiredVersion 0.1 — no requiredAddons

census 1.1 · findings 1.1 · hash ed8673f2e6ffb245