From b7a59d05580048cc713dffb3ffc12d7d0e1ed20a Mon Sep 17 00:00:00 2001 From: Levi Schuck Date: Sat, 5 May 2018 12:20:12 -0500 Subject: [PATCH] FPS plugin: fix startup not applying limits Issue: @deathbeam reported that the limits were not applying immediately after start up and this required dirtying the config manually to get it to apply. Problem: The draw listener expects `reloadConfig` to be called prior to its active use, so it is also an initalizing method. `reloadConfig` was only being called if the config changed, and not when the plugin was activated. Solution: Call `reloadConfig` when the plugin is activated so it has been initialized. --- .../src/main/java/net/runelite/client/plugins/fps/FpsPlugin.java | 1 + 1 file changed, 1 insertion(+) diff --git a/runelite-client/src/main/java/net/runelite/client/plugins/fps/FpsPlugin.java b/runelite-client/src/main/java/net/runelite/client/plugins/fps/FpsPlugin.java index cb2abf4b84..5ccf90b9d7 100644 --- a/runelite-client/src/main/java/net/runelite/client/plugins/fps/FpsPlugin.java +++ b/runelite-client/src/main/java/net/runelite/client/plugins/fps/FpsPlugin.java @@ -94,6 +94,7 @@ public class FpsPlugin extends Plugin protected void startUp() throws Exception { drawManager.registerEveryFrameListener(drawListener); + drawListener.reloadConfig(); } @Override