I will stop adding anymore functions and focus on fixing the hang problem.

About the hang or white screen, it is due to memory leak of the functions that locate color pixels. When it uses DLLCall it uses up memory and it is not properly disposed therefore memory leak. I'll look into this more later but that is the reason my version hangs earlier as it uses that function more often.

I was monitoring the memory usage of the bot and whenever traning troops and "not dead base, skipping" gets triggered the memory usage blows up and never goes down. In training troops, the moment it clicks a unit  it adds .03-.05 and everytime i see "not dead base , skipping" it adds .30-.40 of mem.

not sure if my computers bad or its a glitch but when the bot started to attack it froze my computer

i had same problem.after i deleted ddl files than it works for me

Do you think it would be ideal to do the old way of LF robot style where we force close the script and reopen it in case it freezes? like most of the time its building anyway

whats the best tolerance for you guys ? its been attacking people with the least uncollected resource for me and detects it as dead bases.



the old version only attacked bases like this

Refer to post #12 for why dead base not effective
https://the.bytecode.club/showthread.php?tid=213&page=2

does not attack when I get that kind of error will make the bot attack and closing