-
Posts
3545 -
Joined
-
Last visited
Everything posted by Dr. McKay
-
I'm sure there is.
-
Question Why is apps returning null in getProductInfo?
Dr. McKay replied to ThePlata's topic in node-steam-user
Okay, so there's your problem. As of v4, the first argument in all callbacks is err. Check out the full release notes for all the breaking changes. -
timecreated is Unix time, which is the number of seconds that have elapsed since January 1, 1970 00:00:00 (UTC). In JavaScript, Date.now() gives you the current Unix time in milliseconds, so to get the current Unix time in seconds, you'll do Math.floor(Date.now() / 1000). So to get the seconds since the account was created, you'd do Math.floor(Date.now() / 1000) - player.timecreated.
-
=1, not =true.
-
SnaBe is right, you'll want to use the WebAPI. There's no way to get a player's game time from a CM (via node-steam-user), and scraping the web is futile if there's just an API for it.
-
Question Why is apps returning null in getProductInfo?
Dr. McKay replied to ThePlata's topic in node-steam-user
Are you on v3 or v4? -
BREAKING CHANGES: steam-user v4 now available on npm
Dr. McKay replied to Dr. McKay's topic in node-steam-user
Chat code will never be ported to node-steamcommunity. The new webchat is just a CM WebSocket connection established using a nonce retrieved from a web API. The same CM WebSocket connection is used by steam-user, so porting it to node-steamcommunity would basically just be copying and pasting all of node-steam-user. I may, in the future, add a way to get the nonce from node-steamcommunity in order to login to node-steam-user, but that's about all that would make sense to be done. -
Question Why is apps returning null in getProductInfo?
Dr. McKay replied to ThePlata's topic in node-steam-user
Works fine for me. -
Need some help about checking Steam level
Dr. McKay replied to TextDynasty's topic in node-steam-user
You seem to not have an understanding of how async JavaScript code works. Just because logOn was called doesn't mean you're actually logged on. You need to wait for the loggedOn event. -
Tradeoffer manager not working for me.
Dr. McKay replied to KubekSzklany's topic in node-steam-tradeoffer-manager
Check the setCookies callback for errors. -
Need some help about checking Steam level
Dr. McKay replied to TextDynasty's topic in node-steam-user
It doesn't look like you ever logged on. -
Tradeoffer manager not working for me.
Dr. McKay replied to KubekSzklany's topic in node-steam-tradeoffer-manager
You never called TradesManager.setCookies -
Question How to add only 1 item type to offer
Dr. McKay replied to roughnecks's topic in node-steam-tradeoffer-manager
You are still getting an array. tags: [ [Object], [Object], [Object], [Object] ] is just how console.log represents an array containing 4 objects. -
Question How to add only 1 item type to offer
Dr. McKay replied to roughnecks's topic in node-steam-tradeoffer-manager
let tag; if ((tag = item.getTag('item_class')) && tag.internal_name == 'item_class_2') { ... } -
BREAKING CHANGES: steam-user v4 now available on npm
Dr. McKay replied to Dr. McKay's topic in node-steam-user
Yes, that's normal. Originally v4 was going to fill in all values not sent by Steam with their defaults (e.g. 0 or empty string) but I decided against that and switched those values back to null (which is how it works in v3). Null means that those values were not sent to us by Steam at all, which is more correct than "assuming" 0 or empty string. -
BREAKING CHANGES: steam-user v4 now available on npm
Dr. McKay replied to Dr. McKay's topic in node-steam-user
What is the bug? -
Question How to add only 1 item type to offer
Dr. McKay replied to roughnecks's topic in node-steam-tradeoffer-manager
item_class -
BREAKING CHANGES: steam-user v4 now available on npm
Dr. McKay replied to Dr. McKay's topic in node-steam-user
Thanks for the info, that's fixed in beta 5. With beta 5, steam-user v4 is now feature-complete (unless there's something major I missed). Now just waiting on some more thorough testing (please post your bugs!) and for me to finish the new chat docs. -
I was unable to reproduce this on the v3 branch, but there is indeed a bug in v4 that prevents sentry files from being appropriately confirmed with Steam. It will be fixed in beta 5 to be published later today, but for the time being if you delete your sentry file and login with v3 and provide an email code, v4 should then work.
-
Question How to add only 1 item type to offer
Dr. McKay replied to roughnecks's topic in node-steam-tradeoffer-manager
CEconItem has a getTag method. Filter your inventory to only items with the tag you're looking for. -
BREAKING CHANGES: steam-user v4 now available on npm
Dr. McKay replied to Dr. McKay's topic in node-steam-user
This is fixed in beta 4. Thanks for the detailed info.