The project is discontinued
This project was forked from Jessecar96's SteamBot, a fully automated trading software made specifically for http://market.csgo.com.
Ordinary usecase is as follows:
You should have multiple pods (instances of software) running. One being the master node, others being worker nodes.
To compile master node compile it with CORE constant defined.
Master node is used to load-balance between steam inventories and monitor running pods.
Without having master node, all worker nodes act independently of each other, with no possibility of load-balancing (thus overflowing steam inventory limits).
Master node domain should either be hard-coded Global config in code or overriden via settings.json.
settings.json should be defined as follows
If settings.json is not specified it will be pulled via HTTP request from master node.
To run master pass arguments in format <port> <MasterConfigUrl> MasterConfig.json
To run worker pass arguments in format <WorkerConfigUrl> <SteamBot default options(optional)> WorkerConfig.json
One could potentially run multiple steam accounts from the same machine, yet this is not recommendded due to Steam API being highly unreliable and severe restrictions could apply when running more than a dozen accounts due to Steam authentification protocols.
Worker and master nodes require MongoDB to store logs, keep track of market sale history (for further use by analysts), frequently update ban list, since scamming on steam is very frequent.
It is recommended to run single mongod replicaset for master and all worker nodes.
A list of contributors:
This bot:
- Noobgam (project lead)
- AndreySmirdin analyst
SteamBot contributors: