Dr. McKay
-
Posts
3666 -
Joined
-
Last visited
Everything posted by Dr. McKay
-
asset_properties support for node-steamcommunity
Dr. McKay replied to Mohit's topic in node-steamcommunity
https://github.com/DoctorMcKay/node-steamcommunity/releases/tag/v3.50.0 -
asset_properties support for node-steamcommunity
Dr. McKay replied to Mohit's topic in node-steamcommunity
I'll get to it soon, hopefully tomorrow. -
That embedded inspect link simply doesn't have a wear value in it.
-
If value_bytes is 4 bytes, it's either a 32-bit int or a float. stored_as_integer in items_game.txt will tell you whether to read it as an int or as a float. The vast majority of attributes are either ints or floats. 2013, 2014, and 2025 are all stored as floats, so you should use Buffer.readFloatLE to read them.
-
node-globaloffensive, inspectItem - Parsing masked inspect links
Dr. McKay replied to stepan__sykora's topic in General
I published globaloffensive v3.3.0 last night, which makes inspectItem() work with the new masked inspect links. -
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 have to use the game client code somehow, whether that's injection or hooking or whatever. The GC only sends the raw data (paint seed, paint index, wear, etc) but the code to turn that into a model or image is only inside the game client.
-
Cursor is wrong. Passing the httpProxy option to LoginSession is unnecessary because the CMAuthTransport handles proxying already. All login communication happens through the same proxied TCP/WS connection as all other Steam client communication.
-
It's possible that the request is no longer supported by Steam.
-
740 is not the right AppID, use 730.
-
The /inventory endpoint is newer and provides more up-to-date data. But the trade offer UI does still use this endpoint, so you should be safe to use it even if it's marked as deprecated.
-
There's no reason to think you'd be banned for using this endpoint. It's already there: TradeOffer#loadPartnerInventory
-
Not currently possible but it's on my list of things to do
-
No, you'll need to login twice.
-
Yes, use getAppBetaDecryptionKeys.
-
I don't know why you'd get DuplicateRequest when logging in if you're doing everything correctly. Maybe the code was already used?
-
You're getting DuplicateRequest in the login callback?
-
Question: Using proxies with steamcommunity (v3 and later)
Dr. McKay replied to HunterX12's topic in node-steamcommunity
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.
-
best way to check if an item is used in node-tf2
Dr. McKay replied to mjavad_mllw's topic in General
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.
-
a way to check if trade partner has prohibition
Dr. McKay replied to mjavad_mllw's topic in node-steam-tradeoffer-manager
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.
- 1 reply
-
- 1
-
