Making FPS Reducer Work Alongside Other Performance Mods

FPS Reducer overlaps in purpose with other performance mods, and stacking them carelessly can produce confusing results — frame rates that never recover, or throttling that fights your optimiser.

Know what each mod does

FPS Reducer's job is narrow: lower the frame rate when the window is unfocused or the player is idle. It does not change rendering, chunk loading, or memory use. Optimisation mods do the opposite kind of work — they make each frame cheaper. These goals do not conflict, but their settings can.

Avoid double frame limiting

If another mod or the game itself is already capping your frame rate, adding FPS Reducer's idle cap on top is fine, but do not set both to similar values. The idle cap should be clearly lower than your normal cap, otherwise the mod engages and you cannot tell the difference.

Watch for input-detection conflicts

Some mods change how the game reads input — camera mods, controller support, automation tools. FPS Reducer decides you are idle based on input, so anything that generates or suppresses input events can confuse it. If the mod throttles while you are clearly playing, that is the likely cause. Raise the idle delay or disable the idle trigger.

Test after every mod change

After adding or removing a performance mod, alt-tab away and back, and stand still for a while. Confirm the frame rate drops when expected and recovers instantly when you move. If recovery is slow, the reduced rate is too low or another mod is interfering with frame pacing.

Order of operations

Tune your optimiser first so your baseline frame rate is stable, then tune FPS Reducer's triggers against that baseline. Doing it the other way around means you are adjusting the reducer to compensate for a problem the optimiser should be solving.