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

Include map count in desync info #483

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Include map count in desync info #483

wants to merge 1 commit into from

Commits on Jul 14, 2024

  1. Include map count in desync info 

    It may be a bit of a niche use case, but some desyncs happen only (or a lot more frequently) when players are looking at different maps. Making a list of "which map was each player looking at" would be much more difficult to implement, but just having the map count can suggest if an issue could have possibly happened due to having multiple active maps or not.

I've added a bit of extra safety (instead of `Find.Maps?.Count`) as I've encountered a couple of weird situations in the past where `Find.Maps.Count` ended up throwing `NullReferenceException`. This may have been a weird mod conflict/interaction, but I've decided to be on the safer side here.
    @SokyranTheDragon
    SokyranTheDragon committed Jul 14, 2024
    Configuration menu
    Copy the full SHA
    527ef50 View commit details
    Browse the repository at this point in the history