-
Posts
3650 -
Joined
-
Last visited
Posts posted by Dr. McKay
-
-
You're getting DuplicateRequest in the login callback?
-
Basically just do exactly what the login-with-password example shows, and once you have webCookies then you can call community.setCookies(webCookies)
-
-
Show your code please.
-
Either event should be fine to determine if using a backpack expander succeeded, although personally I'd probably use itemRemoved.
-
Not really. The best you could do is check whether either party is not tradable.
-
Trade bans can be checked with the GetPlayerBans WebAPI method.
Escrow can be checked with the GetTradeHoldDurations WebAPI method.
getUserDetails() works by loading the tradeoffer page (using the user's trade link) and scraping the results from the HTML.
-
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.
-
-
Where are you getting a 'ready' event from? No such event exists in globaloffensive. It's connectedToGC.
-
-
-
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.
-
-
-
-
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.
-
-
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.
getting error on enabling 2FA
in node-steamcommunity
Posted
I don't know why you'd get DuplicateRequest when logging in if you're doing everything correctly. Maybe the code was already used?