Dr. McKay

Don't install it globally.

I don't know the specific number.

There might be some confusion here. The expires property is Steam's expiration date, which is always 14 days from creation time and can't be changed. cancelTime works independently of it.

I started working on that some time ago but I had to put it on hold. Maybe I'll get around to it soon. Pull requests are always welcome.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager#sentofferchanged https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager#receivedofferchanged

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

The limit is higher than 2 per minute.

I... I don't even know what you did here. Did you copy the implementation from the code and paste it? Why??

Using a bunch of sockpuppet accounts to fake votes sounds like a good way to get yourself banned.

I think that's a very, very bad idea.

I don't think bot-voting is a terribly great idea.

Yes, it is always a bad idea. You should check the item's name to see if it's a key.

https://www.google.com/search?q=node.js+screenshot&ie=utf-8&oe=utf-8

All you have to do is call startConfirmationChecker first. You can do it synchronously.

You don't want to use instanceid to identify a type of item. See here: https://dev.doctormckay.com/topic/332-identifying-steam-items/

It does take the cookies, but calling manager.setCookies is still important as that's when it grabs the API key.

I'm not sure I 100% understand. Let me clarify a couple things. SteamTrades is what you get back from require('steam-tradeoffer-manager'), yes? Are you calling manager.setCookies anywhere? What's your console output?

There isn't.

You'll have to ask them how they do things.

You can't get the new item IDs for sent items, no.

It's unfortunately not possible. getUserDetails just loads the offer UI page, which is inaccessible once you're unable to act on the offer (e.g. you send it [outgoing] or you accept it [incoming]).

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.