Dr. McKay

You would have to find the modified version of the plugin, or find someone who can modify it for you.

I'm pretty sure that means that you need to verify your email before continuing. You can request a verification email with steam-user.

You should create a new SteamCommunity instance for each account, in which case they don't share anything except your IP address, unless you're using proxies.

@What Comes Around is right, in that case only the last if has the else attached to it. You'd want to either use a switch (preferred in this case), or a chain of else if.

You were missing a single-quote after !Hello, and in both you're missing a closing paren. I don't see any reason why that would send back both messages; you should probably console.log the message to see what it actually is; you might be receiving another message of some type in addition to your !Hello.

The brackets just mean that it's an optional argument. store.addPhoneNumber('+310***', (err) => {}) is the same as store.addPhoneNumber('+310***', false, (err) => {}). If you want to bypass a confirmation, you'd do store.addPhoneNumber('+310***', true, (err) => {}) The callback doesn't have any other arguments besides err.

That code is full of syntax errors, so I suspect you didn't copy and paste the code that's actually running. client.chat.on('friendMessage', (msg) => { if (!msg.message_bbcode_parsed) { return; } let element = msg.message_bbcode_parsed[0]; if (typeof element == 'object' && element.tag == 'tradeoffer') { client.chat.sendFriendMessage(msg.steamid_friend, `You sent me trade offer #${element.attrs.id}.`); } });

Sorry, that's probably not going to be implemented.

Have you read the docs on the new chat? You get a friendMessage event when a new message comes in, which contains an Incoming Friend Message object. For an incoming trade offer, the message is something like: [tradeoffer sender=46143802 id=4087685841][/tradeoffer] But you can see the parsed BBCode in a more convenient format with message_bbcode_parsed, which looks like: [ TagNode { tag: 'tradeoffer', attrs: { sender: '46143802', id: '4087685841' }, content: [] } ]

You can either listen for the tradeOffers event, or listen for chat messages and check for one that contains a [tradeoffer] BBCode.

GC sessions are weird and sometimes they go away without wanting to reconnect. That said, some changes have been made somewhat recently, so make sure you're up to date. If you are, then I suggest detecting when that happens, and using gamesPlayed([]) then waiting a minute or two and launching CS:GO again.

It couldn't be, that error is coming from somewhere else. But that error is definitely indicating that you're trying to reference eresult on something that's null.

Glad you got that sorted!

This means that err is null, meaning there was no error.

err.eresult is just the number, yes.

Is your inventory full, or would accepting the offer put your inventory over the limit?

Node.js actually performs better if you split as much as you can into separate processes, since Node is single-threaded.

getPersonas is a method, not a property.

You don't need to load someone's inventory if you know the asset ID you plan on putting in the trade offer already. Can you determine which line you're receiving the error on? That error could be coming from either manager.loadInventory or manager.loadUserInventory.

You need to wait for the loggedOn event, and you also need to call getPersonas to actually get user persona data.

What's the purpose of loading the user's inventory if you aren't doing anything with the response? Also, I'd like to know what your partner variable actually looks like.

I really wouldn't recommend that you try parsing item attributes and using them to determine what various items actually are. CS:GO is a complete mess and that's a really good way to go insane. You're far better off keeping track of which items are which IDs before you put them in your storage unit. I'm not aware of any storage unit rate-limits, but I do recommend that you wait for an add/remove request to complete before you issue the next one.

There shouldn't be any problems.

That sounds an awful lot like spam.

Take a look at the examples in the steam-tradeoffer-manager repository. It should be fairly trivial to modify the example to accept all incoming offers into one that declines all incoming offers.