Dr. McKay
-
Posts
3641 -
Joined
-
Last visited
-min(1).thumb.jpeg.467791fa472581b68464b62bab782c03.jpeg)
.thumb.jpg.74112315f9c37abfc8a06c600b0641c2.jpg)
Dr. McKay's Achievements
-
Mobile Confirmation of incoming tradeoffer
Dr. McKay replied to bytes_intravenously's topic in General
You can't mobile confirm a trade offer without having your account's identity_secret, which is present in the mafile. -
Dr. McKay reacted to a post in a topic:
[node-globaloffensive] Connection to CS2 Game Coordinator times out
-
diegob reacted to a post in a topic:
[node-globaloffensive] Connection to CS2 Game Coordinator times out
-
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.
-
diegob reacted to a post in a topic:
[node-globaloffensive] Connection to CS2 Game Coordinator times out
-
Where are you getting a 'ready' event from? No such event exists in globaloffensive. It's connectedToGC.
-
diegob reacted to a post in a topic:
[node-globaloffensive] Connection to CS2 Game Coordinator times out
-
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.
-
jerrey reacted to a post in a topic:
After I successfully call the method this.client.gamesPlayed([730]), haveGCSession is false
-
diegob reacted to a post in a topic:
[node-globaloffensive] Connection to CS2 Game Coordinator times out
-
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.
-
diegob reacted to a post in a topic:
[node-globaloffensive] Connection to CS2 Game Coordinator times out
-
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]);
-
diegob reacted to a post in a topic:
[node-globaloffensive] Connection to CS2 Game Coordinator times out
-
I'm not aware of any other requirements like you describe. Are you sure that you're logging onto Steam correctly?
-
diegob reacted to a post in a topic:
[node-globaloffensive] Connection to CS2 Game Coordinator times out
-
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.
-
diegob reacted to a post in a topic:
[node-globaloffensive] Connection to CS2 Game Coordinator times out
-
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?
-
how to update access token for EAuthTokenPlatformType.SteamClient?
Dr. McKay replied to JVz's topic in node-steam-user
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. -
FloatingF reacted to a post in a topic:
Memory leak in steamUser when using enablePicsCache / picsCacheAll
-
Memory leak in steamUser when using enablePicsCache / picsCacheAll
Dr. McKay replied to FloatingF's topic in node-steam-user
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?