Dr. McKay

There are only three ways that a login can fail with that reason: Time is wrong Secret is wrong Code has already been usedAs you've already eliminated the time being incorrect by getting the time offset (you need to be checking the error though), then you must be using the wrong secret, or you must be reusing the auth code.

What error is it returning?

You just need to wait to get unblocked.

You should make sure that you aren't reusing a code. If you are, then you're logging in more than twice in 30 seconds and that means that you're doing something else wrong.

I believe that he's sending an offer from a bot and not getting sentOfferChanged when the recipient tries to accept it and needs to confirm on mobile. To answer your question mouzes1: the offer's state does not change when the recipient attempts to accept it and needs mobile confirmation. You can't see on the bot's end at all if the recipient has tried to accept it and is awaiting mobile confirmation. All you'll see is when the offer goes Accepted when they confirm it.

Your IP was blocked because you made too many requests in too short a time.

You're probably trying to reuse a code. They're only good once.

This module absolutely won't work with a limited account. You can trade from the website using a limited account, but trying to automate that would be like trying to stab your eye out with a fork. You just don't want to do it. Just pay the $5.

There is no webLogOn method in node-steamcommunity. That's part of node-steam-user.

steam-tradeoffer-manager has a built-in option to automatically cancel offers if they remain active for too long. Look at the cancelTime option. There's no direct resend method, but you can call offer.duplicate() to get a copy of the offer, which you can then send (provided the items still exist).

There's no way to directly get a list of all marketable items, but you can get the list of apps in the store using GetAppList.

Update to 2.1.0 and provide your PIN to setCookies and it should work for you.

I really have no idea, sorry.

What kind of chat are you inviting the bot to join?

I can't reproduce this with group chats or multi-user chats. Make sure all your modules are up to date.

The "partnerid" is just the accountid part of your SteamID: var partnerid = community.steamID.accountid; You can use steam-tradeoffer-manager to get the token.

I posted some ways you can work around this here: https://dev.doctormckay.com/topic/395-how-do-you-deal-with-timeout-err-16-on-tradeoffer-send/

https://dev.doctormckay.com/topic/409-very-important-error/ No need for multiple threads about the same thing.

Just my own experience. I've updated the readme to reflect this fact.

Are you going online on chat properly with client.setPersona?

It performs the same validation that getEscrowDuration did. That is, you'll get an Error with the same message as before if the token is invalid.

You should be using getUserDetails now, which does that and more.

If you're currently being 429'd, you need to wait at least a couple minutes. And you need to slow down to avoid it in the future.

It will absolutely definitely not work.

10 seconds is not long enough.