Dr. McKay

You're accepting offers very wrongly. First, remove the offer.accept(...) around your call to your own accept function. Second, passing offer.accept to setTimeout like that will cause problems because the this reference is lost. For example: function TestObj(name) { this.name = name; } TestObj.prototype.printThis = function() { console.log(this); }; let obj = new TestObj('foobar'); obj.printThis(); setTimeout(obj.printThis, 500); Prints this: TestObj { name: 'foobar' } undefined The reason this happens is because this is set to the reference of the object on which the method was called. So when you call obj.printThis(), the this reference is to obj. But when you pass obj.printThis to setTimeout, what setTimeout sees is something like: function setTimeout(callback, delay) { wait(delay); callback(); } As you can see, when callback is called (which is obj.printThis in this case), there is no object reference on which it's called, so this is undefined. If you want to pass offer.accept to setTimeout like that, you'll need to bind it like this: setTimeout(offer.accept.bind(offer), delay)

https://github.com/DoctorMcKay/node-steam-user#datadirectory

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager#getoffersfilterhistoricalcutoff-callback

No planned date yet.

Sounds like a plausible explanation.

Just remove the whole startConfirmationChecker line. There's no need to confirm anything if you're never losing items.

Looks like your web session is expiring and your app is coded in such a way that that causes a crash.

Sure. If your database is MySQL, you can use the mysql module.

Download it and drop it into node_modules.

Instead of comparing relationship to a number directly, you should compare to SteamUser.EFriendRelationship.RequestRecipient. You're firing off the addFriend request but then immediately trying to send a chat message and post a comment. Steam sees this as all happening at the same time, and wouldn't have processed your add-friend request when you try to post the comment. You need to wait for friendRelationship to get emitted again, this time with relationship Friend.

https://github.com/DoctorMcKay/node-steam-user#requestfreelicenseappids-callback

https://github.com/DoctorMcKay/node-steam-user#user

Once an account is banned, it's banned for good. You can't just change the phone number and get it unbanned. I also wouldn't use that same phone number anymore since it's now "tainted".

That shouldn't be possible, no.

All accounts linked to a phone number are banned if any account linked to that number is banned. No other criteria matter.

Why not use node-steam-user?

Absolutely. If any account gets banned, all accounts with the same phone number get banned.

No. If you want to know whether two players traded items or not, you'll need to poll both players' inventories and check to see if the item(s) disappeared from player A and appeared in player B.

I meant v4. You could install it directly from Git if you wanted, but I haven't yet written docs for new chat support. The new code is here. To call getGroups for example, you'd do user.chat.getGroups(...)

You're missing the tradableOnly param in manager.getInventoryContents.

The code that's an issue is not in your paste.

You need to remove your friendMessage listener after you get your Steam Guard code, otherwise it tries to login again later with the old details.

If you're absolutely sure that you want to allow MitM, this should work: const Request = require('request'); const SteamCommunity = require('steamcommunity'); let community = new SteamCommunity({ "request": Request.defaults({"rejectUnauthorized": false}) });

offer.accept(function(err) { if (err) { // handle error } });

Have you set the promptSteamGuardCode option to false?