Dr. McKay

Before you call webLogOn, check to see if the client.steamID property is null. If it is, then you're not connected to Steam, and that's likely the reason why your web session expired.

Correct, when a new client session is established, a web session is automatically negotiated.

There is no timeout for connection attempts because when Steam goes down, it can stay down for a while and we want to be able to reconnect automatically.
Add this and you can get some more descriptive output:
client.on('debug', (msg) => console.log(msg));  

Thank you very much for the support and help.
This is when you see that I am new hehe

Swap the order of err and personas.

Yes, that's what the setCookies method is for.

Yes, you'd need to request both inventories separately.

Your Steam Community inventory is AppID 753, ContextID 6. So replace 730 with 753 and 2 with 6.

Check the users property to see if you already have their info cached, and if you don't, use getPersonas. The URL to the image is available in the resulting object as avatar_url_icon, avatar_url_medium, and avatar_url_full.

Yeah, if it has to store all that item data in RAM, naturally it's going to consume RAM.

I don't think a block is detectable, no.

Yes.

Update: it's been 9 months since my last post (11 months total), and it has happened a third time.
 
I can confirm that restarting my own steam client does fix it. So, it seems like restarting the bot just pushes a refresh, and really only Valve can fix this.
 
However, it might be something in the bot that is triggering it initially

That code retrieves a list of CS:GO servers and sets itself to in-game, but it doesn't join a server which is why you wouldn't see the bot in the server. It is not possible to actually join a CS:GO server from a bot, as you would have to implement VAC and nobody's been insane enough to try that.

There are a bunch of options. You could use readline to read input commands from the terminal and take actions based on those, you could start up an http server and respond to requests, there are a bunch of other things you could do too.

Sometimes it can be a little confusing to identify a specific item in the Steam economy. There are several different types of IDs present in one particular item, and a lot of vague terminology. This guide aims to clear all that up for you.

For starters, the "official" term for a Steam item is an asset. When I say a "Steam item", I mean a particular copy of an item. I'm not referring to the item's definition, name, image, or anything. I'm referring to a specific, unique copy of the item.

In a general sense, every item on Steam must be owned by an app. An "app" is a game, software, or whatever on Steam. Every app has its own unique AppID. You can find a particular game's AppID by going to its store page or community hub and looking at the URL. For example, TF2's AppID is 440 so TF2's store page can be found at http://store.steampowered.com/app/440. CS:GO's is 730, Dota 2's is 570, and so on. Note that Steam Community items, Steam gifts, and other "Steam" items are owned by the "Steam" app, which has AppID 753. To identify an item, you'll need the AppID of the game which owns it.

Of course, the AppID alone isn't enough. You also need two other IDs. Have you ever noticed how some games have multiple inventories, which appear in a drop-down list? An example is the Steam inventory, which has sub-inventories for "Community", "Gifts", "Coupons", etc. These "sub-inventories" are called contexts, and each context has its own context ID. If a game doesn't have a drop-down menu to select a context, that doesn't mean that it's without contexts. That only means that it has one single visible context. That single context still has an ID. For all current Valve games, the context ID for the publicly-visible context is 2.

Context IDs can be a bit tricky. It's entirely up to the game's developer to determine how they work. For example, Valve games take the "single shared inventory" model in which there's one context ID which is shared by everyone. Under this model, an item belongs to one particular context and never leaves that context. Consequently, the item's context ID never changes. It is, however, possible for game developers to create contexts in any way they choose. For example, Spiral Knights uses the "per-character inventory" model in which everyone who plays the game has their own context IDs for their characters. Creating a new character creates a new context ID. This means that when an item is traded between users, its context ID will change as it moved out of a particular character's inventory.

Those are the two different types of "containers" in the Steam economy. Apps own contexts, and contexts own assets. Every asset on Steam has, in addition to its AppID and context ID, an asset ID which is guaranteed to be unique inside of a given AppID+ContextID combination. Notice that this means that asset IDs are not unique across all of Steam. They aren't even unique across a particular app. They are only unique inside of a given context. For example, there could be two items with asset ID 1 in the same game, as long as they have different context IDs. An item's asset ID may be referred to as "assetid" or just plain "id".

Context IDs and asset IDs are assigned by the game developer and can follow any pattern. They can change when traded or not. They may both be up to 64 bits in size. Consequently, Steam returns them (like all other 64-bit values) in JSON as strings.

Still following? All of what we've learned so far leads us to this conclusion: in order to uniquely identify an item, you need its AppID, its context ID, and its asset ID. Once you have these three things, only then can you uniquely identify it. In fact, this is how you link to a particular item in a user's inventory: steamcommunity.com/profiles/steamid/inventory#appid_contextid_assetid. Here's an example: https://steamcommunity.com/id/DoctorMcKay/inventory#440_2_134161610

What are these "classid" and "instanceid" values though?
The observant reader may have noticed that there are two more IDs attached to a particular item which I haven't mentioned. These are the "classid" and "instanceid". These IDs are used to map an asset to its description.

What's a description? A description is what you need in order to actually display an item. An item's description contains its name, image, color, market_name, whether it's tradable or not, whether it's marketable or not, and more. There are many endpoints on Steam which return JSON objects representing assets that only contain the asset's AppID, context ID, asset ID, classid, instanceid, and amount. An item's amount is how big of a stack it is. Unstackable items always have an amount of 1. Stackable items (such as Steam gems) may have a larger amount. Stacked items always have the same asset ID.

What's the difference between a classid and an instanceid? In a nutshell, a classid "owns" an instanceid. The classid is all you need to get a general overview of an item. For example, items with the same classid will pretty much always have the same name and image. The instanceid allows you to get finer details such as how many kills are on a strange/StatTrak weapon, or custom names/descriptions.

You can turn a classid/instanceid pair into a description using the GetAssetClassInfo WebAPI method. Notice that the instanceid is actually optional: if you only have a classid that's fine, you just won't get finer details for the item.

Name? Market Name? Market Hash Name?
Every asset on Steam has a name. Without a name, there's nothing to show in your inventory. The item's name is the name property of its description. The item's name may be localized if the game's developer has set it up to be.

Every marketable item also has a "market name". This name may be the same as—or different from—the item's regular name. The item's market name is the market_name property of its description. This is the name that's displayed in the Steam Community Market when the item is up for sale. Why the distinction? There are some items which have value-affecting data that isn't in their name; for example, CS:GO skins have 5 different tiers of "wear", which isn't in their names. The wear tier is appended to each skin's market name however, so that the different tiers of wear are separated in the market. The market name may be localized or not, and may not exist at all if the item isn't marketable. It's up to the game's developer.

Finally, every marketable item also has a "market hash name", available under the market_hash_name property. This name is supposed to be the English version of the item's market name, but in practice it may vary. For example, Steam Community items prepend the AppID of the originating app to each item's market hash name, but not to the market name. The market hash name is never localized, and may not exist if the item isn't marketable. Again, it's up to the game's developer. You can view the Community Market listings for any marketable item using this URL formula: steamcommunity.com/market/listings/appid/market_hash_name. Here's an example: https://steamcommunity.com/market/listings/440/Mann%20Co.%20Supply%20Crate%20Key

Note that the Community Market has no concept of contexts. Consequently, market [hash] names are unique for a particular "class" of items per-app (and by extension per-context). This means that for marketable items, two items with identical market hash names will be worth roughly the same (with some exceptions, like unusual TF2 items).

Questions?
Ask below. I'm happy to help!

You need to check the actual relationship. You're likely causing a loop by calling addFriend, which causes friendRelationship to get emitted with relationship == Friend, which calls addFriend, which emits friendRelationship which calls addFriend which...

Thank you very much! It's working beautifully now!

You need to set your persona state to something besides Offline in order for friends stuff to work.
client.setPersona(SteamUser.EPersonaState.Online)

No idea.

It looks like you're sending the parameters in the URL rather than in the post body as you should be.

Thanks for the reply. Yes it works now. Your comment on Ben's questions also helped. So I just had to send the values as x-www-form-urlencoded. I was stuck on this for about a month. I was looking in the wrong direction, I kept thinking there was a problem with how I was sending the cookies or I was missing some cookie, especially the webTradeEligibility cookie as when I cleared my browsers cookies I could not trade, that cookie is not even needed when we request directly, that was strange.
Thanks again. Have a wonderful day.

I checked market history (https://steamcommunity.com/market/myhistory?count=100&start=0(max 500)) and found row "rollback_new_id" he is responsible for new asset id. This way you can track all the skins on your account, but you will not be able to recognize the new asset id of the skin you bought.

You probably want to listen for the 'newOffer' event using your steam-tradeoffer-manager instance.

Unless you're doing something shady, I wouldn't expect Valve to pay any mind to you.