I recall this was previously asked/discussed but I couldn't find it while I'm still in my phone.
This past weekend leading up to and after GeoWoodstock, I used random live caching in unplanned locations more than I normally do. I likely had no concern of going over my limit, but I normally just needed to load the closest couple of caches and not 50 like the function does today. This was more than just about my limit as the GC API was under extreme load and was very slow or timing out.
If the number to load in live vote was user editable, that would be a useful addition.
Question
Team DEMP
I recall this was previously asked/discussed but I couldn't find it while I'm still in my phone.
This past weekend leading up to and after GeoWoodstock, I used random live caching in unplanned locations more than I normally do. I likely had no concern of going over my limit, but I normally just needed to load the closest couple of caches and not 50 like the function does today. This was more than just about my limit as the GC API was under extreme load and was very slow or timing out.
If the number to load in live vote was user editable, that would be a useful addition.
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.