timgfx

Running into this too. Is there any difference in rate limits when logged into steam vs when not logged in?

I'm looking to cache sessions on disk. I've tried simply storing the refreshToken after logging in and then 1) setting it when initializing LoginSession, 2) calling LoginSession:refreshAccessToken(). However, this yields EResult 15 AccessDenied. I've also tried storing cookies and adding them the the session._webClient.cookieJar, but same issue.

Am I doing something wrong or is this not supported?

Edit: Seems like the refresh token should be used to get a new steamLoginSecure cookie instead of getting a new access token. So I suppose all I need to do is store the refresh token, set it on the LoginSession instance, and call getWebCookies

Looks like this process is indeed correct: https://github.com/DoctorMcKay/node-steam-session/issues/11. And refreshing access tokens is just not a thing when using WebClient

I see, I was under the assumption that I could use `time_historical_cutoff` to only get trade offers from after that timestamp, but that assumption was incorrect. Thank you!

I am attempting to fetch all active offers after some timestamp, however this does not seem to work on sent trades (I have not tested this for received trades)

Does this endpoint simply only apply the cutoff to received trades? I don't see steam-tradeoffer-manager doing any filtering so I'm confused about what to expect. 

Im correctly converting timestamps to steam unix time (seconds since epoch), and have tried using both `true/false` and `1/0` for the query parameters. Both yield the same result

I used 

You also need to submit these in your login request.

The thing is that I'm not logging in. I'm registering, then going to /edit?welcomed=1, grabbing a new sessionid there and doing some other things with the account. It works perfectly fine, I got all the cookies I need afaik so I don't really see what is different from logging in or relogging. Any ideas?

Edit: Including those when registering changed nothing.

I already found the answer; mobile headers/cookies. Now my question is whether you need anything else besides that?

What I am doing right now isn't working, it still tells me that my account is restricted etc etc.

Cookies I set for steamcommunity.com:

mobileClientVersion=0 (2.1.3)

mobileClient=android

Steam_Language

And headers:

Its only set when offers are accepted. I am stupid, my bad

getExchangeDetails wouldnt work because my trade apparently didn't have a tradeID set. I couldn't find tradeID being set anywhere in TradeOffer.js's code, and it probably isn't meant to be TradeOffer.id either because that's also being checked for. Any ideas?

Also make sure to provide your steamcommunity instance when creating a new tradeoffermanager instance, this makes tradeoffermanager use steamcommunity’s request instance which will make sessionExpired work with tradeoffermanager too

Try replicating the exact requests your browser sends when creating an account

The problem is that you’re using my shitty leaked bot :Kappa:

Remove this line:

language: “en”,

And it’ll work. That line caches descriptions which really adds up when loading many items. Node has a default memory limit of just under 2GB. This limit can be changed as shown here: https://futurestud.io/tutorials/node-js-increase-the-memory-limit-for-your-process. I would just run it without changing the allocated memory though (unless you run into more issues)

Also don’t use leaked code xd

This is against the steam tos so watch out when doing this. You should check how steam the steam site sends requests when you list an item and replicate that 

Valve changed it, it has nothing to do with steam-user. 

You can use node-steamcommunity's sessionExpired event to detect when your session expires, which is when you want to refresh/update your cookies. You can do this by calling steam-user's webLogOn method

Ahh I thought the description of the escrowDays property indicated that that value would be the highest cooldown between the user and the trade partner, thanks for you response:)

Their descriptions say that Steam uses the larger value between you and the other user - would this mean that if either the bot or the trade partner have a trade cooldown that both of the escrowDays values will be the same amount?

Answer: No, I thought vanityURL was emitted whenever it was retrieved from steam.This was not the case, it is emitted if the vanityURL changes. So it will not emit at all, it will just be set at log in (SteamUser.vanityURL)

Title

I don't, I can check later. Maybe it happens with cards with their game removed

Nope. This library simply executes web requests (or protobufs) and handles cookies etc. It could technically do it but I doubt that itll be added since it's not something steam's server does, the library would have to do a lot more too

I don't think that's implemented. You could scrape instead. I suggest using the node modules request and cheerio

I'm having some problems with this - not a big deal but I'd still like to know. Somehow some cards I am receiving in a trade don't have a market_hash_name. As far as I know all cards are marketable, so how is it possible that it doesn't have a market_hash_name? Language is set if that matters

Edit: Language is only needed for descriptions right? I'd rather not use it because of all the descriptions it'll load but am not sure if that's actually how it works

Thanks .)