Running it

From key to first battle.

Four steps, and about two minutes. The bot checks your key before it logs in, so a run that is not paid for stops before it touches your account.

Step one

Put the key where the bot can see it

The key goes in wg-secrets.local.ini next to the bot, or in the WG_LICENSE_KEY environment variable. Either works; the file wins.

[wotgrinder]
license_key = WG-XXXX-XXXX-XXXX-XXXX

The file is git-ignored. The key is never sent anywhere except the licence server, and the server only keeps a hash of it.

Step two

Check that everything is in place

The bot carries the client's own data files, so it does not need the game installed. This command proves they are readable:

python -m steelwire --doctor

It prints one line per file and ends with what it found. If a file is missing, the bot says which one and where it should be.

Step three

Start a session

This is the whole run: log in, pick a tank, queue, take the battle, and report the frame to your dashboard.

python -m steelwire \
  --licence WG-XXXX-XXXX-XXXX-XXXX \
  --account main \
  --battle --enter-battle \
  --auto-vehicle \
  --listen 30 \
  --queue-wait 300
--licenceYour key. It can also sit in the secrets file, and then you do not need it here.
--accountThe profile name in credentials.ini. Without it the first profile is used.
--auto-vehicleLets the knowledge database choose the tank: the crewed, armed one that fits the missions and the map.
--listen 30Seconds to listen for battle traffic after each queue attempt.
--queue-wait 300How long to wait for the matchmaker to hand you a battle server.
Step four

Watch it on the dashboard

Open the dashboard while the bot runs. The frame arrives over HTTPS every two seconds and the page redraws in place — the map, the damage, the contacts, the research, the battle pass.

A dash means the bot has not reported that value yet. Nothing on the dashboard is filled in until the bot has actually measured it.

Without a key

Looking around is free.

The knowledge database, the grinding guide and the account report do not need a key. They read the client's own data and the account cache; they never talk to the licence server.

Read the game data
python -m steelwire \
  --knowledge summary

Every nation, vehicle, module, mission and campaign, read from the client's own files.

Read the account
python -m steelwire \
  --report

Profile, currencies, garage, research, missions, pass and what is worth doing next. Read-only.

Plan a battle
python -m steelwire \
  --intel \
  --map prokhorovka

The briefing for one map: what to take, what to avoid, and why.

When it does not work

The four failures you will actually hit

"no licence key" The key was not found. Pass --licence, or put license_key in the secrets file next to the bot.
"the licence was refused" The server's own reason, printed as it stands: expired, revoked, or bound to another machine. A key that was copied to a second PC stops working there, on purpose.
"the licence server could not be reached" No network, or a proxy in the way. The battle carries on without the dashboard; the licence is not affected.
The queue never accepts Check --account and --service against your region. --mode proxy falls back to the relay when a direct UDP path is blocked.