← modperf · analyzed mods

Highwatch CF

**Title:** Highwatch CF (RPC counter for Community Framework) ``` Highwatch CF Server-side only. Requires Highwatch and Community Framework. Players do not need to subscribe. A small add-on for the Highwatch server mod. Community Framework handles its RPC channels (RPCManager, notifications, networked variables) inside DayZGame.OnRPC without calling super, so Highwatch on its own never sees them. This add-on loads… (more)

**Title:** Highwatch CF (RPC counter for Community Framework) ``` Highwatch CF Server-side only. Requires Highwatch and Community Framework. Players do not need to subscribe. A small add-on for the Highwatch server mod. Community Framework handles its RPC channels (RPCManager, notifications, networked variables) inside DayZGame.OnRPC without calling super, so Highwatch on its own never sees them. This add-on loads after Community Framework, counts those RPCs, then hands over. Nothing else changes. What you get The Network view in the Highwatch desk shows Community Framework traffic by type and by player beside everything else, and the RPC flood detector sees the whole picture. Payloads are never read. Install Needs @Highwatch 0.14.0 or newer and @CF on the server. -serverMod=@YourOtherMods;@CF;@Highwatch;@Highwatch-CF No config. The desk's Network tab reports the add-on as loaded. Do not load it without Community Framework. A missing required addon stops the server. If your server runs DayZ Expansion, use Highwatch Expansion instead; loading both is harmless, nothing is counted twice. Highwatch Discord ```

Workshop 3819431234 · mod updated 2026-10-14 · analyzed 2026-10-15 20:04 UTC · history · 1 script files

Server 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 10% of 328 scripted mods analyzed.

less than 0.001% of each server frame at 100 players (0.000 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; 36 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
  • This mod
  • 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
  • 8 mods
    1 to 2.2 ms/s · grade A to B
  • 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

Event hooks carry 99.8% of this mod's structural load. 0.000 ms/s in all.

99.8%Event hooks · 99.8%
1 hook · 0.0002 ms/s
Event hooksrun when something happens: an inventory move, a hit, an action 1 hook 0.0002 ms/s 99.8% DayZGame.OnRPC

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.

Where this mod runs often

Hooks on per-frame and high-rate surfaces, with what their bodies call. Body work, not the hook itself, is what costs frame time.

OnRPC on DayZGame
per event
no I/O, timers or RPC
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 1 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
DayZGame.OnRPC T2 yes ✓ HighwatchCF.pbo::scripts\3_Game\hw_rpc_cf.c:15
Dispatch surfaces and timers the grade prices
surfacetierrate (Hz)rate sourcems/s
DayZGame.OnRPCT2 8.0placeholder0.0002

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.

HighwatchCF.pbo

  • HighwatchCF requiredVersion 0.1 — requires Highwatch, JM_CF_Scripts

census 1.1 · findings 1.1 · hash f5c2f3c34b3fcfae