Quote:
Originally Posted by AnAnonyymous
Hey phat34,
The problem seemed to be caused whenever the waitmapload() was too short.. maybe due to ping or lag or w/e... anyway i have increased the time in the gwa2 for waitmapload() so now it just waits a bit longer before calling the first movement command. Like i said as for now the problem seems to be solved but we'll see.
|
About that "Func WaitMapLoading($aMapID = 0, $aDeadlock = 10000)", you can indeed tweak the $aDeadlock value in GWA2.au3 to make it wait longer by default.
Another way to fix your issue without tweaking GWA2 is to just change the call at bot level such as :
Code:
WaitMapLoading($aMapID, 15000) ;Wait 15s instead of 10 before exiting function
;VS
WaitMapLoading($aMapID) ;Wait 10s before exiting function (default GWA2 value)