thanks for the feeds, yup thats the mod4(b) bug.
mod4(b) init the time to a given var first b4 casting tiime. it should be cast time then init the var. oh well watevr, it still a bug, and fixed.
CT works like same as in game casting of skills, the difference is that our bot doesnt have the capability to detect what skill is still in CD and what is still in casting in game, so to have the timing effect in casting of our bot, we need also CASTING TIME.
for example, casting stun skill, how long it will take to finish the cast? let say 2 secs, that will be the value of CT, and how long it will take to cast again which is cool down, that will be the value for the box before CT, sec(s).
e.g.
skill 1 slot [9] sec(s) [2] CT
why must have CT?
to prevent ignoring next skill if all skills has the same value of cool down time.
how?
CT act as a delay in macbot. if we will not include CT, all skills with the same value will be casted without the right timing in zx client. if we noticed in cdbot, skill sometimes casted somestimes are not.
and another thing all input box from 1 - 5 are can now accept 0 value in sec(s), means no cool down time for example your "common attack" can be like this (this works only in mod4(c) version)
skill 1 slot [0]sec(s) [1]CT