EDSM Fuze

[Rixxan]

After the first EDSM timeout:

• Start an automatic, 5m loop to check for EDSM status (With announcement every 5M so blocking is known)
• Any EDSM-related queries, abort and reply back with Offline error
• Add a command to automatically trigger an out-of-sequence ONLINE check (and break the loop if successful)
• If able to reconnect, alert in chat and reenable EDSM commands
• Allow cached results to still process, or landmarks/DSSA with coordaintes (see #79)

[Rixxan]

In GitLab by @rik079 on Sep 18, 2021, 18:34

I think a much better and definitely a more elegant solution would be to add this in as part of a new, ABC based method that would allow objects to get notified of online/offline status either immediately or by checking a variable.

Will link to this issue from there, closing for now.