Open mitfry opened 9 years ago
The bot can't read your troop counts for some reason. I have implemented temporary fix in 2.6.0
I am using the latest version: v2.6.0. The issue still occurs in that build.
Is there anything I can do to help fixing this bug?
On line 2 of cocbot\functions\strategies\standard\readycheck.au3 add the following line:
$stuckCount = 1
You will have to then right-click and recompile (x86) on brokenbot.au3 but that should hopefully help you until I can get a real fix done for you.
Thanks. I'll report back in a couple of minutes.
It seems to be running slightly better now. Still getting the same error but it keeps recalculating the required troops now. Good thing is that it doesnt start attacking before the troops are ready. Bad thing is that It removes troops before they are finished training and then adds them again. It gets the recalculating amounts right though but it adds the wrong amount and it keeps passing the max of 200 troops. It seems to be ignoring part of the troops that are already in the camps.
Ok, so a better option for you to prevent that from happening...delete the $stuckCount = 1 and change it to $TimeSinceNewTroop = 0
Changed the $stuckCount = 1 to $TimeSinceNewTroop = 0 as you said and so far so good. Been running for over 15 minutes now without seeing the error. It also hasn't unnecessarily removed and added troops. It now only prints the line "Forces needed" once every cycle altough it still adds the right troops, even after coming back from an attack.
You might have yourself a possible workaround for now :)
On a sidenote: When deploying troops. It seems to ignore the settings to deploy near the red line and the settings to delay deploying to look more human like.
EDIT: After a full cycle of attacking -> retraining troops -> attacking -> retraining troops it unnecessarily removed and added troops once and has been passing 200/200 ever since again but only by a small amount like 202/200. What's odd is that it reports training 183 troops while it actually is training 202. That counting part going wrong might be the cause of this problem.
Anyway im off for tonight, will be back tomorrow. Hopefully i provided you with some usefull information.
After around 5 minutes of waiting for training troops to complete, BrokenBot suddenly decides to reset troop counts. After the reset is done, BrokenBot starts searching for a match while barely ANY troops are ready.
Below is a part of the log. At first you can see all is fine until 23:50:59 when it suddenly gets stuck. After that the bot loses count and becomes unusable. The only solution is to turn it off.