i guess the command like this:

and the protocol like this:

but i don't know what's the param's value

i can parse redeem_balance from hello，the type id is 6 and the protocol like this:

I am successfully creating valid auth session tickets using the createAuthSessionTicket api, but after a few minutes they get cancelled.

Do I need to keep a client alive somehow for them to stay valid?

Please forgive my ignorance.

Best,

James

Here is the snippet that should do this:

    client.once("appOwnershipCached", function() {
        console.log("appOwnershipCached");
        client.getProductInfo(client.getOwnedApps(), [], function(apps) {
            console.log("gotProductInfo");
            apploop:
            for (appid in apps) {
                depotloop:
                for (depotid in apps[appid].appinfo.depots) {
                    if (!isNaN(parseInt(depotid))) { //is key the depot id?
                        manifestloop:
                        for (type in apps[appid].appinfo.depots[depotid].manifests) {
                            var manifestid = apps[appid].appinfo.depots[depotid].manifests[type];
                            client.getRawManifest(parseInt(appid), parseInt(depotid), manifestid, function(error, manifest) {
                                if (!error) {
                                    //console.log(manifest);
                                    fs.writeFile(path.join(__dirname + "/" + depotid + "_" + manifestid + ".manifest"), manifest, "utf8", function(error) {
                                        console.log(error);
                                    });
                                }
                            });
                            break apploop; //limit to 1 manifest for now
                        }
                    }
                }
            }
        });
    });

Is this the problem? Or is it something else? Should I do something differently?

Thanks

11_3149618157612033597.manifest.zip

Ideally, the full pipeline would cover everything from an action/inspect link (e.g., steam://rungame/... +csgo_econ_action_preview ...) to generating clean, high-quality, UI-free weapon screenshots.

However, I found a YouTube video showing a Python-based method to capture images:
https://www.youtube.com/watch?v=HUIERG6r-t0
This looks more like a manual/automation screenshot workflow inside the game, and it may not match what I want in terms of scalability.

I also noticed this site:
https://cs2inspects.com/zh-CN/screenshots
It seems able to generate screenshots using only paint seed, paint index, and float (wear), without requiring an inspect link.

Or does achieving this level of control usually rely on in-game injection or memory hooking?

https://github.com/DoctorMcKay/node-steam-user#getserverlistfilter-limit-callback

Someone can help me, with a exemples?

Thanks?

Is there a way to obtain both sessions with one login process (one username/password + one mobile authenticator confirmation)?
Or is it possible to convert between these two types of sessions?

Expected result (before today):

{
    "users": {
        "76561198006409530": {
            "richPresence": {
                "status": "Playing CS:GO",
                "version": "13765",
                "time": "15.851017",
                "game:state": "lobby",
                "steam_display": "#display_Menu",
                "connect": "+gcconnectG02C0193A"
            },
            "localizedString": "Playing CS:GO"
        }
    }
}

Result after maintenance:

{
  "users": {

  }
}

node-steam-user version: 5.2.3
Node.js version: 22.11.0

I'm running into a weird issue with the GC session in CS:GO. As you can see in the screenshot, I'm logged in, but haveGCSession is showing as false. The strange part is that it doesn't happen every time—sometimes it's true. Any idea what's going on?

async loginGame(appId = 730){
    logger.info('loginGC', this.config.steamId, ';', this.getClientGC().haveGCSession);
    if(!this.getClientGC().haveGCSession){
      this.client.gamesPlayed([appId]);
      await sleep(1000)
    }
    return {
      code:200,
      success: true,
      data: null
    }
  }

  checkStatus(){
    return {
      code:200,
      success: true,
      data: {
        isSteamConnected: !!this.client.steamID?.toString(),
        isGCClientConnected: this.getClientGC().haveGCSession
      }
    }
  }

Quote

steam-user: 5.2.3
globaloffensive: 3.2.0

The `picsCache` keeps growing over time (this becomes especially noticeable when running 5 or more bots simultaneously), until after a few days the JavaScript Heap runs out of memory and crashes, since the Cache cannot be garbage collected. 
When these functions are not enabled, this memory leak does not occur. In Chrome DevTools, most of the consumed memory can also be traced back to `picsCache`.  

Is there a way to store this `picsCache` on disk (or in some other form of persistent storage) instead of keeping it in memory, in order to prevent the memory leak?
 

Then I login again on Compute B.Maybe It will tell me error of LoggedInElsewhere.

Can I kick off Compute A login session?

const SteamUser = require("steam-user");
const client = new SteamUser();

client.logOn({ refreshToken: "YOUR_REFRESH_TOKEN" });

client.on("loggedOn", () => {
    console.log("Logged in");
});

client.on("webSession", (sessionID, cookies) => {
    console.log("Web session fired!", sessionID, cookies);
});

client.on("error", (err) => console.error(err));

RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds
    at new NodeError (node:internal/errors:399:5)
    at boundsError (node:internal/buffer:86:11)
    at Buffer.readUInt32LE (node:internal/buffer:222:5)
    at TCPConnection._readMessage (/usr/src/csgofloat/node_modules/steam-user/components/connection_protocols/tcp.js:182:33)
    at Socket.emit (node:events:513:28)
    at emitReadable_ (node:internal/streams/readable:590:12)
    at onEofChunk (node:internal/streams/readable:568:5)
    at readableAddChunk (node:internal/streams/readable:275:5)
    at Readable.push (node:internal/streams/readable:234:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:232:12) {
  code: 'ERR_BUFFER_OUT_OF_BOUNDS'

I'm logging in with a username and password using steam-user, and once the webSession event is emitted, I start the two-factor setup process. There is currently no Steam Guard enabled on the account, and Steam Mail Guard is also disabled.

I assume that if Steam Mail Guard were enabled, it would make sense that the process doesn't work—since Mail Guard is a form of Steam Guard. Is that correct?

Interestingly, when I follow the same steps using Steam Desktop Authenticator, everything works as expected.

As some other users have already pointed out, could there be an issue with the enableTwoFactor function itself?
Or is the problem possibly on my end, in my code?

Thanks!

Error: Could not act on confirmation

Is it perhaps related to this issue?

If so, can it only be fixed manually by logging into each steam account or is there a way to fix it via the module?