Dr. McKay

npm update

https://github.com/DoctorMcKay/node-steamcommunity/releases/tag/v3.45.1

From time to time yes, Steam will disconnect you. When the disconnected event is emitted, SteamUser will automatically reconnect and loggedOn will fire again.

Not possible. API keys cannot create, send, accept, or cancel trade offers.

I don't know what to tell you. Maybe you weren't pasting your password correctly. It works fine for me as-is.

Passing a steamGuardCode to startWithCredentials wouldn't change anything with respect to that InvalidParam error. It's raised before the code is sent to Steam.

Looking back at your post, in the second code block you're passing accountName: username, which would be correct if your account name is stored in a "username" variable. In the first block, copied from the example script, you're passing it as accountName. If that variable was empty, that would explain your InvalidParam issue.

You removed the await keyword, so you aren't waiting for the promise to resolve or reject, so there's no opportunity for an error to be raised at all.

There isn't, unfortunately. Steam changed the way things work, and the only way to get an access token that can be used for enabling 2FA is by logging in with steam-session using EAuthTokenPlatformType.MobileApp. steam-user uses EAuthTokenPlatformType.SteamClient.

It's worth mentioning that steam-user does have the ability to enable 2FA on its own, although I haven't tested this in a long while and there's a chance it doesn't work anymore.

Yes, it works fine for me.

steam-user is using steam-session via CommonJS.

You have to use steam-session, at least for now.

https://github.com/DoctorMcKay/node-steamcommunity/blob/master/examples/enable_twofactor.js

No.

npm update

Dunno, sounds like your request params aren't valid.

Sounds like Steam isn't replying to the getPersonas call. You might possibly need to add a short delay to give Steam time to realize that you share a chat room with the user you're requesting data for.

That all looks correct. Is your user appearing as in-game on its Steam profile?

Have you launched CSGO? Does your account have a license for it? Are those inspect parameters valid?

I just threw this together: https://github.com/DoctorMcKay/node-steamcommunity/blob/master/examples/accept_all_confirmations.js

Check the readme for how to use it.

Your proxy is resetting the connection.

At some point.

IDEs have trouble figuring out the project structure sometimes. Just use the method, it'll work (assuming that you meant 3.45.2 and not 3.5.2, which came out in 2015).

Eventually I'll port this to typescript and the problem will be solved.

https://github.com/DoctorMcKay/node-steam-session#steamguardmachinetoken-1

9 hours ago, hkp said:

I have an issue with trades being sent but not confirming.

I'm currently running the latest steamcommunity (3.45.3) and still my trades are not confirming.

Exactly what is happening?

9 hours ago, hkp said:

I've tried using the acceptConfirmationForObject method too but with no results too. The community object on the tradeoffermanager instance is undefined.

tradeBot.manager.community.acceptConfirmationForObject(identitySecret, offerId)

 

This is expected behavior. You aren't intended to access the internal steamcommunity instance. If you need one, create one yourself.

9 hours ago, hkp said:

I've also tried logging in with a new community instance separate from the one that should be autogenerated by the trade offer manager which works fine but I'd rather have the original method of autoconfirmations when using the send method in steam-tradeoffer-manager

Auto confirmations has never been a feature, unless you're talking about the automatic confirmation checker, which has been deprecated and unsupported for something like 5 years.

It's possible that Steam isn't issuing sentry files anymore since they aren't really needed anymore. I'd have to confirm.

I assume you're talking about Firefox's container tabs or some such feature in another browser. I'm not aware of any way to work nicely with that; cross-origin userscript requests originate from the userscript manager's background page, which doesn't run in any tab context.

Sorry.

var TradeOfferManager = require('../lib/index.js'); // use require('steam-tradeoffer-manager') in production

Do what the comment tells you. This line should be:

var TradeOfferManager = require('steam-tradeoffer-manager');

Show your code and stack trace.