Bug with iDelay handling

in
Subscribe to Bug with iDelay handling 2 posts, 2 voices



fcs User

Hi,
I think there are two bugs with the iDelay handling:

- line 1593: if (iDelay>0 && useOfIDelay)... and on the else block it re-schedules the task after the last task. However the message at Delay if error window says "type 0 to not add". So when I try to disable this feature by setting delay time to 0 then the failed task gets re-scheduled after the last task instead of not to be re-scheduled at all. I think the correct code would look like this: if (useOfIDelay) { if(iDelay>0) {...} } else { ... }

- when re-scheduling happens the task gets re-scheduled to the current active village instead of the one in the failed task. I guess the problem is that the getActiveVillage function in setTask uses the html page to determine the village id, but the switchActiveVillage function just calls the url but does not change the html page in the browser. But I am not sure about this.

 
blablubbb Scriptwright

"- when re-scheduling happens the task gets re-scheduled to the current active village instead of the one in the failed task. I guess the problem is that the getActiveVillage function in setTask uses the html page to determine the village id, but the switchActiveVillage function just calls the url but does not change the html page in the browser. But I am not sure about this."
Same problem here... You need to calculate correctly so you can shedule all tasks ... Not easy... Have you tryed to set delay time at "-1"? At some codes such things work.

Cross
Presentational HTML allowed.
Use <code> for inline code and <pre> for code blocks. Use &lt; and &gt; for literal < and >.
We help break paragraphs and link your links.
or cancel