Dr. McKay

Support for this new form of inspect link has been added to globaloffensive v3.3.0. While it's not actually required to connect to the GC to decode these, if you want to avoid making code changes (and support older styles of inspect links) then this will work as a drop-in upgrade.

You need to update node-steamcommunity and call acknowledgeTradeProtection() on each account.

It's available under artifacts on SteamKit's GitHub Actions (you need to login to GitHub to download): https://github.com/SteamRE/SteamKit/actions

 

It's available under artifacts on SteamKit's GitHub Actions (you need to login to GitHub to download): https://github.com/SteamRE/SteamKit/actions

 

Either event should be fine to determine if using a backpack expander succeeded, although personally I'd probably use itemRemoved.

Yeah, no reason that shouldn't work.

Hey Dr. McKay, Just wanted to say thanks a lot for your help.
Really appreciate you taking the time to look at it!

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.

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.

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.

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.

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

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.

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.

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...

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.

A trade that's reversed during Trade Protection will go to status 12 in GetTradeHistory and GetTradeStatus.

You need to update node-steamcommunity and call acknowledgeTradeProtection() on each account.

https://github.com/DoctorMcKay/node-steamcommunity/releases/tag/v3.49.0
As far as I can tell, clicking that button in the popup (which is what acknowledgeTradeProtection() does) is all that's needed, and it only needs to be done once per account. If you've already clicked the button on the account(s) you use to trade, you shouldn't need to do anything more.

This is not unexpected. It was always just happenstance that this method worked via steam-user; it uses a method not used by any official Steam app. You should use node-steamcommunity instead, which uses the official method.