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.
This commit is contained in:
Levi Schuck
2018-05-05 12:20:12 -05:00
parent ca8c8bef13
commit b7a59d0558

View File

@@ -94,6 +94,7 @@ public class FpsPlugin extends Plugin
protected void startUp() throws Exception
{
drawManager.registerEveryFrameListener(drawListener);
drawListener.reloadConfig();
}
@Override