Dr. McKay
-
Posts
3606 -
Joined
-
Last visited
-min(1).thumb.jpeg.467791fa472581b68464b62bab782c03.jpeg)
Dr. McKay's Achievements
-
Receiving counteroffer doesn't trigger newOffer
Dr. McKay replied to JVz's topic in node-steam-tradeoffer-manager
There's no reason it wouldn't, a counter-offer is a new trade offer like any other. -
Yes, that's what I said.
-
'sentOfferChanged' Missing Rollback Event — Needs Update
Dr. McKay replied to Zreex's topic in node-steam-tradeoffer-manager
Already known, see this thread: -
As you've figured out, the actual trade offer stays in the Accepted state, but the underlying trade gets rolled back. steam-tradeoffer-manager doesn't poll GetTradeHistory at all right now, so adding support for detecting these rolled back trades would incur additional requests. I'm still working on thinking of the best way to go about this, but for now I suggest you do your own GetTradeHistory polling.
-
https://github.com/DoctorMcKay/node-steamcommunity/releases/tag/v3.49.0 As far as I can tell, clicking that button in the popup (which is what acknowledgeTradeProtection() does) is all that's needed, and it only needs to be done once per account. If you've already clicked the button on the account(s) you use to trade, you shouldn't need to do anything more.
-
DieterB reacted to a post in a topic:
Problem enabling 2FA via steam-user – result code 2
-
Probably a GC limitation. You should wait until the item modified event is emitted after adding or removing an item before moving on to the next one.
-
Problem enabling 2FA via steam-user – result code 2
Dr. McKay replied to DieterB's topic in node-steam-user
This is not unexpected. It was always just happenstance that this method worked via steam-user; it uses a method not used by any official Steam app. You should use node-steamcommunity instead, which uses the official method.- 1 reply
-
- 1
-
-
I'm traveling right now. I'll be able to push out an update in the next couple days.
-
Do you have some way to reproduce this? Checking whether steamID is set on a timer is not the proper way to reconnect. This would run you into problems if SteamUser is currently attempting to connect but isn't yet logged on. You only need to call logOn() when your bot starts up, and if the error event is emitted.
-
igor reacted to a post in a topic:
Trading and Escrow -- Mobile Trade Confirmations
-
It's the same for everyone.
-
dcv reacted to a post in a topic:
My proxy provider forbids access to https://checkout.steampowered.com/login/settoken
-
def_index tells you what an item is (which weapon, which case, etc) and paint index tells you what skin an item is. Everything you need is in items_game.txt in the game's vpk files.
-
If you aren't planning on making any requests to a domain, then you shouldn't have any issues patching the module to skip that domain's settoken call.
- 1 reply
-
- 1
-
-
I believe webTradeEligibility is basically just a cache of your trading eligibility status for display purposes on the market. Rather than run the backend checks to generate this message every time you load the page, they just run the check once and then set the cookie for display. The backend checks still get run when you attempt to actually complete a purchase or trade though; you can't bypass restrictions just by fudging the cookie.
