If the ArchipelagoClient loses connection, it will call its .disconnect() logic, but there should be a event that gets emitted so application users can see at a moment's notice and react accordingly without having to check the ArchipelagoClient.status property.
A good example is ArchipelagoClient.locations.scout(), ideally would like to await a response from the server with the list of locations we scouted so we can handle them without needing to listen to the locationInfo packet.
Need to also update for ArchipelagoClient.locations.check(). Same deal.