TheMaster

i prompted cursor to find the reason can you take a look at this response and see if its useful ? Bug confirmed The issue is that steam-user does not pass the httpProxy option to LoginSession, even though steam-session supports it. The bug File: E:\Bots\node_modules\steam-user\components\03-messages.js (lines 738-750) Current code (broken):_getLoginSession() { if (!this._loginSession) { let options = { transport: new CMAuthTransport(this), machineId: this._logOnDetails?.machine_id }; let customMachineName = this._logOnDetails?.machine_name || ''; if (customMachineName.length > 0) { options.machineFriendlyName = customMachineName; } this._loginSession = new LoginSession(EAuthTokenPlatformType.SteamClient, options); // ❌ Missing: httpProxy is NOT passed! } return this._loginSession; What should happen steam-session's LoginSession accepts httpProxy in its options (see interfaces-external.ts line 46), and uses it to create a proxied HTTP client (see LoginSession.ts lines 116-117 and 122-125). The fix Pass the proxy from steam-user's options:_getLoginSession() { if (!this._loginSession) { let options = { transport: new CMAuthTransport(this), machineId: this._logOnDetails?.machine_id }; // ✅ ADD THIS: if (this.options.httpProxy) { options.httpProxy = this.options.httpProxy; } let customMachineName = this._logOnDetails?.machine_name || ''; if (customMachineName.length > 0) { options.machineFriendlyName = customMachineName; } this._loginSession = new LoginSession(EAuthTokenPlatformType.SteamClient, options); } return this._loginSession; }

I am seeing a weird pattern the logins are all in the right place but steam shows authorized devices sometimes way off target and issues the your steam account was accessed by some one else y is that hapening any clue we use trading sites also so they collect our steam token too. @Dr. McKay

yes

@Dr. McKay change the count param to 1000 please steam is responding 400 on 5000 self.httpRequest({ "uri": "https://steamcommunity.com/inventory/" + userID.getSteamID64() + "/" + appID + "/" + contextID, "headers": { "Referer": "https://steamcommunity.com/profiles/" + userID.getSteamID64() + "/inventory" }, "qs": { "l": language, // Default language "count": 1000, // Max items per 'page' "start_assetid": start }, "json": true },

id you can change and also the device name

No i havent

we dont hit that when we call the method it calls that thats where the tradeurl is stored no? async function getTradeURL() { return new Promise((resolve, reject) => { community.getTradeURL((err, url, token) => { if (err) { reject(err); } else { tradeurl = url; tradetoken = token; resolve(url); } }); }); }

the main problem is with this endpoint how can we fix this ? https://steamcommunity.com/profiles/steamid/tradeoffers/privacy @Dr. McKay

thats weird because same county dosent cause any problems how ever i recomend using a proxy for a static ip

then chk your login history and see which countires it tried to login from

you have proxy problem in your code

@Dr. McKayif the login history shows all the logins form france then how come that the auth device location is diff can u help me narrow it down a bit? Also is there a way to change the device id everytime we call log on?

thats the only steam related thing i do client form steam user and steam community and passing that client over to steam trade offer manager there cant be a mistake. i will share some results after testing something as well but u see all the logins are from the proxy location how come th auth device location is diff the issue comes down to steam user

these are the ones ├── [email protected] ├── [email protected]

i am using this config to create the objects the proxy is a must on the steam recent logins i can see that all the requests are from te proxy location but on the authorized devices the location is not correct y is that ? const steamOptions = { autoRelogin: true }; steamOptions.httpProxy = proxy; let client = new SteamUser(steamOptions); let community const communityOptions = {}; communityOptions.request = Request.defaults({ 'proxy': proxy }); community = new SteamCommunity(communityOptions);

hmm theres not much to give its just that some times the offer completes and the event does not come idk if anyone else is expereincing this atm

It seems like the sentofferchanged especially and the received offerchanged are missing some events how to fix this?

Just curious if we dont use the machineauth token or the refresh token then what device type the steam user sends to steam cuz i see mobile logins and diff type of mobile devices identified

Is there a method available to update/change the steam password?

If u are Using that many profiles on the same Ip Ofc u wil get ratelimited i suggest using proxies in the constructors of the steam user and community

i want to get the user inventories for them to display on my project for those users who dont use the steam creds to log in so i want to know what is the rate limit of the steam side for the get user inventory contents so i can get their inventory and not get rate limited on my account

@Dr. McKay

i want to validate if a user entered rhe identity secrect correctly so my plan that i implemented was that i will create a api key and handle the confrim mation to see if the api key creates but as th apikey is already created and the steam servers are constantly replying Busy Iwant to know if there is a easy way of verifying this Currrent code async function createSteamApiKey() { return new Promise((resolve, reject) => { const retryDelay = 30000; // 30 seconds const retryLimit = 1; // Retry limit let retryCount = 0; function attemptCreateKey() { if (retryCount >= retryLimit) { console.log(`Retry limit exceeded. Setting isbusy to true.`); isbusy = true; // Permanently set isbusy to true return resolve(false); // Resolve the promise to stop further execution } console.log(`Attempting to create Web API key (Attempt ${retryCount + 1})...`); const options = { domain: "localhost", identitySecret: identity }; community.createWebApiKey(options, (err, result) => { if (err) { if (err.eresult === 10) { // Busy error console.log("API busy, retrying in 30 seconds..."); retryCount++; return setTimeout(attemptCreateKey, retryDelay); } return reject(err); // Handle other errors } if (result.confirmationRequired) { console.log("Mobile confirmation is required to create the Web API key."); return resolve({ confirmationRequired: true, finalizeOptions: result.finalizeOptions }); } console.log("API key created successfully: " + result.apiKey); isbusy = false; // Reset isbusy to false if successful resolve(result.apiKey); // Resolve the promise with API key }); } attemptCreateKey(); // Start the attempt }); } Update: the steamservers only return buys if we try to create a api on top of a api the thing that was writtten in the docs has now been set to true i read the doc idk if i am blind but i didnt saw a function to delete/revoke the webapi

fixed for now i guess

read the mobile access token thingy