LagMeter
Diagnostic: logs FPS, loaded lights, smoke, fires, building pieces, objects, top object types and ms per frame of main game systems to find what makes a base lag.
About this mod Author’s original text
Lag Meter
A diagnostic tool for finding out why a place lags. Every few seconds it writes a line to the BepInEx log
(BepInEx/LogOutput.log).
What it logs
- FPS, ms per frame, worst frame and garbage collections.
- Loaded point lights (and how many cast shadows), smoke puffs, fires burning, building pieces, plants, network objects
and physics bodies.
- Milliseconds per frame spent in the main game systems (scripts, object streaming, network, building support, plants,
fires, smoke, grass, terrain).
- Once a minute: the 25 most common loaded object types and which objects the lights belong to.
How to use
Stand where it lags for a minute, then walk somewhere that does not lag for comparison, and read the [Lag] lines.
Settings
| Section | Setting | Default |
|---|---|---|
| General | Enabled | true |
| General | Interval (seconds) | 10 |
Notes
- Client-side. Measuring costs a little performance; disable or remove it when done.
Install & use Install: BepInEx plugin
- The archive from playbuff is the mod itself — usually a BepInEx plugin (a .dll or a plugin folder once unzipped).
- Recommended: use a community mod manager (such as r2modman) — pick this game, import the mod, and the manager sets up BepInEx and its dependencies for you.
- Manual route: install the BepInEx loader in the game folder, then drop the unzipped .dll or plugin folder into BepInEx/plugins/.
- Launch the game — the BepInEx console logs every plugin it loads; seeing this mod in the log means it is installed.
Mods with listed dependencies need those installed too, or they will not load. Options are usually changed in-game or in the plugin's config file. In multiplayer, the host and every client need the same mods installed.
Install these first, or the mod will not work: