Akaz

Thanks!

I'll use this Steam enpoint for now, but if there is a way to get the trade ban status through an event instead, I'll be happy to know it https://api.steampowered.com/ISteamUser/GetPlayerBans/v1/?key=XXX&steamids=76561197960435530

Hi, accountLimitations works great for community ban and it's an event, but I've not found anything great to detect a trade ban on the account. getSteamGuardDetails seems fine but it must be called manually and is not specific to trade ban but to all trading restrictions. Edit: getSteamGuardDetails canTrade is true even when trade banned. Is there anything better to call? An endpoint maybe? Thanks!

Same issue here with 2.3.0 The code provided above worked great

Despite the steamcommunity v3.48.1 fix, I'm still facing the issue. Assigning cookies generated from steamcommunity login to steamstore fails. Dependencies: "steamcommunity": "^3.48.2", "steamstore": "^2.3.0" Code: community.login(OPTIONS, (err, sessionID, cookies) => { if (err) { console.log(`Login error : ${err.message}`); } store.setCookies(cookies); }); Log: Am I doing something wrong?

Thank you for the explanation

https://github.com/DoctorMcKay/node-steamstore#addphonenumbernumber-bypassconfirmation-callback Hey, calling this function with bypassConfirmation to true still send the email confirmation with the link that must be clicked. Am I doing something wrong or did I misunderstood the parameter? Or maybe it's just broken? store.addPhoneNumber(phoneNumber, true, (err) => { if (err) { reject(new Error(`Failed to add phone number: ${err.message}`)); } else { logInfo(`Confirmation sent to phone number: ${phoneNumber}`); } }); Thanks

Hey McKay, thanks for your work fixing this project quickly. However the solution you released using https://doctormckay.github.io/steam-twofactor-server/ doesn't seem to work with multiple session, would it have an update? To make it more clean, I'm handling multiple accounts via a session manager browser extension where each tab is a dedicated session. Let's say I log my main account A normally, then open B and C from dedicated tabs with sessions. Everything works fine so far, but when the userscript redirect to https://doctormckay.github.io/steam-twofactor-server/, it always show me logged in as A, no matter if I'm confirming a trade from A, B or C. Do you have any idea on the issue and potential fix? Thanks

Bumping this, an issue has been opened on github: https://github.com/DoctorMcKay/steam-twofactor-server/issues/6 I tried to fix it myself but couldn't find a way to submit the 2FA code after filling the field. It looks like they removed most of the javascript functions which make it more difficult.

Hey, is there a way to activate a viewer pass for the majors using one of your package? I had hope with node-globaloffensive but it doesn't seem possible Thanks

I'm using cancelTime property directly on the offer and not as a property of the trade manager, I guess in that case it is instance-linked. offer.data('cancelTime', DELAY);

Hey, A simple question, is the cancelTime mechanism linked to an instance? To be more clear, does it work as a timeout waiting for X ms before canceling the trade, in that case, only the instance that created the offer will cancel item, or would it cancel any outgoing offer that reach a certain age. Or with an example: My bot create and send an offer, cancelTime is set to 10 minutes. After 5 minute I restart the bot. Will it cancel the offer previously sent? As I'm typing I'm realizing that the answer seems pretty obvious but I'm still opening the question, a simple "It's linked to the instance that sent the trade" as answer would be enough 😄

Bump, it broke again since the rework of the login page by Steam, it doesn't automatically request for 2FA code anymore

Hey, I'm aware that I can do something like that const requestProxy = request.defaults({'proxy':userProxy}); let community = new SteamCommunity({'request': requestProxy}); But this set up a single proxy for the whole instance, while I would like to use a different proxy on different request I do with community I know I could do that by doing my own request with something like this const options = {url: URL, proxy: getRandomProxy()}; request(options, function (err, resp, body) { // Here I have a different proxy everytime }); But is there a way to have something similar while using the functions from this package? Thank you! Edit : Unless it's useless and the rate limite is based on the Steam account rather than the IP used Edit2 : After some testing, rate limite seems to be based on account requests rather than IP, making the proxy switch useless. I'll investigate a bit more but probably won't change the result.

It did the job, thanks a lot