Dr. McKay

Most people use the steamcommunity.com JSON inventory endpoint: https://steamcommunity.com/profiles/STEAMID/inventory/json/730/2/node-steamcommunity has a method for this. Example: community.getUserInventory("[U:1:46143802]", 730, 2, false, function(err, inventory) { console.log(inventory); });

I believe this is caused by your calling checkConfirmations without having started the confirmation checker first. This isn't supported behavior. Do you want it to be?

It's the "region code" assigned to you by Steam. Changing it is useless.

I want to know what you're using node-csgo for.

Please update to steam-user v3.10.0 and this should be fixed.

Sure thing.

That looks fine to me.

It was, he's probably still on v1 for whatever reason.

Sounds like it's neither failing nor going into status "sent". As you're sending items, the offer requires confirmation and so the status will be "pending".

Can I ask what you're trying to do with it?

Yes, it's because you're friends. The trade URL is wrong.

You need to do it yourself.

You're treating the symptom and not the problem if you do that. The problem, as given by the HTTP status code, is that you're making too many requests. Slow down.

I'm pretty sure it means that you've made too many requests in a short time, and consequently your IP has been temporarily blocked.

They should.

You... recheck it again later.

I throw Errors in steam-user when you do something that you just shouldn't. For example, there are no cases where you should be trying to log on when you're already logged on. An Error being thrown basically means that you failed a precondition. For example, in the case quoted here, you need to check if you're already logged on before you attempt to log on again.

Client = new CMClient(), GC = new SteamGC(client, 730); See a problem in the capitalization here?

My mistake, update to v1.1.1 and this is fixed.

Are you getting some kind of error?

Whoops. That should be fixed in 3.9.1.

There's nothing in there that would spam requests. Note that it's an IP limit. It can be anything on your IP that is spamming requests.

Trade offer ID? Yes, it's possible. You'd just need to request your confirmation list then get details for each individual one until you found the matching offer ID.

1. If you want to get all active offers and that's it, you'd use this: { "get_sent_offers": 1, "active_only": 1, "time_historical_cutoff": 2147483647 } 2. You'd check the trade_offer_state. If they accepted it then they received the item you sent them. 3. If you want all offers from a time period you'll need to just leave out both active_only and historical_only and filter the result.

Because you're adding a new listener every single time you request item info. Just use the callback and you won't need to worry about it.