Skip to content

Troubleshooting

Jump to bottom
Nexor256 edited this page Jun 5, 2026 · 1 revision

Troubleshooting

This page covers the most common problems users run into and how to fix them. If your issue is not listed here, please open an issue or ask in Discussions.

App Won't Start

"Config file is missing"

The app expects config.json to exist next to the main executable. Launch the app once from the installer shortcut — it creates this file automatically on first run.

App stuck on "Initializing Sidecar"

Windows Defender has likely quarantined scanner_sidecar.exe because the Nuitka-compiled binary triggers a false positive.

Fix:

  1. Open Windows Security (search for it in the Start menu).
  2. Go to Protection History.
  3. Find the blocked threat for scanner_sidecar.exe.
  4. Click on it and select Restore or Allow on device.
  5. Restart the app.

Sidecar won't start (no Defender alert)

Check the sidecar.log file in the app directory for specific error messages. Common causes:

  • Missing dependencies in the deps/ folder.
  • A corrupted download — try re-downloading the installer.

Emulator Issues

Emulator not detected

  1. Make sure ADB is correctly placed in deps/platform-tools/ (you should see adb.exe inside that folder).
  2. Verify that Android Debug Bridge is turned on in Bluestacks Advanced settings.
  3. Restart the emulator after enabling ADB.

ADB port not found automatically

If the app cannot detect the port:

  1. Check that the bluestacks.conf path in Settings is correct (usually C:\ProgramData\BlueStacks_nxt\bluestacks.conf).
  2. Make sure the instance name in Settings matches your Bluestacks instance exactly.
  3. If the config file does not exist, your Bluestacks installation likely uses a fixed port. Try setting the port manually to 5555.

Scanning Issues

Scan produces incorrect or garbled data

  • Make sure Bluestacks resolution is set to 1600 x 900 and DPI is Custom (450). Other resolutions will break the OCR.
  • Your game language must be English. Other languages cause issues with text recognition and inactive detection.

Governor names contain wrong characters

  • Chinese and special characters may appear incorrectly in the terminal output, but they should be correct in the saved output files (XLSX, CSV, JSONL).
  • Avoid copying anything to the clipboard while a scan is running — the scanner uses the clipboard to capture governor names.

Kill values seem wrong

Enable Kill Validation in the Kingdom Scanner settings. This feature compares kills against kill points using known ratios and flags suspicious values. Flagged screenshots are saved to manual_review/ for you to check manually.

You can also enable Kill Reconstruction to let the scanner attempt to fix misread values automatically.

Scan skips too many governors / scans wrong data

  • Your character must be in the Home Kingdom to see only your kingdom's rankings.
  • Your account must rank lower than the number of governors you want to scan.
  • Make sure you start the scan from the top of the ranking list.

Output Issues

"deps not found" or scanner fails immediately

The deps/ folder and its contents are required. Make sure you have:

See the Installation page for full instructions.

Still Need Help?

When asking for help, please include:

  • A clear description of the problem and the steps to reproduce it.
  • Your app version (visible in the Settings page).
  • Your sidecar.log file (in the app directory).
  • Your config.json file (remove any personal file paths before sharing).

You can reach out through:

Made by Nexor256.
Return to main repository

Getting Started

Reference

Community

Clone this wiki locally