Dr. McKay

^^^ https://steamerrors.com/26

You have to provide a callback.

There are examples in the repository. If you don't know what events are, I suggest that you learn more about Node before trying to undertake this.

The sentOfferChanged event will be emitted when an offer you sent is accepted or declined.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/releases/tag/v2.0.0-beta1

No, images for two items with identical classid/instanceid pairs (which is not uncommon) will be identical. Plus I believe it can change from time to time unpredictably.

Unfortunately there isn't. You'll need to just avoid moving two items which might get mixed up inside of one trade.

You're trying to invite people to TeamSpeak through Steam?

The problem with this is that I'm about 99% sure that you need to actually be "in" a server in order to invite someone to a game, unless it's a Steam lobby. And "joining" a server is a non-trivial task.

Don't worry about poll failures unless you aren't getting any successful polls at all. Failures will happen.

I'm not very familiar with Dota, but as far as I know TF2 and possibly Dota are the only Valve games where IEconService gives enough useful information to build an item's display information. For everything else, you need to use inventory JSON. Attributes are only a concept in Valve-land; the Steam econ server has no concept of "attributes". Consequently, attribute data doesn't translate to the inventory JSON. Attributes are just that: attributes attached to an item. For example in TF2 an attribute might change how much damage the weapon does. In CS:GO, wear is an attribute. IEconService has no classids because again, it has no concept of classids. They're entirely assigned by and used by the Steam econ server, and consequently they're only available in the econ endpoints (like inventory JSON and GetAssetClassInfo).

I purposefully didn't mention the WebAPIs because they aren't really "Steam items". They're "Valve items", and third-party games don't need to follow any of the same standards. However, for Valve games, the "id" in the WebAPI is the item's asset ID, and "original_id" is the item's asset ID when it was originally created. If it's identical to the item's "id", that means that the item was never traded or modified. Quality (generally) determines the color of the item's name, and (sometimes) a prefix to the item's name (for example, StatTrak, ★, etc). Quality has nothing to do with wear. For CS:GO, you can't really get much useful information out of the WebAPI except an item's raw wear value (frequently, incorrectly, and ignorantly referred to as its "float value") and perhaps original ID.

Don't do this. Timezones don't matter.

I can't help in any way with C#.

The trade receipt page contains the new item data. If you're using node-steam-tradeoffer-manager, you only need to use offer.getReceivedItems.

Use offer.getReceivedItems, which will contain the new asset IDs of those items.

Check if itemsToGive.length is 0, and itemsToReceive.length is greater than 0. If both tests pass, then accept the offer. Make sure you check both, as both itemsToGive and itemsToReceive could be empty when the Steam econ server is acting up, even though you might be giving items in that offer.

That error means that either your secret is wrong or your clock is wrong. If you're using the same code and the same secret on both machines, then the time must be wrong on the VPS.

If you're being redirected to login, then you pretty clearly aren't logged in.

Make sure your "output log" is capturing stdout.

Please answer my questions.

Is this module the entry point for your application? What output are you getting?

Well, you wrapped everything in a "login" function. Call that.

You have to actually call logOn to connect to Steam and log on.

Please read this guide and let me know if you still have questions.