Dr. McKay
-
Posts
3658 -
Joined
-
Last visited
Everything posted by Dr. McKay
-
Question getOffer + cancel offer
Dr. McKay replied to tchosniper's topic in node-steam-tradeoffer-manager
You cannot rearrange arguments. Order of arguments matters. It's err, offer and not the other way around. -
That doesn't look like an unencrypted appticket, so I'd assume that it's an encrypted one. But it doesn't look like that either, which is curious. I think I'd need some more information to know what it is. Have you ever used NetHook? If you were interested in gifting me a copy of Battlerite, I could probably figure out what it is definitively.
-
That's not currently possible but I had worked on it previously. Do you know if this application is using an encrypted appticket, or just a regular one?
-
Question startConfirmationChecker not starting
Dr. McKay replied to sianbg's topic in node-steamcommunity
If you use acceptConfirmationForObject as you send trades, that should work just as well. Timezones shouldn't make a difference with confirmations, as long as you changed the timezone and didn't literally change the clock. -
It should definitely work without the confirmation checker running.
-
Question startConfirmationChecker not starting
Dr. McKay replied to sianbg's topic in node-steamcommunity
All I can say is to make sure that your identity_secret is right, that your local time is right, and that you're logged in. -
Question startConfirmationChecker not starting
Dr. McKay replied to sianbg's topic in node-steamcommunity
Add community.on('debug', console.log); and provide the output. -
You're logged into the Steam client, but your web session (which is separate) has expired. In this case, call webLogOn on your SteamUser.
-
It's possible.
-
Make sure you aren't trying to double-confirm things, I suppose. When accepting a confirmation fails, all Steam returns is {"success":false} which is what triggers this error. Unfortunately, there's no more detail.
-
You need to check the escrowDays property of both them and me. Read the documentation, please. I spent a lot of time on it.
-
I'm sure you can automate updates. Find some way to get the latest version of csgo_english.txt and parse it with one of the many VDF parsers. Ignore float_value in this instance. It's meaningless.
-
Yes, that's correct. You can determine when an offer changes state with the sentOfferChanged event.
-
Attribute 113's value contains the ID of the sticker, which in your case is 1063. You got that much right. The name of that sticker is given by item_name, which is a translation token. You can look that up in resource/csgo_english.txt from the game download.
-
It's possible it was only a temporary Steam issue. Has this been happening repeatedly for a long time?
-
If you're sending a trade, there's no way to check escrow status after you send it, until the user accepts it and it either goes into escrow or it doesn't. You need to use getUserDetails to know beforehand.
-
Are you sure that you aren't reusing a 2FA code? My testing reveals that you get error 8 if you try to use a 2FA code which has already been used (perhaps to login).
-
Are you definitely logged in?
-
Is your bot logged in? Also, is everything up to date?
-
getUserDetails will tell you whether or not a trade would go into escrow.
-
Question Steambot Identify items by a unique number
Dr. McKay replied to Cracker's topic in node-steam-tradeoffer-manager
The asset ID for an item is also referred to as just the item's "id". In GetPlayerItems, "id" is the same as "assetid". Asset IDs do change when traded for Valve games (and some others). You can get the new IDs from the getReceivedItems method. -
You can use this to accept all outstanding confirmations at once, but the entire request will fail if any one confirmation fails to be confirmed.
-
Yes, the assetid is the "id" property there.
-
I believe your problem is stemming from the fact that you're trying to confirm all your pending confirmations at once. A key can only be used once, so if you try to confirm multiple confirmations in the same second, you'll generate the same key so it won't work.
