Dr. McKay

Show your code please.

Correct.

I don't think you can get from Steam the SteamID of the server a player is on, but if you can obtain their server's IP (which I think you can't do for CS:GO) then you can ascertain the SteamID from that.

Sure would be nice to know what error.

Well yeah, that's how you "bypass" needing to be friends with someone to invite them to your group.... you become friends with them. That's not a bypass, that's doing it how you're supposed to do it.

Sentry files do not expire. I don't know about what SteamKit calls loginKeys but it's probably named similarly. Steam calls them login_keys on the wire.

You don't.

Please read the documentation, specifically the options.

You can call getExchangeDetails at any time after the trade is accepted, even a year afterward.

It timed out while contacting Steam. That happens sometimes. Either Steam is having trouble or your network is having trouble.

No, timed polling remains enabled (unless you disable it manually). Passing a SteamUser just triggers polls more quickly after specific actions happen.

There are examples in the GitHub repo.

The amount parameter is only applicable for stackable items, like Steam gems. CS:GO keys are not stackable, so you will need to add the individual items separately.

The inventory seems to be unlimited. Asset IDs do change on trade. Your code should always assume that an asset ID can change on trade.

addMyItem takes one argument, which should be an object.

No, "sign in through Steam" doesn't provide any kind of access to the user's Steam account. All it does is give you a verified SteamID.

Yeah, that should work.

You should be able to send messages to non-friends if you're in a group chat with them, but that's about it I think.

There's no concurrency concern with sending offers, but if you send offers too frequently (or you send too many offers) then Steam will start limiting you. You're limited to 30 total active outgoing offers, and 5 active outgoing offers to the same recipient. There are also request rate-limits.

The createOffer method doesn't do anything on the network. It just creates a new object in memory, which you can add items to and set properties on. Nothing of value actually happens until you call offer.send(). So that means you can call createOffer as many times as you want. You could call it a million times in a second if you wanted and nothing would break. Of course, sending offers that frequently isn't gonna work.

Just offer.message.

That's just one of those Steam errors that happens. Slowing down may help, and it may not.

community = new SteamCommunity(); community.login({"accountName": "username", "password": "password", "twoFactorCode": "ABCDE"}, (err, sessionID, cookies, steamguard, oAuthToken) => { if (err) { throw err; } community.getUserInventoryContents("[U:1:46143802]", 730, 2, true, (err, inventory) => { if (err) { throw err; } console.log(inventory); }); });

Please read the documentation. It's fairly straightforward.