Dr. McKay

Move your client, community, manager, logOnOptions declarations inside of the Bot function.

DigitalOcean is fine. I'd recommend them more now that they've dropped their prices than I would in the past. If you're going with a VPS then you need to read up on security so you don't get pwned.
 
You probably want at least 2 GB of RAM. 1 GB might work but keep in mind that it also needs to support the entire OS too.
 
On a reputable host your files are safe. You don't need to encrypt them unless you're really paranoid, and if you do go that route you can't store the key on the server or it'll defeat the purpose.

let sold = JSON.parse(require('fs').readFileSync('TotalSold.json').toString('utf8'));
sold.TotalItemsTraded.TotalKeys += something;
require('fs').writeFileSync('TotalSold.json', JSON.stringify(sold, undefined, "\t"));

DigitalOcean is fine. I'd recommend them more now that they've dropped their prices than I would in the past. If you're going with a VPS then you need to read up on security so you don't get pwned.
 
You probably want at least 2 GB of RAM. 1 GB might work but keep in mind that it also needs to support the entire OS too.
 
On a reputable host your files are safe. You don't need to encrypt them unless you're really paranoid, and if you do go that route you can't store the key on the server or it'll defeat the purpose.

Sure, just load two inventories and add two items from different games.
Change the amount property on the item. For example:

manager.getUserInventoryContents(steamID, 753, 6, true, (err, inv) => {
if (err) {
throw err;
}

let gems = inv.filter(item => item.market_hash_name == "Gems");
let item = gems[0];
item.amount = 300;
offer.addMyItem(item);
});

The bot thinks this because it's true.

I don't know, sorry.

You're adding an event listener named getTradeURL, not calling a method. community.getTradeURL(...

If you want the steamGuard event to work, you need to set the promptSteamGuardCode option to false.

I don't think anyone knows an exact limit but I think you should be safe if you keep it to 1 second between trade sends. As long as you aren't perpetually sending trades at that speed, you should be fine.

Are you up to date?

Did you supply a language to the constructor?

I don't believe so.

https://github.com/DoctorMcKay/node-steam-user#gamesplayedapps-force

Sounds like Valve's tired of people creating spam bots.

Most likely it just won't let you redeem the key if you already own everything in the package it would grant you.

socket.io is okay but I don't personally recommend it because I personally think it's a bit too much for what it needs to do. Plain old boring websockets are plenty since there's no real need to support browsers that don't support websockets anymore (they've been standard for years now). I made a websocket library but you can use anything.
 
If you want to protect your server from having its direct IP exposed, you could use Cloudflare. They support websockets even on the free plan.

Should work the same way.

There is no other way to do it. Steam imposes limits on how frequently you can send inspect requests.

You can use the url module to parse the URL, then you'd want to check the domain, path, etc.

The item ID is wrong.

Make sure all your modules are up to date. Run 'npm update'.
 
And I mean to make sure your timer doesn't exceed 231.

Use the SteamID to pull their inventory from Steam to get the inspect link, then use that to get the wear.

https://github.com/DoctorMcKay/node-steamstore#redeemwalletcodewalletcode-callback

How could it get details for the item exchange if there was no item exchange?