testing
You mean timerd?
timerd here 1 is the same of 0.5, 0.4, 0.3 etc...( as i remeber, years ago i treid to use and gave up)
I think when you put 0 to 0.4 it runs as timer 0, when u put 0.4 to 0.9, timer will be 1 second, something like that
No differences
EDIT: i made the tests
Code:
[FUNCTION timerdt] //sendpacket 0A2 D01a4b6 w120 w100
sysmessage ------
serv.newitem i_timerdtest
new.cont <uid>
new.amount 7
new.timer 1
serv.newitem i_timerdtest
new.cont <uid>
new.amount 6
new.timerd 0.7
serv.newitem i_timerdtest
new.cont <uid>
new.amount 5
new.timerd 0.5
serv.newitem i_timerdtest
new.cont <uid>
new.amount 4
new.timerd 0.5
serv.newitem i_timerdtest
new.cont <uid>
new.amount 3
new.timerd 0.4
serv.newitem i_timerdtest
new.cont <uid>
new.amount 2
new.timerd 0.2
serv.newitem i_timerdtest
new.cont <uid>
new.amount 1
new.timerd 0.1
It is so unstable:
Not always they appeared on same standard:
example, sometimes it appears 1 and 2 instant, then 3 4 and 5 togheter.
Sometimes all of them together
And look, they even change the order:
Second test:
Sometimes 1, 2 and 3 instant, then one second later, then 4, 5, 6 ,7 instant.
Sometimes 1, 2 instant, then one second later 3, 4, 5, 6 ,7 instant.
Sometimes 1, 2 ,3, 4 instant, then one second later 5, 6 ,7 instant.
very very unstable
With a local connection.
using serv.time to test:
Code:
[FUNCTION timerdt]
ctag.rt <serv.time>
sysmessage ------
serv.newitem i_timerdtest
new.cont <uid>
new.amount 7
new.timer 1
serv.newitem i_timerdtest
new.cont <uid>
new.amount 6
new.timerd 0.7
serv.newitem i_timerdtest
new.cont <uid>
new.amount 5
new.timerd 0.5
serv.newitem i_timerdtest
new.cont <uid>
new.amount 4
new.timerd 0.5
serv.newitem i_timerdtest
new.cont <uid>
new.amount 3
new.timerd 0.4
serv.newitem i_timerdtest
new.cont <uid>
new.amount 2
new.timerd 0.2
serv.newitem i_timerdtest
new.cont <uid>
new.amount 1
new.timerd 0.1
[itemdef i_timerdtest]
name=a-apvp
ID=i_memory
TYPE = t_eq_script
LAYER = 30
ON=@CREATE
ATTR=attr_decay
on=@timer
cont.say <amount> <fval <serv.time>-<cont.ctag.rt>>
remove
return 1
Completely different numbers each time, many variations:
unusable