Andrew

Works great now, thanks!

Huh, I'm still getting this error on macOS, even after updating `steam-user` and `steam-client`. Node v6.3.1, NPM v3.10.3 (Node v6.11.0 and v8.1.3, and NPM v3.10.10 and v5.0.3 aren't working, either). Error: ENOENT: no such file or directory, uv_chdir at Error (native) at Object.<anonymous> (/Users/amd/Desktop/Programming/JavaScript/csgo-trading/node_modules/steam-user/node_modules/steam-client/node_modules/mckay-steam-resources/steam_language_parser/index.js:8:9) at Module._compile (module.js:541:32) at Object.Module._extensions..js (module.js:550:10) at Module.load (module.js:458:32) at tryModuleLoad (module.js:417:12) at Function.Module._load (module.js:409:3) at Module.require (module.js:468:17) at require (internal/module.js:20:19) at Object.<anonymous> (/Users/amd/Desktop/Programming/JavaScript/csgo-trading/node_modules/steam-user/node_modules/steam-client/node_modules/mckay-steam-resources/index.js:83:1) My source tree for `steam-user` (as that seems like it might be part of the issue): ├─┬ [email protected] │ ├── @doctormckay/[email protected] │ ├── [email protected] │ ├── [email protected] │ ├── [email protected] │ ├─┬ [email protected] │ │ └── [email protected] │ ├─┬ [email protected] │ │ └── [email protected] │ ├─┬ [email protected] │ │ └── [email protected] │ ├── [email protected] │ ├─┬ [email protected] │ │ ├─┬ [email protected] │ │ │ ├── [email protected] │ │ │ └── [email protected] │ │ ├─┬ [email protected] │ │ │ ├── [email protected] │ │ │ ├─┬ [email protected] │ │ │ │ └── [email protected] │ │ │ ├─┬ [email protected] │ │ │ │ └─┬ [email protected] │ │ │ │ ├── [email protected] │ │ │ │ └── [email protected] │ │ │ ├── [email protected] │ │ │ └── [email protected] │ │ └─┬ [email protected] │ │ ├── [email protected] │ │ ├─┬ [email protected] │ │ │ └── [email protected] │ │ ├── [email protected] │ │ ├─┬ [email protected] │ │ │ └─┬ [email protected] │ │ │ └── [email protected] │ │ ├─┬ [email protected] │ │ │ ├── [email protected] │ │ │ └─┬ [email protected] │ │ │ └── [email protected] │ │ ├── [email protected] │ │ └── [email protected] │ ├─┬ [email protected] │ │ ├─┬ [email protected] │ │ │ └── [email protected] │ │ └─┬ [email protected] (git://github.com/doctormckay/node-steam-resources.git#823bb2546bb2107117bb2fe34c69341ca5d540ca) │ │ └─┬ [email protected] │ │ ├─┬ [email protected] │ │ │ ├── [email protected] │ │ │ └── [email protected] │ │ ├─┬ [email protected] │ │ │ ├── [email protected] │ │ │ └── [email protected] │ │ ├─┬ [email protected] │ │ │ ├─┬ [email protected] │ │ │ │ └── [email protected] │ │ │ ├── [email protected] │ │ │ ├─┬ [email protected] │ │ │ │ └─┬ [email protected] │ │ │ │ ├── [email protected] │ │ │ │ └── [email protected] │ │ │ ├── [email protected] │ │ │ └── [email protected] │ │ └─┬ [email protected] │ │ ├── [email protected] │ │ ├─┬ [email protected] │ │ │ ├─┬ [email protected] │ │ │ │ └── [email protected] │ │ │ └── [email protected] │ │ ├── [email protected] │ │ ├─┬ [email protected] │ │ │ └─┬ [email protected] │ │ │ └── [email protected] │ │ ├─┬ [email protected] │ │ │ ├── [email protected] │ │ │ └─┬ [email protected] │ │ │ └── [email protected] │ │ ├── [email protected] │ │ └── [email protected] │ ├── [email protected] │ ├─┬ [email protected] │ │ └── [email protected] │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected]

The `429` error means "Too Many Requests", but if you changed the server and IP address, I don't know what could be causing this. More info on the `429` HTTP error here: https://httpstatuses.com/429

There are many ways of doing this. One way would be to use MySQL or MongoDB to create a queue for the bot to send. This queue might contain the items to send, the SteamID of the person to send it to, and their token. Then, the bot will poll the database every X seconds to check if there's a new trade offer to send, and, if there is, send it. Websites that I've made use MongoDB to do just that. Another, cleaner, and faster way to do this would be to use Socket.io to emit the trade offer to send just like above. The downside to Socket.io, however, is not having a queue which would build up while the bot is offline, or serve as a log. You could also go with the straight PHP route, using waylaidwanderer's PHP-SteamCommunity.

I really like this idea. Having the option to use your trade URL would mean less parsing and cleaner code on the server/bot side.