← modperf

Stack composer

Started from STALKER QUANT PVE 1: the 20 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.

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.

The one pair#

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.

Stall risks#

8 places where one mod's code can hold up a frame by itself, whatever the load figure says. Each is a pattern found in the code, not a measurement: how much it costs depends on what the hook does inside. Most severe first, then in load order.

• Per-player, per-frame hook. Runs for every player on every tick, so whatever it does inside is multiplied by the population.
• Timer created inside a hot hook. Registers a timer each time the hook runs. Timers that are never cleaned up pile up in the queue the server walks every frame; the analysis cannot see the cleanup, so read the code.

Everything else#

69 methods on client-only classes are not shown: a dedicated server never runs them.