-
Notifications
You must be signed in to change notification settings - Fork 22
Troubleshooting
Check/try the following:
- If you have multiple monitors, make sure Kantai Collection is running on the primary monitors. Sikuli can only find windows on the primary monitor.
- Make sure your Kantai Collection game window is scaled/resized to 100% (no resize). kancolle-auto only works if your game is in its original scale.
- Disable any extensions or plugins that might obstruct the Kantai Collection game window.
- The moment the script starts, manually click on the game window to switch focus to it.
A: If you are on Windows, please try disabling time synchronization on the OS level (relevant information). If that doesn't work, try raising the SleepModifier field in the config to 1, 2, or 3. If this does not reduce the number of crashes, then please open a detailed issue ticket.
If you are getting the above error on Windows, try running the command chcp 437 in the command prompt before running kancolle-auto.
Generally, if the script crashes, simply restarting the script should let kancolle-auto recover gracefully, especially if the crash is transient and does not occur consistently. If you're in a sortie, please get back to the Home screen before restarting the script. If the crash does occur consistently at a specific point/scenario, please create an issue ticket.
Possible reasons for the transient crashes:
- Sikuli, the program this script relies on for button/screen recognition and OCR, can mis-identify portions of the screen or mis-click at times. The script might fail as a result.
- Sikuli sometimes can't outright find/match portions of the screen properly. The script might fail as a result.
- I tried to make the sleeps and delays as flexible as possible, but if Kancolle takes too long in certain screen transitions due to slow internet connections/unresponsive Kancolle servers/etc. the script might fail as a result.
If you suspect that your crashes are caused by any of the above, try increasing the SleepModifier parameter in config.ini to 1 or 2.
To help debug, run Sikuli with the -d 3 flag (for debug level 3) which will print verbose logs to the console. Sometimes verbose console logs can help identify the issue when creating a ticket on the issue tracker.