Allows you to send commends and reports for CSGO, though commend botting is the focus of it and reporting is just a little side thing.
Note: Even though I have implemented a report bot I still believe they are fixed. - Read More
Please view the Changelog for a list of changes.
Please read the README in its entirety before coming to me asking for help.
node-v12.9.1-x64.msi
npm ci
config.json.example
to config.json
and adjust it (See below)node index.js
Following the installation steps from 1
to 4
and simply override all files. NEVER DELETE YOUR accounts.sqlite
IT STORES ALL IMPORTANT INFORMATION - NOT ONLY ACCOUNT DETAILS
Some values are not always used:
COMMEND
the entire report
section is ignoredREPORT
the entire commend
section is ignoredauto
in serverID
or matchID
will require an account to be entered in the fetcher
sectionLOGIN
ignored the entire report
, fetcher
, serverID
, and matchID
section but will require you to enter an account in the account
section, other way around for using the SERVER
methodsteamWebAPIKey
is always required, it doesn't matter which key you useExplanation of each value:
Number
: Amount of commends you want to send as friendlyNumber
: Amount of commends you want to send as teachingNumber
: Amount of commends you want to send as leaderNumber
: Amount of reports you want to send as aimbottingNumber
: Amount of reports you want to send as wallhackingNumber
: Amount of reports you want to send as other hackingNumber
: Amount of reports you want to send as abusive communications or profileString
: Username of the account you want to boostString
: Pasword of the account you want to boostString
: Optional shared secret if the account has two factor authenticationString
: Username of the account you want to use for automatically fetching serverID
/matchID
String
: Password of the accountString
: Optional shared secret of the accountNumber
: Maximum amount of tries before cancelling fetchingNumber
: Amount of milliseconds to wait between each tryBoolean
: Set to true
if you want the script to ask for Steam Guard code, false
to just error and cancelBoolean
: Whether or not proxies are suppose to be usedString
: The filename you want to load proxies from (With extension like .txt
or .json
) - Read MoreNumber
: One proxy per X accountsString
: Define the type - Valid values are COMMEND
& REPORT
- Read MoreString
: Define the method - Valid values: LOGIN
& SERVER
- Read MoreString
: SteamID/VanityURL/ProfileURL of targetString
: ServerID, or IP, or auto
of the server - Read MoreString
: Optional match ID (Use "0"
if you don't want to use one) - Read MoreNumber
: Will chunk all accounts into groups of perChunk
sizeNumber
: Delay in milliseconds between chunksNumber
: Cooldown in milliseconds to not reuse accountsBoolean
: Whether or not to print commends at the start and end of commending (Enabling this requires a fetcher account)Boolean
: If enabled and target is on a Valve Matchmaking server wait until the match has ended (Enabling this requires a fetcher account)Number
: When using LOGIN
method switch server automatically after this many chunks have been processedString
: Either Auto
, TCP
, WebSocket
, or WebCompatibility
- Specify the connection protocol to use for Steam. Try changing this if you encounter Method Not Allowed
String
: Steam Web API key from hereBoolean
: Whether or not to skip update checksExport account list
: Export all accounts in a username:password
formatList commends for user
: List all accounts which have commended a specific userReset commends for user
: Delete all commend entries from the database of a specific user (Note: This does not remove commends from the target in-game. You will likely never have to use this)Remove account from database
: Delete a specific account from the database including commend history *Add account(s) to database
: Add accounts to the database, import from JSON file, import from username:password
file or manually add accountsList not working accounts
: List all accounts which are marked as inoperational by the scriptRemove all not working accounts
: Remove all accounts which have been marked as not working *Get last commend target and time
: Retrieve the last target and time at which we commendedReset Database
: Will clear out all content of the database, resetting it to the defaultExit
: Safely close database before exiting processSimply run it via node databaseManager.js
, use the arrow keys & enter to navigate. Read on-screen instructions for more details.
* Commend history is important, removing it will cause the script to re-use already used accounts which will result in duplicate commends, which does not work and will therefore do nothing until commend history has been rebuilt.
You can choose between two types, COMMEND
and REPORT
.
There isn't much to it. Commending botting is confirmed to work, report botting is impossible to prove working due to many factors which cannot be controlled. I believe report bots haven't worked since 2016 due to how simple it is to prevent them working. Don't try to lecture me, I don't care.
You can choose between two botting methods, LOGIN
and SERVER
.
LOGIN
will log into the targets account and automatically grab a server. Fastest, easiest and most lightweight (No need to run CSGO) for personal usage
SERVER
will commend a target, but the target has to be on a valid Valve or Community server - Read More
serverID
field allows for either ServerIP, ServerID or auto
.
status
into the console ingame.1.37.0.1/13701 934/7508 secure [A:1:1297634312:12708]
> [A:1:1297634312:12708]
.Connected to =[A:1:3849827331:12657]:0
> [A:1:3849827331:12657]
.auto
will work on any server, community server require the target to use cl_join_advertise
to be 2
or higherfetcher
sectionmatchID
field allows for either MatchID or auto
.
match_id=3243320471183730331
> 3243320471183730331
auto
will automatically find the match ID for youfetcher
sectionProxies are simple to use, just follow the example config to set them up. Your proxy file will need to be either a JSON array with each element being one HTTP proxy or a plain text file with each line being one proxy. One proxy can do ~20 commends, so I recommend leaving switchProxyEveryXaccounts
at 20
.
ONLY HTTP proxies are supported
JSON Example:
[
"127.0.0.1:12345",
"127.0.0.1:67890",
"127.0.0.2:12345",
"127.0.0.2:67890"
]
Plain text example:
127.0.0.1:12345
127.0.0.1:67890
127.0.0.2:12345
127.0.0.2:67890
I am getting timeout errors
Can I get banned for using this?
I get an error when trying npm ci
node-v12.9.1-x64.msi
.How many commends can I send?
I get a proxy error!
I get an "Failed to commend" error
The config is confusing, can you make an interface for it?
Can I make an automated commend selling service with this?
Can you do X for me?
Can you do X for me? I pay!
I found someone who copied this and is selling it/released it without mentioning you.
Lets start by saying: None of this is confirmed, nobody knows what the truth is so these are just assumptions.
Aside from Valve literally saying they are fixed every match (Competitive, Wingman, Danger Zone, etc) has a list of account IDs which are allowed to join/participate, so when a report gets sent all Valve has to do is check if the sender and receiver are in the same match or not.
Now you could argue why doesn't the same happen when commending or why do they give a fake response? The answer is: Community servers.
Commending must work on community servers so it is not as strict as reporting. Reporting on the other hand is completely irrelevant on community servers, there is no reason why Valve should use them especially considering community servers may give advantages to some players, so reporting simply returns a fake response.