Sentinel Enforcer - BreachingCharge
Sentinel Enforcer - BreachingCharge integration Optional add-on for Sentinel Enforcer. Install this only if your server also runs the BreachingCharge mod (HDSN / HandsomeNipple). It reports breaching-charge activity (placed / armed / detonated / defused / target destroyed — who, where, the target structure, and the damage dealt) to the dayz.fyi platform, for raid logs (the explosion layer). Requires:… (more)
Sentinel Enforcer - BreachingCharge integration Optional add-on for Sentinel Enforcer. Install this only if your server also runs the BreachingCharge mod (HDSN / HandsomeNipple). It reports breaching-charge activity (placed / armed / detonated / defused / target destroyed — who, where, the target structure, and the damage dealt) to the dayz.fyi platform, for raid logs (the explosion layer). Requires: @SentinelEnforcer (core) + the BreachingCharge mod. Server-side only — players install nothing. Dormant unless BreachingCharge is present. Add to your server launch: -serverMod=@SentinelEnforcer;@SentinelEnforcer_BreachingCharge
No file I/O on hot paths, no timers created per event, no per-player-per-frame hooks.
Every server-visible override preserves its chain.
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.
Structural load of the 328 scripted mods analyzed, lightest on the left. This mod's bar is lit; 23 others share it. Ranked list.
Lifecycle hooks carry 81% of this mod's structural load. 0.000 ms/s in all.
1 hook · 0.000002 ms/s
| Lifecycle hooksrun when an entity is created, loaded or deleted | 1 hook | 0.000002 ms/s | 81% | MissionServer.OnInit |
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.
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.
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 2 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.
| method | surface | server | super() | where |
|---|---|---|---|---|
HDSN_BreachingChargeLogger.LogEvent |
— | yes | ✓ | sentinel_addon_breachingcharge.pbo::scripts\4_World\capture\BreachingChargeHook.c:33 |
MissionServer.OnInit |
T3 | yes | ✓ | sentinel_addon_breachingcharge.pbo::scripts\5_Mission\_register.c:9 |
Dispatch surfaces and timers the grade prices
| surface | tier | rate (Hz) | rate source | ms/s |
|---|---|---|---|---|
MissionServer.OnInit | T3 | 0.1 | placeholder | 0.0000 |
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.
sentinel_addon_breachingcharge.pbo
SentinelAddon_BreachingChargerequiredVersion 0.1 — requiresSentinelEnforcer,HDSN_BreachingCharge
census 1.1 · findings 1.1 · hash bec7a82c0b6a899e