Dr. McKay

You should be able to send messages to non-friends if you're in a group chat with them, but that's about it I think.

There's no concurrency concern with sending offers, but if you send offers too frequently (or you send too many offers) then Steam will start limiting you. You're limited to 30 total active outgoing offers, and 5 active outgoing offers to the same recipient. There are also request rate-limits.

The createOffer method doesn't do anything on the network. It just creates a new object in memory, which you can add items to and set properties on. Nothing of value actually happens until you call offer.send(). So that means you can call createOffer as many times as you want. You could call it a million times in a second if you wanted and nothing would break. Of course, sending offers that frequently isn't gonna work.

Just offer.message.

That's just one of those Steam errors that happens. Slowing down may help, and it may not.

community = new SteamCommunity(); community.login({"accountName": "username", "password": "password", "twoFactorCode": "ABCDE"}, (err, sessionID, cookies, steamguard, oAuthToken) => { if (err) { throw err; } community.getUserInventoryContents("[U:1:46143802]", 730, 2, true, (err, inventory) => { if (err) { throw err; } console.log(inventory); }); });

Please read the documentation. It's fairly straightforward.

You can't do it with node-steam-user. You'll want node-steamcommunity to do that.

steam-tradeoffer-manager uses this API: https://lab.xpaw.me/steam_api_documentation.html#ISteamEconomy_GetAssetClassInfo_v1

I can't really support modules I didn't write, but to be sure the problem isn't with my module, I need more information. Anytime you get an error, give the entire output.

The item.fraudwarnings array contains the item's fraud warnings. If you want to see if there an exists an item in that array which literally matches "This item has been renamed", you can use item.fraudwarnings.includes("This item has been renamed") The problem is that typically, that isn't the exact text. Usually items which have been renamed also include their original names in the fraud warning. In this case, you'll need to loop the array and use includes on each entry.

As per the documentation, if you pass a node-steam-user instance to the constructor, then you will get real-time notifications if an offer you sent was accepted, provided you received items in that offer.

You can only relog while connected. If you're not connected, you need to login again.

Need more detail. Please show the entire output, and your code.

You can create an offer and use getUserDetails. If the token is bad, it will error.

Because they can't get API keys, and this module needs to use the API.

Guess what? As per the documentation, limited accounts don't work.

As per the documentation, it only cancels offers as the result of a poll, so the actual cancel time is whatever you set it to +/- your poll interval.

Show your code and the entire output.

That's my bad, sorry. Update to 3.32.2.

Please read the documentation. An error event is emitted if there's a problem logging on. Also, you should under no circumstances be collecting credentials from users.

Worked fine for me. Note that it won't do anything if you already own those apps.

If you're asking how to check if the bot is connected to Steam, check if user.steamID is not null. If you're asking how to check if the web session is still valid, node-steamcommunity has some stuff for that.

I'd need to see how you're saving it, but it's not unlikely that the cookies are just expiring.