← modperf · analyzed mods

PVEZMarkersOnVPPMap

It is allowed to be used, copied, packed, modded, you're absolutely free to do whatever you want with this mod and it's source code. Compatibility plugin for PVEZ and VanillaPlusPlusMap. It makes PVEZ lawbreakers markers and zones borderlines visible on Vanilla++ map. PVEZ's player marker won't be displayed on VPPMap, because VPPMap has it's own player marker. This plugin only adds lawbreakers markers and zones… (more)

It is allowed to be used, copied, packed, modded, you're absolutely free to do whatever you want with this mod and it's source code. Compatibility plugin for PVEZ and VanillaPlusPlusMap. It makes PVEZ lawbreakers markers and zones borderlines visible on Vanilla++ map. PVEZ's player marker won't be displayed on VPPMap, because VPPMap has it's own player marker. This plugin only adds lawbreakers markers and zones borderlines. For DayZ-Expansion map use this: PVEZ Expansion plugin. INSTALLATION INSTRUCTIONS FOR SERVER ADMINS: Install PVEZ and VanillaPlusPlusMap. Subscribe to the PVEZMarkersOnVPPMap mod at Steam Workshop; Copy/paste the mod folder from your "DayZ/!Wokshop/" folder into your server root folder ("DayZServer/"); Make sure your "DayZServer/Keys" folder contains "Ermiq.bikey" file from PVEZ (or you can copy/paste the file from this mod's "Keys" folder); Set up your server *.bat to load PVEZ, VanillaPlusPlusMap and PVEZMarkersOnVPPMap mod (e.g., -mod=@PVEZ;@VanillaPlusPlusMap;@PVEZMarkersOnVPPMap). Don't forget to also load VPP's dependencies (CF mod).

Workshop 2109061314 · mod updated 2021-02-11 · analyzed 2026-10-03 08:23 UTC · history · 1 script files

EnvironmentMechanics 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
No server script overrides, so nothing to rank.

No server-side script overrides. Counts hook dispatch and timers only, not what the hooks do inside. Methodology.

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

methodsurfaceserversuper()where
VPPMapMenu.Init — yes ✓ PVEZMarkersOnVPPMap.pbo::5_mission\gui\mapmenu.c:5
VPPMapMenu.DisplayClientMarkers — yes ✓ PVEZMarkersOnVPPMap.pbo::5_mission\gui\mapmenu.c:18
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.

PVEZMarkersOnVPPMap.pbo

  • PVEZMarkersOnVPPMap requiredVersion 0.1 — requires DZ_Data

census 1.1 · findings 1.1 · hash 48ba167d3666d2b1