This is a pretty minor fix but it will stop some error messages that would commonly occur within the first few seconds of the plugin starting. Now, if there is no lag, the location-caching-thread will start up one second after the plugin loads, but if there is lag, it will wait for the average tick time to be under 55ms for 5 seconds. In testing, this stopped the first few calls to cache a random location from timing out or failing, and had no noticeable effect otherwise.