Dr. McKay

The unix timestamp in the second screenshot is the current time when the message was printed?

Using classid/instanceid to track a specific item doesn't work anyway.

Clusters are designed for applications which have to process lots of things at once (like many user requests). Running bots is really not a good use for clusters. I'm personally running 30 bots within the same node process on low-end VPSes and the only problems I'm having are Steam IP limits.

How many bots are you running?

Can you add timestamps?

It gets fired automatically after logon. Maybe it got disconnected from Steam (today is Tuesday, after all), reconnected, and then the event fired.

Only if you set up your bot to automatically accept all trades.

If you don't know how to work with a database from node, you should probably start with an introductory course.

If err is defined, the offer will never have an ID. Sometimes an offer can actually go through after send() gets an error, but that's just Steam and there isn't any real way we can track that. What I'm saying is that if err isn't undefined, then Steam told us that the offer failed to be sent. If it actually got sent, it'll appear in the API later but you won't have its ID as Steam didn't give it to us when we sent it. That's where the unknownOfferSent event comes in.

It isn't emitted by the error event, no.

Yes, you need to spend $5 in order to remove limitations on the account. This is necessary if you plan to add friends or use the WebAPI (e.g. for trade offers) on the account.

Fair enough. How about an offerList event that's emitted every time we do a full-update poll?

Any new Steam account will be unable to trade entirely for 15 days, since you need SG enabled for 15 days in order to trade. A sentry file is how Steam remembers a "device" for Steam Guard. You'll get sent one when you login without one, and you should save it and use it for subsequent logins. node-steam-user does this for you. You can't bypass the 15-day waiting period for Steam Guard. Trade holds (which last for 15 days) can be disabled by enabling the mobile authenticator. Once the mobile authenticator is enabled, after you wait 7 days, trade holds go away. You can wait out the 7 days at the same time as the 15 days. So the quickest way to get a new Steam account tradable is to verify its email and immediately enable the mobile authenticator. Once done, it will be able to trade in 15 days.

Please update.

I ask if you're up to date because Steam can sometimes return data that implies that the offer is completely empty (no items on either side). A recent update made the getOffers request fail instead of returning that bad data.

Is itemsToGive for sure bigger than 0? Also are you up to date?

I don't understand what you're saying.

It still does some manual polls when you disabled timed polling.

You must have, or they obtained it from another source where you previously shared it.

Yes, a TradeOffer object has a confirmationMethod property as you describe. The value of that property is different for each party in the trade. If you're the sender, then it's populated on send. A nonzero value in state CreatedNeedsConfirmation means that it's waiting on you to confirm it. A nonzero value in any other state means that you were required to initially confirm it using that method, but no further action is required on your part. On the recipient's side, a zero value in state Active means you haven't tried to accept it yet. A nonzero value in state Active means you need to confirm it using that method before the offer can be accepted. A nonzero value in any other state means you previously had to confirm it using that method.

You'll want to prompt the user for their trade URL, then use the token from that URL to authenticate the trade offer.

What version are you running?

I'm assuming that you're asking whether or not Steam stopped paginating inventories? Steam paginates after 2500 items. Here's an example.

Player 1 creates a trade offer and sends it to Player 2. Player 1 needs to confirm it: offer state is CreatedNeedsConfirmation and it's invisible to Player 2. Player 1 confirms the trade. It goes into state Active and both players can view it. Player 2 accepts the trade. It requires confirmation, but stays in state Active. Once accepted, the API for Player 2 says that confirmation_method is either 1 or 2 (previously 0) depending on email or mobile confirmations. Player 2 confirms the trade. It changes into state Accepted.

I'm not sure we're on the same page. Allowing the usage of a trade URL wouldn't remove the ability to use a SteamID and token separately.