https://dev.doctormckay.com/discover/McKay Development - All Activityenhi, did u update SteamCommunity on a new version?Wed, 15 Jul 2026 08:32:34 +0000This fix has been working for 40 hours, there have been no problems with anything. Share who has what resultsWed, 15 Jul 2026 03:39:25 +0000check out this thread: https://dev.doctormckay.com/topic/5946-new-request-limits-429-error/Tue, 14 Jul 2026 23:15:52 +0000it just brute forced it. I just used "/Goal" mode in codex. it changed a bit, sent a new request, changed a bit, sent a new request, on and on an on, in a loop. for like 30 minutes.Tue, 14 Jul 2026 19:21:38 +0000😵‍💫 I was panicking 😅 but thanks for the clarification. This cookie new for me. I've never seen it in cookies since yesterday.Tue, 14 Jul 2026 18:09:49 +0000steam using this cookies few years) dont panicTue, 14 Jul 2026 09:06:52 +0000Something big comming 🤫 - steam has new cookies bm_sv and ak_bmscMon, 13 Jul 2026 23:14:43 +0000This still seems to work fine for me atm. But Steam seems to go through a bit of turbulence right now, so I catch stray 500's and 400's I'm afraid it's specific Steam-related problem from recent site changes and GPT won't have that in it's training data. Did it give any guesses on why this might work? Many years of being afraid for my normal trading accounts T ^ TMon, 13 Jul 2026 18:25:32 +0000Send correct user-agent for mobileconf requests, to avoid 429 errors (#371) Full Changelog: v3.50.2...v3.50.3 View on GitHubMon, 13 Jul 2026 16:52:05 +0000there is always risk of getting banned with steamMon, 13 Jul 2026 15:59:09 +0000Hey guys. I have asked gpt5.5 to fix it. (With the samples from this thread) And telling it that it needs to change the headers to prevent akamai WAF. This was the set of headers that works for 95 percent of times: const headers = { 'Sec-Fetch-Dest': 'empty', 'Sec-Fetch-Mode': 'cors', 'Sec-Fetch-Site': 'same-origin', }; Although, some endpoints needed some more tuning. (E.g. getting partner details after creating an offer) So right now, i use this to change header dynamically: I have been using this for the past 36 hours and it is working fine. Is there anything suspicious about this? Is there a ban risk? (I don't think so myself, but wanted to share it)Mon, 13 Jul 2026 15:15:38 +0000This option also turned out to be quite working, for me it does not even require changing the Accept-Encoding, the key is to transfer Accept and sec-fetch-user. headers: { //"User-Agent": "Mozilla/5.0 (Linux; Android 14; Pixel 8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Mobile Safari/537.36", "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8", //"Accept-Encoding": "gzip, deflate, br, zstd", "Accept-Language": "en-US,en;q=0.9", "sec-ch-ua": "\"Chromium\";v=\"140\", \"Not=A?Brand\";v=\"24\", \"Google Chrome\";v=\"140\"", "sec-ch-ua-mobile": "?1", "sec-ch-ua-platform": "\"Android\"", "sec-fetch-dest": "document", "sec-fetch-mode": "navigate", "sec-fetch-site": "same-origin", "sec-fetch-user": "?1", "upgrade-insecure-requests": "1" }Mon, 13 Jul 2026 10:14:44 +0000It's absolutely crazy, every time i delete one parameter, everything starts to work. What is the logic behind this? headers: { 'Accept-Encoding': 'zstd', // 🤪 },Mon, 13 Jul 2026 09:19:38 +0000thanks so muchMon, 13 Jul 2026 03:09:51 +0000Fix CEconItem crash when "Tradable/Marketable After" date isn't day-first by @GVRLNKMK in #370 Fix login hanging indefinitely on steam-session timeout by @lrftw in #369 Full Changelog: v3.50.1...v3.50.2 View on GitHubSun, 12 Jul 2026 21:20:03 +0000This helped me with inventory requests, thanksSun, 12 Jul 2026 18:09:12 +0000Error 429 appeared again, this entry fixed the situation, but idk for how long: 'Accept-Encoding': 'br, zstd'Sun, 12 Jul 2026 15:38:35 +0000Nope, I test requests one by one and still got a few errorsSun, 12 Jul 2026 15:33:10 +0000do you have 100% success rate? it's still gives me rate limit from time to timeSun, 12 Jul 2026 14:31:21 +0000Thanks for the feedback guys! This helped me with trade confirmations when testing, thanks! Nothing works for inventory requests yet. I'll take a closer look at real site requests later.Sun, 12 Jul 2026 14:15:16 +0000Here is a cleaner version if you encounter problems. Still not working %100, randomly works. As on some steamcommunity versions, that method would cause a crash. if (this._options.request) { return reject(new Error('SteamCommunity.login() is incompatible with node-steamcommunity v3\'s usage of \'request\'. If you need to specify a custom \'request\' instance (e.g. when using a proxy), use https://www.npmjs.com/package/steam-session directly to log onto Steam.')); } const SteamCommunity = require('steamcommunity'); const community = new SteamCommunity(); // Patch before confirmations — login doesn't use this.request community.request = community.request.defaults({ headers: { 'Accept-Encoding': 'gzip, deflate, br' } });Sat, 11 Jul 2026 15:22:07 +0000For me, this method has not changed anything at all. I consistently receive cookies from the steam-session, setCookies() in steamcommunity and tradeoffer-manager work stably, but as soon as I try to send an exchange from the bot or get a link to the exchange bot getTradeURL(), I get error 429 Works for me: request: Request.defaults({ proxy: proxy, headers: { 'Accept-Encoding': 'deflate, br, zstd' } })Sat, 11 Jul 2026 03:42:12 +0000Hello, I have been having problems loading my inventory since yesterday and I keep getting the 429 warning. I updated all the modules but my problem is still not solved and I am not able to load my inventory. How should I solve my problem? ThanksSat, 11 Jul 2026 01:39:03 +0000Hello, I have been having problems loading my inventory since yesterday and I keep getting the 429 warning. I updated all the modules but my problem is still not solved and I am not able to load my inventory. How should I solve my problem? ThanksSat, 11 Jul 2026 01:36:02 +0000receiving ofc. Trying to find the way to minimize itFri, 10 Jul 2026 17:54:46 +0000