-
Posts
3398 -
Joined
-
Last visited
Posts posted by Dr. McKay
-
-
Contact your proxy provider.
-
Sounds like someone with control of your network is trying to modify traffic.
-
I don't believe you can get non-game badges or your account's creation time via steam-user. You'll need to use the WebAPI.
-
2 hours ago, m.tsa said:
I apologize for my dumb question sir, but I haven't found it anywhere else.
What is the specific error that I should listen for when I need to logOn again?
ATM I'm only using community.on("sessionExpired") to call webLogon to refresh the cookies on community and trade manager, with the client.on("webSession") event btw.https://github.com/DoctorMcKay/node-steam-user?tab=readme-ov-file#error
The 'error' event.
-
-
If you're passing an instance of SteamUser in to the constructor, I recommend you don't poll more frequently than every 30 seconds (30000). And you shouldn't be running full updates more frequently than every 2 minutes (120000).
In other words, the defaults are fine.
-
You can't use OpenID with steam-user.
-
I don't believe I've ever seen this happen.
-
The inspect request is rate limited. The absolute fastest I've seen it work is once per second, and that may even be too frequent these days.
-
I suggest you ask the csfloat project, with which I have no relation.
-
There's no reason to ever call logOn in an interval. If you receive the error event, then just log on again and you'll always be connected.
-
2.11.4 should fix this for you.
-
-
15 hours ago, JAHMCR said:
I'm trying to filter "backpack.tf" listings based on an inventory items, but I'm not sure how to get a "defindex" or any other way to map the item from CEconItem.
I know the Steam WebAPI provides a "IEconItems_440" method to get the player items with relevant information like a "defindex", is there any special reason why you are not using this?
You can't really reliably do it. There are some community endpoints that include app_data on the item description, which does contain def_index, but not all have that.
steam-tradeoffer-manager isn't using IEconItems_440 because that's a TF2-specific interface and steam-tradeoffer-manager is meant to work with any Steam app.
-
2 hours ago, JAHMCR said:
Just replaced "SteamID.fromIndividualAccountID(76561198024816553)" with "76561198024816553" for testing and it worked fine, was I using "SteamID.fromIndividualAccountID()" wrong?
Yes, 76561198024816553 is a full SteamID, not an account ID. An account ID is what you see in a [U:1:46143802] ID (46143802 is the account ID).
-
If you're fetching your time offset and it's 1, then your clock is correct. If you're still being told that your authenticator is invalid, then the secret must be wrong.
-
On 4/13/2024 at 7:54 AM, Ryuu said:
Aren't you taking similar risks when logging in with steam in any website?
No. When you sign into a site using Steam OpenID, the site only gets your SteamID and nothing more. Certainly not an access token.
On 4/13/2024 at 7:54 AM, Ryuu said:They also use an app you can download and use to trade, which also gives them full control of everything including running an exe file on your pc. Many other markets such as Waxpeer also do it. I've been selling on those markets for years so it's a risk I'm willing to take
That's great. I'm still not going to help you compromise your own account.
-
You need to provide the asset owner's SteamID as well. The linked repository only indicates that S is optional because you need either S or M (M is used for market listings).
-
-
Giving an access token to a third-party site is effectively the same thing as giving them your username, password, and mobile auth code. I wouldn't recommend it.
-
What's there is what Steam reports. I can't help you if the backend is returning bad data.
-
-
No, use steam-session for that.
-
The third-party typescript definitions haven't been updated for 2.11.0. Just suppress the error.
CS sendToGC Not Getting Reply
in node-steam-user
Posted
You need to report that you're in CS2 by calling user.gamesPlayed(730), then complete the GC handshaking process before sending any other GC messages. For CS, this is sending ClientHello (4006) with the proper version number and waiting for ClientWelcome (4004) in response.
You can check node-globaloffensive for reference.