beepisla/fake-stattrak

Apply kills to your stattrak and strange weapons in CSGO and TF2 without doing anything

fake-stattrak's Issues

Why _steamid "90071992547409920" is Anon Gameserver?

I'm interested, why _steamid "90071992547409920" is Anon Gameserver here? Isn't "90071992547409920" is steamid of some guy? lol

In case of GSLT tokens, what _steamid it'll be?

fake-stattrak/components/Server_Shared.js

Line 105 in e954c99

_steamid: "90071992547409920", // Anon gameserver

Program is running fine but no kills are applied.

Hey,

I have installed all the dependencies that are listed on README, I write the config json and then with both accounts logged out, I run the script and everything seems to be working fine, and it reaches that part that it will disconnect after 10 seconds and then sucessfully disconnects, but the kills are never applied to the strange item.

I am trying to use it for tf2 and I am running win10.

This is the bottom part of the properties file :

	"itemID": "10148665608",
	"appID": 440,
	"eventType": 0,
	"incrementValue": 100000,
	"repeat": 1

This is the powershell output :

PS C:\Users\pc\Desktop\fake-stattrak-master> node .\index.js
Validating protobufs...
Found protobufs!
Requiring files for appID 440
Creating constructors...
Logging into Steam as client and server...
Successfully logged into Steam and signed up as bot account as 76561198450758517
Successfully logged into Steam and signed up as main account as 76561198436221822
Successfully logged into Steam and signed up as server as 90146753008516096
Fake joining server with bot account 76561198450758517...
Successfully added player to server, verifying on client...
Successfully connected client and server!
Fake joining server with bot account 76561198436221822...
Successfully added player to server, verifying on client...
Successfully connected client and server!
Item increments are now being processed by Valve, this may take a little bit or until log-off.
Logging off in 10 seconds...
Successfully logged off

Server player connetct-disconnect log and player list

Hello, I'm trying to fake stattrak on multiple accounts. I'm spreading this over a long process so that I don't get stuck on the limit. The player on the server sometimes gets disconnected. So is it possible to log these disconnections and connections? Also, is it possible to get the instant list of players on the server?

Insanely slow now

Hey, I was wondering why the repeat feature was removed, as it now takes ages to increment

can't seem to log in

I have been using the version downloaded in 2022, but recently I found that some accounts cannot be logged in, so I downloaded the latest version, but I found that I still cannot log in to these accounts, can you help me check the problem

Validating protobufs...
Failed to find protobufs, downloading...
ReferenceError: fetch is not defined
at Function.downloadProtobufs (/app/test/helpers/Helper.js:39:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async /app/test/index.js:37:3
Failed to download protobufs.

When I manually downloaded protobufs from GitHub and put them in, another problem occurred

**Validating protobufs...
Found protobufs!
Requiring files for appID 730
Creating constructors...
Logging into main account...
Steam Guard App Code: ****
/app/test/components/Client_Shared.js:116
reject(new Error("Failed to connect to Steam"));
^

Error: Failed to connect to Steam
at /app/test/components/Client_Shared.js:116:14**

and sometimes is

**Validating protobufs...
Found protobufs!
Requiring files for appID 730
Creating constructors...
Logging into main account...
/app/test/helpers/Helper.js:19
let res = await fetch(uri.href);
^

ReferenceError: fetch is not defined
at Function.getJSON (/app/test/helpers/Helper.js:19:13)
at Function.GetSteamAPI (/app/test/helpers/Helper.js:9:25)
at /app/test/components/Client_Shared.js:65:32
at new Promise ()
at CSGOClient.login (/app/test/components/Client_Shared.js:63:10)
at /app/test/components/Client_730.js:12:28
at new Promise ()
at CSGOClient.login (/app/test/components/Client_730.js:10:10)
at /app/test/index.js:61:19
at Object. (/app/test/index.js:105:3)
at Module._compile (node:internal/modules/cjs/loader:1101:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:17:47**

I have conducted some tests. The account that has not opened the steam token or has not updated the new version of steamapp can be used normally when logging in, but various errors will appear when logging in to the account that has updated the new version of steamapp.

Thanks for your reply and your precious time!

CS:GO Music kit ST doesnt works.

header /\

CSGO ST doesn't boostings

https://imgur.com/a/Wzu2d6V

I tried everything, constantly changed the repeat values , something turned out 1 time, as a result, 1 kill, and no longer works, I only achieved the XD limit
in tf2 everything works fine, I don't know why
maybe I'm doing something wrong?

ReferenceError: fetch is not defined. anyone help?

at Function.downloadProtobufs (C:\Users\q\Downloads\fake-stattrak-master\fake-stattrak-master\helpers\Helper.js:39:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async C:\Users\q\Downloads\fake-stattrak-master\fake-stattrak-master\index.js:37:3

Failed to download protobufs.

Question: IncrementValue progress kill

How can i increase kill progress more and more faster
P.S sorry my bad english

Some bug for fake stattrak.

1.Does not download automatically [https://prnt.sc/rhaitv] if you manually set it works.

CSGO Stat Track weapons not working

Tested with multiple weapons and settings.

UnhandledPromiseRejectionWarning: Error: Failed to send GC message: Timeout

    at Timeout._onTimeout (/home/koutsie/Downloads/fake-stattrak-master/helpers/Coordinator.js:92:12)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)
(node:26809) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:26809) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.```

Is this still work in tf2?

I tried this like half year ago and it was working flawessly. Now it's just doesnt. Am i doing something wrong here? Maybe bot account should be premium or something? Kills just never apply.

[Question] TF2 strange farmer.

How do I make it so that I can get more value than 300000 at a time?
If I write "repeat": at least more than 300001, it does not work, it shows that everything is successful, logged off, but nothing happens, I met one person who has 77 million on 20+ guns, and wherever there are additional counters the same number, he can't be so long all 300k times to run the script for what?
For example: https://steamcommunity.com/id/goodgalRiRi/inventory/#440 (just look , that's amazing, LOL)

Update

Will you update the script? It works very slowly

Steam authorization inside the program for SteamAPI_Init ()

Hi, my application works with SteamAPI_Init (), for successful operation you need to have an authorized (login | password) Steam client next to the program. Can you please tell me if it is possible to authorize Steam inside my application so that I do not have to keep an open Steam nearby?

Possibility with Steamworks

Was trying to rewrite this using Steamworks API, however I'm stucked at implementing
this.client.gamesPlayed({steam_id_gs: serverID, game_id: this.appID});, which seems critical for this thing to work.

Are there any clues on it, or that's impossible via Steamworks, or it's a server-side thing?

Cannot find CRC for ticket from user

hi,
i just set up the bot for CSGO and this error comes up. Is this important or should i ignore that?

Successfully added player to server, verifying on client...
Successfully connected client and server!
[T2#7] Handled message: ClientTicketAuthComplete
Cannot find CRC 1733908275 for ticket from user 76561xxxx with state 0

Logging into Steam as client and server

ss 1 https://i.upload.systems/vxUDRZqu
ss 2 https://cute-cats.online/sCxdJIPY
cfg https://cute-cats.online/iBSfUy44

Requiring files for appID 730 Creating constructors... Logging into Steam as client and server... (node:12092) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ' connectionType' of undefined at SteamUser._processMulti (C:\Users\Suspectxyz\Desktop\fake-stattrak-master \node_modules\steam-user\components\messages.js:617:21) at SteamUser._handleMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-maste r\node_modules\steam-user\components\messages.js:547:8) at SteamUser.Coordinator.steamUser._handleMessage (C:\Users\Suspectxyz\Deskt op\fake-stattrak-master\helpers\Coordinator.js:22:19) at SteamUser._handleNetMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-ma ster\node_modules\steam-user\components\messages.js:533:7) at WebSocketConnection._readMessage (C:\Users\Suspectxyz\Desktop\fake-stattr ak-master\node_modules\steam-user\components\connection_protocols\websocket.js:1 96:13) at WebSocket.emit (events.js:375:28) at C:\Users\Suspectxyz\Desktop\fake-stattrak-master\node_modules\websocket13 \lib\base.js:518:10 at pipe (C:\Users\Suspectxyz\Desktop\fake-stattrak-master\node_modules\webso cket-extensions\lib\pipeline\index.js:37:40) at Pipeline._loop (C:\Users\Suspectxyz\Desktop\fake-stattrak-master\node_mod ules\websocket-extensions\lib\pipeline\index.js:44:3) at Pipeline.processIncomingMessage (C:\Users\Suspectxyz\Desktop\fake-stattra k-master\node_modules\websocket-extensions\lib\pipeline\index.js:13:8) at Extensions.processIncomingMessage (C:\Users\Suspectxyz\Desktop\fake-statt rak-master\node_modules\websocket-extensions\lib\websocket_extensions.js:133:20) at WebSocketBase._dispatchDataFrame (C:\Users\Suspectxyz\Desktop\fake-stattr ak-master\node_modules\websocket13\lib\base.js:495:18) at WebSocketBase._handleFrame (C:\Users\Suspectxyz\Desktop\fake-stattrak-mas ter\node_modules\websocket13\lib\base.js:491:7) at WebSocketBase._handleData (C:\Users\Suspectxyz\Desktop\fake-stattrak-mast er\node_modules\websocket13\lib\base.js:304:7) at TLSSocket.<anonymous> (C:\Users\Suspectxyz\Desktop\fake-stattrak-master\n ode_modules\websocket13\lib\base.js:126:9) at TLSSocket.emit (events.js:375:28) (Use node --trace-warnings ...to show where the warning was created) (node:12092) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termin ate the node process on unhandled promise rejection, use the CLI flag--unhandl
ed-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejecti ons_mode). (rejection id: 1) (node:12092) [DEP0018] DeprecationWarning: Unhandled promise rejections are depr ecated. In the future, promise rejections that are not handled will terminate th e Node.js process with a non-zero exit code. (node:12092) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ' connectionType' of undefined at SteamUser._processMulti (C:\Users\Suspectxyz\Desktop\fake-stattrak-master \node_modules\steam-user\components\messages.js:617:21) at SteamUser._handleMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-maste r\node_modules\steam-user\components\messages.js:547:8) at SteamUser.Coordinator.steamUser._handleMessage (C:\Users\Suspectxyz\Deskt op\fake-stattrak-master\helpers\Coordinator.js:22:19) at SteamUser._handleNetMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-ma ster\node_modules\steam-user\components\messages.js:533:7) at TCPConnection._readMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-mas ter\node_modules\steam-user\components\connection_protocols\tcp.js:194:13) at Socket.emit (events.js:375:28) at emitReadable_ (internal/streams/readable.js:550:12) at processTicksAndRejections (internal/process/task_queues.js:81:21) (node:12092) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termin ate the node process on unhandled promise rejection, use the CLI flag--unhandl
ed-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejecti ons_mode). (rejection id: 2) (node:12092) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ' connectionType' of undefined at SteamUser._processMulti (C:\Users\Suspectxyz\Desktop\fake-stattrak-master \node_modules\steam-user\components\messages.js:617:21) at SteamUser._handleMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-maste r\node_modules\steam-user\components\messages.js:547:8) at SteamUser.Coordinator.steamUser._handleMessage (C:\Users\Suspectxyz\Deskt op\fake-stattrak-master\helpers\Coordinator.js:22:19) at SteamUser._handleNetMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-ma ster\node_modules\steam-user\components\messages.js:533:7) at TCPConnection._readMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-mas ter\node_modules\steam-user\components\connection_protocols\tcp.js:194:13) at Socket.emit (events.js:375:28) at emitReadable_ (internal/streams/readable.js:550:12) at processTicksAndRejections (internal/process/task_queues.js:81:21) (node:12092) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termin ate the node process on unhandled promise rejection, use the CLI flag--unhandl
ed-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejecti ons_mode). (rejection id: 3) (node:12092) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ' connectionType' of undefined at SteamUser._processMulti (C:\Users\Suspectxyz\Desktop\fake-stattrak-master \node_modules\steam-user\components\messages.js:617:21) at SteamUser._handleMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-maste r\node_modules\steam-user\components\messages.js:547:8) at SteamUser.Coordinator.steamUser._handleMessage (C:\Users\Suspectxyz\Deskt op\fake-stattrak-master\helpers\Coordinator.js:22:19) at SteamUser._handleNetMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-ma ster\node_modules\steam-user\components\messages.js:533:7) at TCPConnection._readMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-mas ter\node_modules\steam-user\components\connection_protocols\tcp.js:194:13) at Socket.emit (events.js:375:28) at emitReadable_ (internal/streams/readable.js:550:12) at processTicksAndRejections (internal/process/task_queues.js:81:21) (node:12092) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termin ate the node process on unhandled promise rejection, use the CLI flag--unhandl
ed-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejecti ons_mode). (rejection id: 4) (node:12092) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ' connectionType' of undefined at SteamUser._processMulti (C:\Users\Suspectxyz\Desktop\fake-stattrak-master \node_modules\steam-user\components\messages.js:617:21) at SteamUser._handleMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-maste r\node_modules\steam-user\components\messages.js:547:8) at SteamUser.Coordinator.steamUser._handleMessage (C:\Users\Suspectxyz\Deskt op\fake-stattrak-master\helpers\Coordinator.js:22:19) at SteamUser._handleNetMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-ma ster\node_modules\steam-user\components\messages.js:533:7) at WebSocketConnection._readMessage (C:\Users\Suspectxyz\Desktop\fake-stattr ak-master\node_modules\steam-user\components\connection_protocols\websocket.js:1 96:13) at WebSocket.emit (events.js:375:28) at C:\Users\Suspectxyz\Desktop\fake-stattrak-master\node_modules\websocket13 \lib\base.js:518:10 at pipe (C:\Users\Suspectxyz\Desktop\fake-stattrak-master\node_modules\webso cket-extensions\lib\pipeline\index.js:37:40) at Pipeline._loop (C:\Users\Suspectxyz\Desktop\fake-stattrak-master\node_mod ules\websocket-extensions\lib\pipeline\index.js:44:3) at Pipeline.processIncomingMessage (C:\Users\Suspectxyz\Desktop\fake-stattra k-master\node_modules\websocket-extensions\lib\pipeline\index.js:13:8) at Extensions.processIncomingMessage (C:\Users\Suspectxyz\Desktop\fake-statt rak-master\node_modules\websocket-extensions\lib\websocket_extensions.js:133:20) at WebSocketBase._dispatchDataFrame (C:\Users\Suspectxyz\Desktop\fake-stattr ak-master\node_modules\websocket13\lib\base.js:495:18) at WebSocketBase._handleFrame (C:\Users\Suspectxyz\Desktop\fake-stattrak-mas ter\node_modules\websocket13\lib\base.js:491:7) at WebSocketBase._handleData (C:\Users\Suspectxyz\Desktop\fake-stattrak-mast er\node_modules\websocket13\lib\base.js:304:7) at TLSSocket.<anonymous> (C:\Users\Suspectxyz\Desktop\fake-stattrak-master\n ode_modules\websocket13\lib\base.js:126:9) at TLSSocket.emit (events.js:375:28) (node:12092) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termin ate the node process on unhandled promise rejection, use the CLI flag--unhandl
ed-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejecti ons_mode). (rejection id: 5) (node:12092) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ' connectionType' of undefined at SteamUser._processMulti (C:\Users\Suspectxyz\Desktop\fake-stattrak-master \node_modules\steam-user\components\messages.js:617:21) at SteamUser._handleMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-maste r\node_modules\steam-user\components\messages.js:547:8) at SteamUser.Coordinator.steamUser._handleMessage (C:\Users\Suspectxyz\Deskt op\fake-stattrak-master\helpers\Coordinator.js:22:19) at SteamUser._handleNetMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-ma ster\node_modules\steam-user\components\messages.js:533:7) at TCPConnection._readMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-mas ter\node_modules\steam-user\components\connection_protocols\tcp.js:194:13) at Socket.emit (events.js:375:28) at emitReadable_ (internal/streams/readable.js:550:12) at processTicksAndRejections (internal/process/task_queues.js:81:21) (node:12092) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termin ate the node process on unhandled promise rejection, use the CLI flag--unhandl
ed-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejecti ons_mode). (rejection id: 6) (node:12092) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ' connectionType' of undefined at SteamUser._processMulti (C:\Users\Suspectxyz\Desktop\fake-stattrak-master \node_modules\steam-user\components\messages.js:617:21) at SteamUser._handleMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-maste r\node_modules\steam-user\components\messages.js:547:8) at SteamUser.Coordinator.steamUser._handleMessage (C:\Users\Suspectxyz\Deskt op\fake-stattrak-master\helpers\Coordinator.js:22:19) at SteamUser._handleNetMessage (C:\Users\Suspectxyz\Desktop\fake-stattrak-ma ster\node_modules\steam-user\components\messages.js:533:7) at WebSocketConnection._readMessage (C:\Users\Suspectxyz\Desktop\fake-stattr ak-master\node_modules\steam-user\components\connection_protocols\websocket.js:1 96:13) at WebSocket.emit (events.js:375:28) at C:\Users\Suspectxyz\Desktop\fake-stattrak-master\node_modules\websocket13 \lib\base.js:518:10 at pipe (C:\Users\Suspectxyz\Desktop\fake-stattrak-master\node_modules\webso cket-extensions\lib\pipeline\index.js:37:40) at Pipeline._loop (C:\Users\Suspectxyz\Desktop\fake-stattrak-master\node_mod ules\websocket-extensions\lib\pipeline\index.js:44:3) at Pipeline.processIncomingMessage (C:\Users\Suspectxyz\Desktop\fake-stattra k-master\node_modules\websocket-extensions\lib\pipeline\index.js:13:8) at Extensions.processIncomingMessage (C:\Users\Suspectxyz\Desktop\fake-statt rak-master\node_modules\websocket-extensions\lib\websocket_extensions.js:133:20) at WebSocketBase._dispatchDataFrame (C:\Users\Suspectxyz\Desktop\fake-stattr ak-master\node_modules\websocket13\lib\base.js:495:18) at WebSocketBase._handleFrame (C:\Users\Suspectxyz\Desktop\fake-stattrak-mas ter\node_modules\websocket13\lib\base.js:491:7) at WebSocketBase._handleData (C:\Users\Suspectxyz\Desktop\fake-stattrak-mast er\node_modules\websocket13\lib\base.js:304:7) at TLSSocket.<anonymous> (C:\Users\Suspectxyz\Desktop\fake-stattrak-master\n ode_modules\websocket13\lib\base.js:126:9) at TLSSocket.emit (events.js:375:28) (node:12092) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To termin ate the node process on unhandled promise rejection, use the CLI flag--unhandl
ed-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejecti ons_mode). (rejection id: 7)

I was going to post this on the csgo crasher exploit but it is read only, this exploit also works for tf2, could you port it?

I was going to post this on the csgo crasher exploit but it is read only, this exploit should also works for tf2, could you port it?

Bot open connect on server csgo

Is it possible to create a bot that knows how to connect to a real server? In order for the steam server browser (search for community servers) to see the connection to the server and report that there is 1 player on the server. It is not necessary to hold such a connection for a long time, is it just possible to do this?

some problem with CMsgClientHello ?

Client_Shared.js:116
reject(new Error("Failed to connect to Steam"));
^
Error: Failed to connect to Steam

I need some help

once I write "node index.js" in the CMD

I get this:

Validating protobufs...
Failed to find protobufs, downloading...
Failed to download protobufs.

I followed your instructions very well, I'm not sure if I did anything wrong but here's a screenshot of how it looks like

Connect on server via IP:PORT

Please tell me where to fix the code so that I can connect the bot to my real server via IP: PORT? I beg you very much.

Script doesnt add kills

seems something may have been updated in the game, have redownload and installed everything from scratch and no kills are being added to any weapon or strange cosmetic. TF2

Stats not changing (TF2)

The script itself seems to be working properly, but no stats are going through. Fixes from the closed issues don't seem to be working. I'm not sure if this just doesn't work anymore, or if I'm making a really dumb mistake
Config:

edit: it was the second

seems to cap out after a couple thousand

seems to cap out. value update their side maybe?!?

[TF2] Spirit of Giving

strange on this item does not work in tf2, eventtype: 8

Unfortunately Unusable (11/12/23)

-resolved

[TF2] Stats not changing

I just tried this and it didn't work.
I had 617 kills before and now i have the same kills (I got the succesfull message so yeha, it should have worked)

Didn't have this error before and how can i fix it?

PS C:\Users\User\Desktop\fake-stattrak-master> node index.js
Validating protobufs...
Failed to find protobufs, downloading...
(node:22024) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use node --trace-warnings ... to show where the warning was created)
ReferenceError: body is not defined
at Helper.downloadProtobufs (C:\Users\User\Desktop\fake-stattrak-master\helpers\Helper.js:42:40)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async C:\Users\User\Desktop\fake-stattrak-master\index.js:37:3
Failed to download protobufs.

Trouble Using This in November of 2023

I'm trying to use this but finding myself unable to do so, I'm getting login errors but I believe thats only because I have steam guard and I do not see a place in which to put a code for either account. Is there any chance of this working? My goal is to get to the strange limit of 2.49 billion. No worries if you dont want to come back to this problem after so long. Slight bummer but I'd understand.

Looping the script

This is really not a issue since the program is working fine but I dont know other way to ask you this.

I have no clue how to program with node or anything .js related, but i was wondering if you could tell me how could i automate the script. For example "run node Index.js" everytime the script ends its execution, from what I saw I believe its just a few lines of code but could you point me to the right direction ?

Does not work

Hey so we tested it multiple times and it does not work anymore but we dont know why. Maybe u can help

Event Listening

node-steam-user package and node-globaloffensive with the package (logOn, tradeOffers, steamGuard, connectedToGC,connectedFromGC) some events can be listened to. Is it possible to listen to some protobufs events of a server created in this project? If possible, how can I do this?