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.

Sign up for GitHub

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

Jump to bottom

Double gameover detection #3

Open
Qazzquimby opened this issue Mar 11, 2019 · 2 comments
Open

Double gameover detection #3

Qazzquimby opened this issue Mar 11, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@Qazzquimby
Copy link
Owner

After loading a new map, Lindholm will sometimes immediately detect a new end of game, wait 30 (for the potg it thinks is happening) and then restart the map again.
@Qazzquimby
Copy link
Owner Author

Confirmed ongoing.
There are checks and safeties that should be preventing this. It might be best to start by adding verbose logging of gameover and restart events.

@Qazzquimby Qazzquimby added the bug Something isn't working label Mar 12, 2019
@Qazzquimby
Copy link
Owner Author

I've seen Lindholm print end of game chat messages twice, which should help pinpoint the point of error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Qazzquimby