Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inaccuracies when areas span multiple timezones. #40

Open
comstud opened this issue Mar 14, 2024 · 0 comments
Open

Inaccuracies when areas span multiple timezones. #40

comstud opened this issue Mar 14, 2024 · 0 comments

Comments

@comstud
Copy link
Collaborator

comstud commented Mar 14, 2024

If one has areas in multiple time zones, the global spawn data is all mixed together. If only 1 small area is in a completely separate timezone, it's effectively comparing against global spawn data that contains mostly data for another time zone. This would mess up the logic that prevents CD/Spotlight hour mons from being counted as nesting.

I wondered if anyone would have this. Apparently at least 1 person does.

@comstud comstud changed the title Inaccuracies when areas spawn multiple timezones. Inaccuracies when areas span multiple timezones. Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant