It is necessary to develop and configure a bot for CS2 that can autonomously navigate the map, react to the game situation, shoot, perform basic actions in the match, and operate stably without constant manual control. There are also some existing materials that can assist in the development, so the project does not need to be done completely from scratch.
Here is the technical specification for the development of the second part of the panel and the bot for CS2.
General Task
It is necessary to develop a desktop/web panel for managing CS2 bots, as well as the bot itself for automatic operation in the game.
The project should be built as a complete management system:
accounts;
VM;
proxy/VPN;
bot launch;
analytics;
HWID profiles;
Telegram notifications;
logs and statistics.
There are examples from competitors and some source codes/ready-made solutions that can be used as a base or reference.
1. Bot Functionality
Basic Behavior
The bot must:
autonomously enter a match;
move around the map;
orient itself in space;
react to opponents;
shoot;
perform basic actions;
not hang after matches;
automatically switch to the next account;
maintain a stable work cycle.
Logic
It is necessary to think through:
anti-AFK behavior;
randomness of movements;
different behavior scenarios;
a recovery system after errors;
automatic restart.
2. Control Panel
Dashboard
On the main screen:
active VMs;
number of accounts;
number of drops;
earnings statistics;
average working time;
bot statuses;
live statistics.
Account Management
It is necessary:
to import accounts;
to edit;
to group;
to filter;
to launch individual accounts;
to mass launch;
to bind proxy/VPN;
to bind HWID profile.
Account Statuses
Statuses:
working;
error;
completed;
waiting;
blocked;
restarting.
3. VM / Virtual Machines
VM Support
It is necessary:
to launch through VM;
separate configs for each VM;
to manage multiple VMs;
automatic launch;
load monitoring;
to check VM stability.
Quick Deployment
It is desirable:
VM templates;
auto-import of configs;
profile saving;
automatic setup.
4. HWID / Fingerprint System
It is necessary to implement a system for working with HWID profiles.
It should include:
a separate HWID profile for each account;
generation/modification of parameters;
binding HWID to VM;
profile saving;
profile switching.
Display in the panel
Show:
MachineGuid;
MAC;
Product ID;
Steam MachineID;
HWProfileGuid;
other system parameters.
5. Proxy / VPN
Proxy System
It is necessary:
support for SOCKS5/HTTP;
IP rotation;
proxy testing;
mass addition;
binding proxy to account.
Work Logic
IP retention for accounts;
automatic selection;
blacklist problematic IPs;
rechecking proxies.
6. Telegram Bot
It is necessary to implement:
Telegram notifications;
remote control;
statuses;
error messages;
drop messages;
start/stop via Telegram.
7. Analytics
Drop Analytics
It is necessary:
drop history;
prices;
profit;
account statistics;
VM statistics;
graphs;
average profit.
Archive
launch history;
launch logs;
errors;
drop history;
sorting and filtering.
8. Settings
Main Settings
auto-start;
repeat problematic accounts;
timers;
limits;
Steam configuration;
VM configuration;
logging.
DEV / TEST MODE
A separate test mode:
proxy checking;
launch testing;
account testing;
work emulation.
9. Interface
Style:
modern;
dark UI;
minimalistic;
fast;
user-friendly.
It is necessary:
to think through UX;
to create clear navigation;
to optimize for a large number of accounts.
10. Requirements from the Developer
to fully think through the architecture;
to propose a technology stack;
to assess the load;
to outline the development stages;
to describe risks;
to describe possible limitations;
to prepare a development roadmap.
It is also necessary to immediately assess:
approximate timelines;
complexity;
what is better to do as separate modules;
what can be implemented through ready-made solutions.