Blue

ty

some user inventories are really big, and the module would be doing lots of requests to steam, so if only a single one request fails, it would have to start all over again, to have a few extra attempts to that specific request if we receive a mailformed response or a common http error would be realy cool

// A bit of optimization; objects are hash tables so it's more efficient to look up by key than to iterate an array var quickDescriptionLookup = {}; function getDescription(descriptions, classID, instanceID) { var key = classID + '_' + (instanceID || '0'); // instanceID can be undefined, in which case it's 0. if (quickDescriptionLookup[key]) { return quickDescriptionLookup[key]; } for (var i = 0; i < descriptions.length; i++) { quickDescriptionLookup[descriptions[i].classid + '_' + (descriptions[i].instanceid || '0')] = descriptions[i]; } return quickDescriptionLookup[key]; } This part of your node-steamcommunity, i meant the "quickDescriptionLookup", if the target inventory has to many descriptions, it could overload ram right? like for instance some target inventory with 100k items or something..

ok cool, what about the steamcommunity module, this proccess is the same about the getInventoryContents? i saw that you made a temp var to load the target inventory, but if the target inventory is to big it can pretty much overload the ram as well right? would be cool to have something alike to keep control of ram usage if it doesnt exist yet, also thanks for the quick responses =D

Im using savePollData:true on the constructor, so my dataDirectory is already seted right?

so basicaly if i down a bit the asset cache values, i would use less ram, but the polling would be done slower? this doesnt sound that bad, but how badly this will impact the performace?

I was doing some tests in one of my projects that use this module, and i noticed that de polling sometimes requests to much ram, after get further the module in github, the "problem", seems to be that to much information is cached in the LeastUsedCache(), this happens only when there is a that bot account has to many items i suppose.. so having that in mind, i have a question that can possibly lower the ram usage, what if we use a mongoDB or something alike to store that data intead(as an option to implement of course), this would only be useful in some cases like mine, but it might improve a little the ram usage, and also would be possible to store more data for more time if needed.. i could have did it myself and test it to see if is worth it, but i'd rather see you guys thoughts first, and also the possibility of this to be implemented in the module by the @Doctor himself, if the results seems to be good

For Steam Mobile Auth: client.logOn({ "accountName": username, "password": password, "twoFactorCode": steamGuardCode //Steam Guard Code Generated by steam-totp });For Steam Guard email code: client.logOn({ "accountName": username, "password": password, "authCode": code //Get somehow the code sended to your email, and put it here });You can see more detailed information HERE

if is anyone interested in this, i have managed to make it work by setting up the Steamcommunity session cookies in a request.jar(), and changed the URI to the target account vaniyUrl.

I just noticed that a few level up bots dissapear, and a few others got banned, so, valve is banning bot accounts for random reasons now? anyone have a clue of what is going on ? any information is welcome!

community.httpRequestPost({ "uri": "https://steamcommunity.com/profiles/" + client.steamID.getSteamID64() + "/ajaxsetshowcaseconfig", "form": { "appid": 730, "item_contextid": 2, "item_assetid": 11692952310, "customization_type": 4, "slot": 0, "sessionid": sessionID }, "json": true }, (err, response, body) => { console.log("err:", err); console.log("body:", body); }, "steamcommunity"); I'm trying to play a little with the profile showcases, the idea is to make a change in the item that are showed in a desired slot, but for some reason it doesn't work, all the data passed in the POST are definetely right, you guys have an idea on how to make it work?

Sometimes when i use getUserDetails(), i receive the error: has declined your trade request. why i'm getting this error, and how may i avoid this?

may you have an idea, or a close number ?

There is any limit in getUserInventoryContents() ?, i mean, steam rate limits or anything that may freeze my bot, or may cause errors?

Yeah i know what this error is about, but my question is, will the node-steam-user try again later if bot can't login cuz have rearched the RateLimitExceeded ??

try to use checkconfirmations

yes i know what error 26 is about, you dont get my point, if the sentOfferChanged isnt fired, so the bot cant handle items to avoid errors 26. and to a bot with requests all the time, re-scan inventory just isnt a good idea.

i'm getting a lot of errors 26, and i have maked the bot to handle gived and received items, and if any error comes up, completely reload inventory, but still there are errors 26 all the time, so this event will for sure be fired ?? Constructor i'm using.↓↓ new TradeOfferManager({ "steam": client, "language": "en", "community":community, "pollInterval": "10000", "cancelTime": "7200000" });

I have already changed the promptSteamGuardCode to false, and maked a steamGuard handler this.getCode(shared, function(code) { callback({ "accountName": login, "password": pw, "twoFactorCode": code, "rememberPassword":true, "promptSteamGuardCode": false }); }); client.on('steamGuard', function(domain, callback) { helper.getCode(config.sharedse, function(code){ callback(code); }); });But sometimes i still got the Steam app code request, and i have to restart the node..

i'll receive any captcha if i use 2fa(sharedsecret)?

are you sure about that? i was thinking in something about 15~20 seconds, 10 seems to low ..

yeah i know i can do that, but i want to know how low can i put and be safe with the API

Problem Fixed! Cause: i was running ASF, and when i closed ASF all the problems got fixed, its probably cuz i cant have more than 1 WebSessions Tips: when you're running your bot make sure you dont have another WebSessions it may cause anoying bugs

its very simple, the event sentOfferChanged is instantly fired when the bot has received any item, but if wasnt, its fired only around 30 seconds later, so how can i make it faster when i wasnt received any item? if i have to wait always 30 seconds it may cause a bug in the future.. decrease the 30 seconds maybe a good idea, but may cause too many requests .. ?

sometimes i got: There was an error accepting this trade offer. Please try again later. (16) but a few seconds later, the offer is accepted, and the event receivedOfferChanged is fired in ateast 10~30 seconds how can i fix or, make the receivedOfferChanged event more quicker?