Dr. McKay

Are you up to date?

No, there's a device ID parameter in the URL for all confirmation HTTP requests. As I said, if you're using my libraries then they transparently take care of it for you.

Well I mean, you have to do both.

I don't imagine there's a massive difference unless you're doing heavy overhead tasks.

That error means that your account is limited. Steam was incredibly, incredibly broken yesterday and the night before and was limiting people it shouldn't have been. If your account shouldn't be limited, then try logging into it from a real Steam client, then restart your bot.

Yes, that works.

To be more specific (and I should really make some kind of wiki with this information), classid and instanceid are used to identify a description, not an item. A description is the item's display information. Two identical items will most likely have identical classid/instanceid; this means that using classid and instanceid to track a specific unique item really won't work.

It would be like trying to use a car's make, model, and color to track that unique car. Sure you'll get close, but you won't always find that exact car. You want its license plate or VIN for that (assetid).

I haven't seen any issues like this. What's your polling interval set to?

Can you attach a listener to the "debug" event and print that to the console?

manager.on('debug', console.log);

Yeah making your bots separate from your site is probably your best bet.

var offer = manager.createOffer("[U:1:46143802]");
offer.addMyItem({"appid": 440, "contextid": 2, "assetid": "1234567890"});
offer.send("Hi there", "KYworVTM", function(err, status) {
    if (err) {
        console.log(err);
    } else {
        console.log("Offer #" + offer.id + " " + status);
    }
});

Something like that, where [u:1:46143802] is my SteamID and KYworVTM is my trade token.

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.