-
-
Notifications
You must be signed in to change notification settings - Fork 20
Logs can be found by opening the WAI2K folder usually located at C:\Users\<user>\.wai2k\wai2k\debug.log (Windows) or ~/.wai2k/wai2k/debug.log (Linux).
When a crash occurs, the script usually takes a screenshot and saves it under C:\Users\<user>\.wai2k\wai2k\debug\ (Windows) or ~/.wai2k/wai2k/debug/ (Linux).
You can also open the WAI2K folder in the menu bar under Files>Open WAI2K Folder
Consider submitting the last crash screenshot and debug.log file when trying to get help.
If you are a new player, you will be lacking some buttons in your home status menu (the yellow tab on the home screen). This can be fixed by completing 60 missions to unlock fairies and clearing up to 8-5 to unlock HoCs. Typically the only 'game' requirement to use the bot are these two. The combat module requires seeing the 'fairy counter' in the combat screen which is unlocked after clearing 60 missions. Home_Status check requires all the button in the home status screen (yellow button on the home screen) which requires clearing normal maps up to 8-5.
If you get this error either the emulator has crashed which means you have to restart both the emulator or bot. Or you have training happening under your 4 logistics teams. Simply remove the T-Doll from the formation that is in training in formations under the logistics teams and this error should fix itself. It is recommended to have your logistics teams as your last 4 formations to prevent this error.
Sometimes the bot will error during battle and restart (if game restart is turned on). The most common reason for this to happen is your battle timeout under 'Profile > Combat' is set too low. If you are taking a while for your battles then you may want to set this to something higher. Keep in mind that the Android emulator tends to slow down with prolonged use so if your battle timeout works initially it may not work when the emulator slows down. If you notice significant slowdown issues after prolonged use, try a higher battle timeout. 60 seconds is the default but you may need something more than 95 seconds depending on your situation. It is also recommended to turn on GPU acceleration if you have an Nvidia GPU and follow the tips for your CPU to speed up your emulator.
The bot views logistics timers through the yellow tab on the home page. If some echelons are obscured (either thorough combat, repairs or training). It will not detect the logistic timer and attempt to send it thinking it is not sent. The fix to this is either start on the yellow tab with all logistics teams visible or remove all combat echelons and t-dolls in repairs/training from your echelons so they don't show up.
Ubuntu users (and some Linux) will need to download this package: https://www.ubuntuupdates.org/package/core/focal/universe/base/tesseract-ocr
On the off-chance that you turned on USB debugging, have resolution set and are on Android 7 and the IP connect is not working or showing it as listed devices then you may need to find the port that Nox is on.
To do this first open up task manager > go to details tab > find a process name called "NoxVMSVC.exe" and note the process ID (usually in the column right beside the process name). Then open up cmd and type in "netstat -aon | findstr PID" where PID is your process ID from the previous step. Next it will show up with a bunch of ports that are LISTENING in the second column. Find the next port number that is >=62001 (in my case it was 62026). Go back to Wai2k and connect to IP using the new port.