fatal error clarification.

[rsyhg7]

Hi,

I'm going through the steam-user documentation and had some questions with the "error" event emitted.

Quote

Emitted when an error occurs during logon. Also emitted if we're disconnected and autoRelogin is either disabled, or it's a fatal disconnect.

If I leave autoRelogin enabled and my instance receives a fatal disconnect. Should I try to relog myself when it regains connection to steam or will the package automatically attempt relogs without me needing to?

[Dr. McKay]

If error gets emitted, the SteamUser instance is done doing anything until you manually log it back on. Steam outages are not fatal disconnects, and if autoRelogin is left enabled then error will not get emitted when Steam goes down. Fatal disconnects are things like InvalidPassword, AccountLoginDeniedNeedTwoFactor, RateLimitExceeded, or LoggedInElsewhere.

Essentially anything that isn't Fail, NoConnection, ServiceUnavailable, or TryAnotherCM is fatal.

Edited January 14, 2021 by Dr. McKay

[rsyhg7]

Ok,

Whenever steam goes down for maintenance on Tuesdays and I'm using a proxy to connect to steam I frequently get the error event sent out.

Thanks for the confirmation!

[Dr. McKay]

I would guess that's because the proxy isn't able to connect so it throws up its own error.

[rsyhg7]

On 1/14/2021 at 6:17 PM, Dr. McKay said:

I would guess that's because the proxy isn't able to connect so it throws up its own error.

Yes, I can confirm steam just went down and I was able to confirm this is the cause of the fatal error being thrown.

When steam goes down I got a disconnection event of "3 NoConnection" then a few seconds later I got thrown the fatal error of "Proxy connection timed out".

Is there a way I can test proxy connection with steam before trying to relog?

[Dr. McKay]

Not really. I guess you should handle the error event, check whether the error message is about your proxy, and if it is then retry a few times and abort if it can't reconnect after a bunch of attempts.