Dr. McKay

Yeah, no reason that shouldn't work.

You can't mobile confirm a trade offer without having your account's identity_secret, which is present in the mafile.

You're far more than one step away. Joining a community server is not supported and never will be, as you'd have to implement VAC which nobody has been insane enough to try.

Where are you getting a 'ready' event from? No such event exists in globaloffensive. It's connectedToGC.

It wouldn't show as in-game on the profile unless you set your persona state to Online with the setPersona() method, although that wouldn't affect connecting to the GC.

Are you still using your modifications to global offensive? Try getting rid of those, as those weren't your problem.

Set your client's persona state to Online and then check the account's Steam profile to make sure it's actually launching CS. If it doesn't appear as in-game, you're doing something else wrong.

This is normal if your steam-user client shut down without properly logging off recently. I believe what happens is the GC never receives a notification of the client disconnecting, so it keeps your session active even though you're no longer there. You can typically solve this by calling logOff() if you don't get a session in a reasonable time, then logging on again.

client.gamesPlayed = [730]; // Announce we are "playing" CS2

This is your problem. The correct usage is:

client.gamesPlayed([730]);

I'm not aware of any other requirements like you describe. Are you sure that you're logging onto Steam correctly?

No, there's no other prerequisite. Were you previously using these accounts for something like requesting item data? I've heard reports of people having their accounts "banned" from connecting to the GC after doing so.

They're likely to be protobuf objects that are defined in the CS2 protobufs. I don't have any source off-hand to map type_ids to protobuf definitions; your best bet is likely to just try parsing data using various definitions and see what looks right.

The latest version of globaloffensive is working fine for me. Do your accounts own a CS2 license?

You would be expected to see the same access token/steamLoginSecure value if you attempt to refresh within 10 minutes of your last refresh, as steam-session caches it for 10 minutes. After that, you shouldn't see the same response to webLogOn() unless Steam truly returned the same access token again for some reason.

It's not really a memory leak, it's by design. picsCacheAll is especially going to consume lots of memory since it caches all app data it ever comes across. You really shouldn't use picsCacheAll in any app that lives longer than a few hours, and you should avoid using picsCache in general unless you really need it.

For what purpose do you need the pics cache?

For your own account that you're logged into, the steam-user accountLimitations and vacBans events are your best bet. For trade bans, I believe you'd need to use the GetPlayerBans WebAPI method.

Are you trying to get this data for your own account, or for other users?

No, you'd need to use that API yourself. IEconItems_440 is a TF2-specific API and steam-tradeoffer-manager is general for all Steam assets.

Sounds like it.

Read the docs please. You should not call logOn() inside of the disconnected event as steam-user will handle reconnecting automatically. Checking the steamID property is how you can tell whether you're currently logged in or not.

I believe you wouldn't receive that message if there are no other playing sessions.

Yes, getExchangeDetails makes a Steam API call (specifically, GetTradeStatus). Generally speaking, anything that has a callback makes a network request.

No, there's no built-in mechanism for handling rate limiting. You'll need to do it yourself.

Yes, this is the only way to obtain web cookies if you have a refresh token for EAuthTokenPlatformType.SteamClient. Other platform types can get cookies via steam-session.

You can still use a proxy the same way you did before with steamcommunity, but you're correct that the login() method no longer works if you do. You need to use steam-session with your proxy and call setCookies on steamcommunity, passing your proxy to both.

407 means your proxy is rejecting your connection. You're either using the wrong credentials or you have things configured wrong.

Trades containing CS2 items are not returned by the WebAPI when using an API key. You need to use an access token instead. You can get one using steam-session, and you provide it like this:

https://api.steampowered.com/IEconService/GetTradeStatus/v1/?tradeid=123456&access_token=eyAid...