The following warnings occurred:
Warning [2] Use of undefined constant SAPI_NAME - assumed 'SAPI_NAME' (this will throw an Error in a future version of PHP) - Line: 3388 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3388 errorHandler->error
/showthread.php 116 build_archive_link
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/inc/functions.php 3324 build_forum_breadcrumb
/showthread.php 195 build_forum_breadcrumb
Warning [2] Use of undefined constant IN_ARCHIVE - assumed 'IN_ARCHIVE' (this will throw an Error in a future version of PHP) - Line: 3331 - File: inc/functions.php PHP 7.4.33-nmm7 (Linux)
File Line Function
/inc/functions.php 3331 errorHandler->error
/showthread.php 195 build_forum_breadcrumb






Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
tenths of a second timer
Author Message
ChaveS
Journeyman
*

Posts: 69
Likes Given: 0
Likes Received: 0 in 0 posts
Joined: Oct 2012
Reputation: 0



Post: #3
RE: tenths of a second timer
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:
[Image: timerd.jpg]

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:
[Image: timerd2.jpg]

unusable
(This post was last modified: 11-16-2012 09:43 AM by ChaveS.)
11-16-2012 08:45 AM
Find all posts by this user Like Post Quote this message in a reply
Post Reply 


Messages In This Thread
tenths of a second timer - ChaveS - 11-16-2012, 03:47 AM
RE: tenths of a second timer - Mordaunt - 11-16-2012, 06:13 AM
RE: tenths of a second timer - ChaveS - 11-16-2012 08:45 AM
RE: tenths of a second timer - Skul - 11-16-2012, 01:09 PM
RE: tenths of a second timer - Barnabus - 11-17-2012, 03:20 AM
RE: tenths of a second timer - Mordaunt - 11-16-2012, 11:01 PM
RE: tenths of a second timer - ChaveS - 11-24-2012, 04:29 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)