Avoid Error 429 Too Many Requests when loading large inventory

[Mr-VIT]

SteamCommunity.prototype.getUserInventory:

node-steamcommunity/components/users.js

Line 384 in 2bbdbf3

get(inventory, currency, body.more_start);

maybe it is worth adding a delay? I don't know the exact rate limit to avoid 429

setTimeout(get, DELAY, inventory, currency, body.more_start);

[DoctorMcKay]

If you're getting rate-limited, it's because you're requesting too many inventories from the same IP. Requesting multiple pages of the same inventory would not cause a rate-limit (except perhaps hugely massive inventories), since obviously nobody would be able to load the inventory from their browser.

[Mr-VIT]

I load only 1 inventory and on ~15 page hit 429 error

[DoctorMcKay]

Please try getUserInventoryContents instead.

[Mr-VIT]

few days ago getUserInventoryContents endpoint was broken (may be still broken for some) for many invenories with error EYldRefreshAppIfNecessary failed with EResult 55/20, but old endpoint works.

Steam still uses /json/ endpoint for trade offer making window

[DoctorMcKay]

Parts of Steam break all the time. getUserInventoryContents is more stable than getUserInventory since it's not rate-limiting you when you try to load a large inventory. If the GC goes down, then naturally getUserInventoryContents isn't going to work when it tries to contact that GC. The old endpoint is likely just serving up its stale cache when it can't contact the GC, which means it's giving you outdated information without any indication that it's outdated.

If you can tell me exactly what delay prevents you from getting rate-limited, and if it's a reasonable length of time, then I'll consider adding it. I'm not going to spend any of my personal time updating a deprecated, unstable endpoint though.

[nolddor]

Steam changed once again rate-limits, see existing PR on node-steam-tradeoffer-manager

DoctorMcKay/node-steam-tradeoffer-manager#330