How to keep the bot logged in

[dawe]

Hello!
How do I keep the bot logged in? It logs out after a while. 

Do I just use this:

    this.client.setOption('autoRelogin', true);

Appearently you should use webLogOn() in  the code, but how?

[Dr. McKay]

What do you mean by "logged in", exactly?

[dawe]

1 hour ago, Dr. McKay said:

What do you mean by "logged in", exactly?

Logged into steam

[Dr. McKay]

Logged into the Steam client, or the website?

[dawe]

Steam client

[Dr. McKay]

Once you're connected, it'll just stay connected unless Steam goes down or your network goes down.

[dawe]

What happens is the session expires

[Dr. McKay]

That's not a thing for CM (Steam client) connections. What's the actual symptom you're seeing?

[dawe]

Ok then I may be in the wrong subforum. The symptom is that the Steam bot gets logged out because the session expires and can't send trades anymore after about 15 hours.

Edited Thursday at 05:02 PM by dawe

[Dr. McKay]

Right, that's a web session, not a client session. When you log in to the client using steam-user and receive a webSession event, that's a web session that's started through the client. Those web sessions expire independently of the client session, and you do need to call webLogOn() occasionally to get a new web session.

[Yeezy]

On 10/23/2024 at 6:09 AM, Dr. McKay said:

Once you're connected, it'll just stay connected unless Steam goes down or your network goes down.

It used to reconnect when steam went down right? I think autoRelogin might be broken currently with steam going down.

 

Does the relog function do the same as the autoRelogin option?
https://github.com/DoctorMcKay/node-steam-user?tab=readme-ov-file#relog

 

[Dr. McKay]

I'm not aware of autoRelogin being broken in any way.

Web sessions are completely independent of CM connections. When steam-user is "connected", that's a CM session. A web session is negotiated through the CM session, but they're entirely separate. Web sessions are never automatically renewed by steam-user; that responsibility falls onto you.

[dawe]

Thank you for your help, much appreciated.

 

Would this work: 

this.community.on("sessionExpired", async function (err) {

      if (err) {

        console.log('Session Expired: ' + err);

       

    }

 

      self.client.webLogOn();

      console.log('called weblogon');

   

  });

Edited yesterday at 12:23 PM by dawe

[Dr. McKay]

Yes, that should work. I'd recommend some debouncing to ensure that you don't spam-call webLogOn if multiple sessionExpired events are emitted quickly.