Dr. McKay

Using setInterval will make it automatically call webLogOn every 30 minutes (with your configuration). If you call setInterval more than once, it will call webLogOn more than once every 30 minutes.

I don't know exactly what limitations are placed on loginKeys, sorry. I've never really looked into it. loginKeys are what the Steam client uses when you check the "remember my password" box to automatically log you back in every time you restart Steam. Web logon tokens aren't useful for this purpose since they are only good for a few minutes.

Yes, you should put that outside of any callback. It should only ever be called once. Also, there's no use in nesting it inside a setTimeout.

Every time you get a new web session, you're starting a new interval to call client.webLogOn(). So after a half hour, your web logon rate has elapsed 6 times and now you're calling client.webLogOn() 6 times every 30 minutes.

Check out rememberPassword and loginKey.

You should probably attach a callback so you can see if there was an error.

What is there to fix? If you're trade banned you aren't necessarily community banned.

https://github.com/DoctorMcKay/node-steamcommunity/releases/tag/v3.41.1

Either your clock is wrong or your secret is wrong.

It cannot be added to steam-user. Sorry. You don't need to call getSteamUser to use this method. Just call community.sendImageToUser(steamID, imageBuffer, options, callback).

Your shared_secret is retrieved from enabling mobile two factor using steamcommunity. If you don't have a mobile authenticator enabled on your account, then you can't use generateAuthCode and you need to get a code from your email instead.

https://github.com/DoctorMcKay/node-steamcommunity/releases/tag/v3.41.0

Those are system messages, not chat features. You can't send them yourself. No, you would lose all new chat functionality.

Steam's probably having an issue.

In the user event (or getPersonas), user.persona_state == SteamUser.EPersonaState.Away tells you if their status is set to "Away". And you can check if user.game_played_app_id is truthy to see if they're in-game.

So this is happening because JavaScript is single-threaded, and your loop is taking too long. While the loop is running, the rest of the code can't keep the connection to Steam alive and do other housekeeping tasks. You'll need to figure out a way to get the time that loop takes down, perhaps by limiting how many items it will process at a time, or perhaps by using setImmediate periodically so the rest of the event loop can get processed.

The first argument to client.chatMessage needs to be the SteamID of the user to whom you're sending the message.

I have no idea what trips that, but running a bot doesn't seem to have a significant impact on it.

You may run into problems with confirmations not appearing if you use two different solutions to confirm trades. But otherwise, it should work alright. I'm not sure I understand what you're asking here. If you create an account but don't enable a mobile authenticator on it, it'll work fine but it won't be able to trade without 15-day trade holds.

If you don't want to use the mechanisms built into steam-tradeoffer-manager, then you'll have to call GetAssetClassInfo yourself.

If you pass a language to the constructor, then item descriptions (including name) will be set. tradable is false if you don't have a language set because an item's tradability is part of its description, which isn't loaded if there's no language set. It would probably be a good idea if I deleted those properties for items that don't have descriptions available, I guess.

403 usually means your IP got temporarily blocked. You need to tone down the requests you make, especially to inventories. And don't use the confirmation checker.

This is a known issue. I haven't gotten around to adding proper support for showcases yet.

They're the same thing.

Asset IDs generally won't change if an item is just sitting in your inventory. They will change (for Valve games) if they are "changed" somehow (e.g. renamed in-game) or if they're traded away. Note that in some circumstances, a trade offer can be sent and accepted, but the actual item exchange might fail and Steam might roll back the trade. If this happens, some (but not necessarily all) of the items in the trade will have their IDs change.