Dr. McKay

You can use node-steamcommunity for that: https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#editprofilesettings-callback

You're correct. I'll update that now.

Wow that was a quick fix, thanks a lot

Added in v2.1.0.

It's a planned feature for globaloffensive, but I haven't gotten around to adding it yet.

I don't see any reason why that should be the case. The only reason I could figure that would happen is that it doesn't clean up some timer or something, but every instance where it emits error, it also calls _disconnect, which cleans up after itself.
Do you know what particular error code(s) cause this?

The modules may work without the peer dependencies, or you should just install them yourself manually with npm install.

This logic will be written in the constructor. Something like this :
constructor(accountName) { this.setCookies = util.promisify(this.manager.setCookies).bind(this.manager); this.user.on('error', this.logOut); this.user.on('loginKey', loginKey => db.findOne('bot', { accountName }, { loginKey })); }  

The CM sends a notification message to the Steam client (which steam-user can receive), but that message only contains the count of pending trade offers. To get any details at all about the actual content of the trade, we need to hit the API for that.

It's very much not a bad idea to spawn one process per account. That way, if something causes one bot to crash, the rest don't also crash. Also, Node.js is single-threaded, so that's the best way to take advantage of multiple processor cores.
About the only downside of spawning multiple processes is the increased memory usage. But if you have enough RAM, go for it.

It's very much not a bad idea to spawn one process per account. That way, if something causes one bot to crash, the rest don't also crash. Also, Node.js is single-threaded, so that's the best way to take advantage of multiple processor cores.
About the only downside of spawning multiple processes is the increased memory usage. But if you have enough RAM, go for it.

appid, contextid, assetid, classid, instanceid, amount, name, market_name, market_hash_name See this guide id Same as assetid pos Not always present; this is the item's position in the user's inventory (starting at 1) background_color Hex code for the background color rendered for this item in the Steam inventory name_color Hex code for the name and border color rendered for this item in the Steam inventory icon_url Append this to https://steamcommunity-a.akamaihd.net/economy/image/ to get the item's image descriptions Array of objects containing human-readable description text lines tradable, marketable Self-explanatory type The text that goes under the game's name to the right of the square game logo in the Steam inventory when this item is viewed commodity Determines whether this item's Market listing uses buy orders exclusively (true), or individual listings with the possibility to submit buy orders (false) market_tradable_restriction Length in days that this item will be untradable after it's bought on the market market_marketable_restriction Length in days that this item will be unmarketable after it's bought on the market tags Array of tag objects; tags are used in the Steam inventory for filtering is_currency Always going to be false except for some Spiral Knights stuff (I think). You really don't want to deal with currencies, trust me. fraudwarnings Array of warnings that will be rendered in red when this item is viewed. If fraudwarnings exist, the item gets a red (!) icon in the Steam inventory

You're not meant to use the method I gave in conjunction with the confirmation checker. 
The confirmation checker (in simple terms) works by telling Steam every X seconds: "Hey, I wanna confirm everything waiting to be confirmed". It will tell steam even if there is nothing waiting to be confirmed thus the load it puts on servers - imagine loads of bots doing this. 
Whereas the method I put tells steams servers: "Hey, I wanna confirm this specific trade". Therefore, it only tells steam when there is something to be confirmed. 

Using a confirmation checker puts unnecessary load on steam's servers. 
 
After receiving or sending a trade offer, obtain the offer's ID and then call this method:
community.acceptConfirmationForObject('YOUR_IDENTITY_SECRET', 'OFFER ID', (err) => { if (err) { console.log(err); } // code here })  

I'm not sure I believe you.

https://www.npmjs.com/package/steamid

Yes, that's what the code I posted is for.
Yes, yes, yes.

You don't need to log into the client to send or receive trade offers, no.
You can use a proxy like:
 
const SteamUser = require('steam-user'); let user = new SteamUser({ httpProxy: 'http://user:[email protected]:5678' });  

I'm sorry, I don't think I can really help you much more with this. I haven't seriously touched any GC-related code in a good while, and the most I could do is experiment, which it seems is what you're doing anyway.

const SteamID = require('steamid'); const URL = require('url'); let link = 'https://steamcommunity.com/tradeoffer/new/?partner=46143802&token=aaaaaaaa'; let steamid = SteamID.fromIndividualAccountID(URL.parse(link, true).query.partner);  

https://github.com/DoctorMcKay/node-steamcommunity/wiki/SteamCommunity#sessionexpired

I guess you should confirm your email.

By sleeping synchronously, you're preventing the module from actually sending the message over the network. You should almost never sleep synchronously in JavaScript.
You're looking for the setTimeout function.

I suppose theoretically it would be possible if you used a bot to get some new cookies for steamcommunity.com, then requested steamcommunity.com/chat with those cookies and proxied the response back to the browser.

https://steamerrors.com/15