Dr. McKay

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.

Because that's how it works.

setCookies makes exactly one request (two if you supply a Family View PIN). It isn't setCookies' fault. You're making requests elsewhere too quickly.

429 means that you've sent too many requests to Steam in a short time and you need to slow down.

There's a reason why you can't supply your own API key. The key it uses must be associated with the Steam account you're using. You can't use another account's key. If your account is limited, you'll just have to pay $5.

node-globaloffensive is using an option where instead of underscores, you should provide protobuf fields in camelCase. Basically, just remove the underscores and capitalize the next letter. However, I've added that functionality in v1.1.0.

Your crash log gist 404s.

WebStorm sometimes has trouble resolving Node dependencies. Do you have the Node.js plugin installed in WebStorm?

Right.

Sounds right.