Turns out there was a typo in the win screen code that causes this issue. Pretty easy fix once I found it. Thanks again for reporting it.
I'll just assume I won then 😃
