Guide/Help

Reporting a problem

Found a bug? Tell us on our Discord. With the right information we can usually fix it quickly.

What to send

  1. What you expected and what happened instead. "It flew to 1-1 instead of 2-1" is perfect. "It's broken" isn't.
  2. Roughly when it happened.
  3. The log file from that run (see below).
  4. A screenshot if it shows something useful. Leave Streamer on, so names and addresses are hidden.

Find the log file

LeanBot writes one log file per account, per run, named like leanbot-<date>-<account>.log. The last 20 per account are kept.

  1. Press Logs in the LeanBot window's top bar. A folder opens. (This button is only in the window, not in a browser.)
  2. Find the newest file for the account that had the problem. Sort by Date modified if you're not sure.
  3. Send us that file.
Good to know

The log lives in the data\logs folder inside your LeanBot folder.

Good to know

The log hides what is personal. IP addresses, proxies and your game user ID read [hidden], and your accounts and pilots read Account 1, Account 2 and so on, numbered as in your Accounts list. Only the file's name still has the account's name in it: rename the file before you post it if you'd rather it didn't.

If LeanBot crashed

If the window disappeared by itself, LeanBot writes a crash report to the data\crash folder (crash-<date>.txt). Send us the newest one, together with the log file of the account that was running.

Careful

Never send anyone your accounts.json or proxies.json files, or your DarkOrbit password. We never need them, and anyone asking for them is not us.

Still stuck?Ask on our Discord. Say what you pressed and what happened, and send the newest log file (the Logs button in LeanBot's title bar).
Ask on Discord