Troubleshooting Guide

Steps to fix:

1. 1Make sure you are using the correct email address and password for your Kingshot Bot account.
2. 2Check that Caps Lock is off.
3. 3Use "Forgot Password" on the login page to reset your password if needed.
4. 4If you registered with a social login, use the same method to sign in.

Steps to fix:

1. 1This happens when your game Session Key rotates (e.g. you logged in on another device).
2. 2Open the Kingshot game in your emulator and log in once.
3. 3Re-extract your credentials using the extraction tool at /guide/extract-credentials.
4. 4Update the account in Kingshot Bot with the new Session Key.

Steps to fix:

1. 1Make sure you copied the full FPID and Session Key without any extra spaces or line breaks.
2. 2Verify you opened the correct XML file: com.cg.sdk.xml in /data/data/com.run.tower.defense/shared_prefs/
3. 3Try logging in to the game again and re-extracting the credentials.
4. 4Use the automatic extraction tool to avoid manual copy-paste errors.

Steps to fix:

1. 1Check your internet connection — open a browser and verify you can reach websites.
2. 2Temporarily disable your VPN or antivirus and try again (they can block outgoing connections).
3. 3Restart the bot client.
4. 4If using a proxy, verify the proxy is online and the credentials are correct.
5. 5Check our Discord for any known server outages.

Steps to fix:

1. 1Check your internet stability — use a wired connection if possible.
2. 2If you are on WiFi, move closer to your router or switch to a 5 GHz band.
3. 3Test without a proxy to rule out proxy instability.
4. 4Increase the Action Delay setting slightly to reduce connection load.

Steps to fix:

1. 1This usually means you started more distinct game accounts than your plan has slots. Unbound accounts are blocked — on current bot versions the whole session can stop with a connection error for about 30 minutes.
2. 2Open Dashboard → Accounts and check the Linked Game Accounts list to see which game accounts are bound to your slots.
3. 3Release a bound game account to free a slot (this uses one monthly swap), or wait ~30 minutes for the cooldown and start only your bound accounts.
4. 4If you need more simultaneous accounts, buy extra slots or upgrade your plan from the billing page.
5. 5Note: using the offline scheduler across more game accounts than your plan's slots is not supported.

Steps to fix:

1. 1Verify the proxy host, port, username, and password are correct.
2. 2Use the "Test Connection" button in the proxy settings to diagnose.
3. 3Check with your proxy provider that the proxy is active and your plan is not expired.
4. 4Make sure the proxy supports SOCKS5 — HTTP proxies are not supported.

Steps to fix:

1. 1Make sure you are logged in to the bot client with the same email address linked to your subscription.
2. 2Check that your subscription is active in Dashboard → Settings → Billing.
3. 3Restart the bot client after confirming your subscription is active.
4. 4Contact support if the issue persists after checking the above.

Steps to fix:

1. 1Log in to your Kingshot Bot dashboard.
2. 2Navigate to Settings → License and click 'Reset HWID'.
3. 3Restart the bot client on the new machine.
4. 4Note: You are limited to 2 HWID resets per month.

Steps to fix:

1. 1HWID resets are capped at 10 per month to prevent abuse.
2. 2Wait until the start of the next calendar month for the limit to reset.
3. 3If you have a genuine urgent need, contact support on Discord with your account details.

Steps to fix:

1. 1Make sure at least one feature toggle is enabled for the account.
2. 2Check that the account is connected (green status indicator).
3. 3If you set a schedule, verify the current time falls within the active window.
4. 4Check the bot log for any error messages that may indicate why actions are paused.

Steps to fix:

1. 1Ensure you have enough resources — the bot will not train if resources are below your configured minimums.
2. 2Verify the specific feature (e.g. Infantry Training) is toggled on.
3. 3Check that you have free builder or barracks slots in-game.

Steps to fix:

1. 1Confirm you have free march slots available (not all marches already deployed).
2. 2Check the resource level filter — if set too high, no nodes may match.
3. 3Verify the Gathering feature is enabled for this account.

Steps to fix:

1. 1Check the Action Delay setting — a high delay (above 5 seconds) will visibly slow down the bot.
2. 2Running many accounts simultaneously on a low-spec machine can also increase latency.
3. 3Close other applications to free up system resources.

Steps to fix:

1. 1Make sure you are running Windows 10 or 11 (64-bit).
2. 2Re-download the client from your dashboard in case the installation is corrupted.
3. 3Temporarily disable antivirus and try again — some AV software flags bot clients.
4. 4Add the bot executable to your antivirus exclusion list if that resolves it.

Steps to fix:

1. 1Each account uses about 256 MB RAM. If running 5+ accounts, ensure you have enough free RAM.
2. 2Close unused applications to free memory.
3. 3Check that no antivirus scan is running simultaneously while the bot is active.

Steps to fix:

1. 1Game updates sometimes change the server protocol. Check Discord for announcements about compatibility.
2. 2Make sure your bot client is on the latest version — check the download page in your dashboard.
3. 3If a bot update has been released, restart the client to apply it automatically.