← modperf

Stack composer

Started from KarmaKrew Sakhal EU - 1PP | VANILLA + MODS: the 17 mods it publishes to the Steam server browser (as of 2026-10-21), 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.

✓ No server-side conflicts: every method two or more of these mods hook preserves super() end to end.

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#

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

• File I/O in a hot hook. Reads or writes a file on the main thread each time the hook runs; the frame waits on the disk.
• Per-player, per-frame hook. Runs for every player on every tick, so whatever it does inside is multiplied by the population.

Everything else#

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