Dr. McKay

Some people are working on maintaining a list of rate-limits here: https://www.reddit.com/r/SteamBot/wiki/rate-limits

You're logging in anonymously, because you're using account_name instead of accountName.

You can't use the same 2FA code twice. That means that effectively you can't login twice within 30 seconds.
 
That said, you don't have to. SteamUser will give you login cookies you can use with SteamCommunity.
client.on('webSession', function(sessionID, cookies) { community.setCookies(cookies); });

The easiest way to determine which game a community item belongs to is to check its market_hash_name. All cards/emoticons/backgrounds have their market_hash_names prefixed with the game's appid and a hyphen (e.g. "440-SCOUT").

Are you logged in?

You're overwriting the value of steamID in your outer loop, which changes the context of the closure. This is confusing, I know. Just do this and it should work:
bot.on('friendsList', function() { Object.keys(bot.myFriends).forEach(function(steamID) { if(bot.myFriends[steamID] === 2) { bot.getPersonas([steamID], function(getName) { var friendName = getName[steamID].player_name; //Some code }); } }); });

https://github.com/DoctorMcKay/node-steamcommunity/blob/master/components/users.js#L345

https://steamerrors.com/26

I've been investigating this for the past hour and a half or so, and it appears that Valve did indeed break something with client-based web logons last night. The API is giving quite a lot of 403s with the same error message that you get if you use a bad nonce. Therefore, my suspicion is that there's some kind of miscommunication between the CM (the server which most likely generates the nonce and issues it to you), and whichever server consumes those nonces to turn them into cookies. I've tried adding some delays just in case the communication between those servers is slow, but that doesn't appear to have helped anything.
 
Re-logging your client seems to solve the problem, at least temporarily. You may want to try doing that if you don't get a web session within a reasonable amount of time after requesting one.
 
I've alerted Valve, but there's no telling if or when they'll take action.

Best I can tell, web logons became finnicky ever since the Steam maintenance last night.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#properties
 
itemsToReceive

https://www.npmjs.com/package/steamid
var SteamID = require('steamid'); var steamid3 = (new SteamID(steamid64)).steam3(); If you want the accountID and not the Steam3 rendered format as your title implies ([u:1:46143802]) then you just want to do:
var SteamID = require('steamid'); var accountID = (new SteamID(steamid64)).accountid;

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#getreceiveditemsgetactions-callback

After some time having trouble with it (as I am new), I got it to work! Thanks so much dude! for everyone else wondering.. I used this:
client.on('friendMessage', function(steamID, message) { friendID = [steamID]; client.getPersonas(friendID, function(getName) { var x = getName[friendID]; var friendName = x.player_name; console.log("[FriendlyMessage] " + friendName + ": " + message); } }); Brackets could be wrong because my code didn't stop there and I am correcting it within the text editor
 
I do have another question and I don't know if I should ask it here?
But, what are the numbers for friendrelationships??
I know 2 is friend request send to me. But where can I find it.. because I am having trouble finding everything...   
 
EDIT: After actually turning my brain on.. I checked within the files of your node and found a file with the numbers.... Shit I'm stupid... Thanks anyway!! GREAT SHIT DUDE!!!

Don't do it that way, that's a very bad idea. Write the entire 64-bit number to the buffer.

Okay, here's the flow of how this works:
CS:GO client sends a GCStorePurchaseInit to the GC with the items you want to buy You get back a GCStorePurchaseInitResponse containing a result (1 = OK) and a transaction ID (64-bit, even though it can currently fit into 32 bits) Concurrently, you get a ClientMicroTxnAuthRequest message via Steam. Discard the first byte of the payload (seems to be 1 in the dump you sent, not sure if that's always the case or what the significance of it is), then decode the remainder of the payload as Binary KeyValues (require('binarykvparser').parse(payload.toBuffer().slice(1))). The interesting stuff in there is the total/BillingTotal and transID (orderid is there if you want to make sure it matches what the GC sent back). Grab the transID and send it back in ClientMicroTxnAuthorize (little-endian encoded, as always) and append a 32-bit value of 2 (unsure what the significance of this is, or if it ever changes from 2. Could perhaps be an authorization result, where 1 is deny or something). You'll get back ClientMicroTxnAuthorizeResponse with a payload containing a 32-bit eresult value (1 = OK), and a 1-byte unknown value of 0. If successful, If successful, send GCStorePurchaseFinalize to the GC containing the transaction ID you from the GC before (not transID) to get your items.

Remove listeners if you're done with it. But it being emitted is an indicator that something is still trying to do something even when you've logged off.

There is no way to do this. You can parse the CS:GO item schema that ships with the game, but I don't believe it'll get you what you want.

On your local PC it should be your private IP, but not 127.0.0.1.

It usually helps to print out values of variables when debugging. In this case, I suspect one of appid, contextid, or assetid is undefined or not the value you are expecting.

Data types shouldn't matter. The module should convert everything internally for you. Are you absolutely sure you're using asset IDs which are owned by the account you're logged into? Maybe you mixed up some accounts?

Your asset ID is still wrong.

Yes, the assetid is the "id" property there.

You can use this to accept all outstanding confirmations at once, but the entire request will fail if any one confirmation fails to be confirmed.

That will create a new interval every time your session expires. Either use setTimeout or create the internal outside of that event callback.
 
Also, you may want to listen for the sessionExpired event.