jduartedj wrote:What I mean by delta is:
While the cast bar disappears and the bot starts doing something else.
lets say the bot encourages the chicken and then collects it's egg. While the cast bar is on until it is finished and moving to the next step, it takes roughly 2000ms, whereas if you make the time 1500 manually it'll start doing the next task, collecting the egg right away, delta is this diff between the 2000 and the 1500.
So you are saying that by setting the waittime to 1500ms you reduced the time by 500ms? That shouldn't happen because either way target_Object will wait until the castingbar disappears then continue. Are you 100% sure that it reduces the time?
jduartedj wrote:But what ur sayin is makeing more sense, I though the cst bar would actually take 2000 ms, but you say it takes 1500 so I think it indeed takes 1500 but the lag/performance/etc makes the value to be bigger.
No what I was saying was, after it's clicked the hen and collected the first egg, that's how often it checks to see if the next hen is clickable. The way it should work is it should click the first hen, then immediately after the castingbar disappears, collect the first egg. Then it loops 1500ms in the 'while' loop until it can click the next hen. Optimizing the waittime is not really possible as, when I was testing it, I found the time before the next hen is clickable was variable.
jduartedj wrote:Anyway does your castbar check take any romscript or aything that takes >500ms to check when you set waittime to nil instead of putting a manual time? Because i think that my "delta" comes from that.
There are no RoMScript commands in player:target_Object besides the 'UseSkill(1,1)' commands. Actually, if you are looking for delays, if there is a waittime and the castingbar doesn't appear(like what happens with the coop hens), it will try the RoMScript("UseSkill(,1,1)") command again. So having a waittime will cause an extra RoMScript on the second and third hens.