timgfx

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 process.env = {}; at the start of my code. That broke stuff

Stack Trace: TypeError: Path must be a string. Received undefined at assertPath (path.js:28:11) at Object.join (path.js:489:7) at userData (C:\Users\timol\Desktop\myFolder\node_modules\appdirectory\lib\appdirectory.js:16:25) at AppDirectory._setTemplates (C:\Users\timol\Desktop\myFolder\node_modules\appdirectory\lib\appdirectory.js:134:34) at new AppDirectory (C:\Users\timol\Desktop\myFolder\node_modules\appdirectory\lib\appdirectory.js:129:10) at new SteamUser (C:\Users\timol\Desktop\myFolder\node_modules\steam-user\index.js:104:34) at my files This is steam-user index.js:104. This was always there, so this is weird. The exact same thing happens in steam-tradeoffer-manager this.options.dataDirectory = (new AppDirectory({ "appName": "node-steamuser", "appAuthor": "doctormckay" })).userData();

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: X-Requested-With: 'com.valvesoftware.android.steam',Referer: 'https://steamcommunity.com/mobilelogin?oauth_client_id=DE45CD61&oauth_scope=read_profile%20write_profile%20read_client%20write_client',User-Agent: 'Mozilla/5.0 (Linux; U; Android 4.1.1; en-us; Google Nexus 4 - 4.1.1 - API 16 - 768x1280 Build/JRO03S) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30',Accept: 'text/javascript, text/html, application/xml, text/xml, */*' These are both taken from node-steamcommunity. What I'm doing is registering an account, and trying to activate 2fa. But I am not able to get the oauth token because I can't access /chat. I tried using the values above in all my requests and still it doesn't work. I can't find anything else I would have to add in node-steamcommunity. The only real difference is that I am registering instead of logging in, could that be the problem or am I missing something?

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:)