You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2021. It is now read-only.
Would love to have this, or at least some type of dynamic spawnpoint analysis of what to check and when. Although I think this would be better suited for the next counter part app, the DeviceController.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In principle, with enough data on each spawn point, we can get a good estimate of the spawn table distribution and thus cluster the spawnpoints. This has been done before for Boston: https://www.reddit.com/r/TheSilphRoad/comments/5etwz9/analysis_identification_of_potential_biomes_by/
It seems feasible if we can automatize the process and dynamically cluster the spawnpoints once in a while.
The text was updated successfully, but these errors were encountered: