SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002401SphereServerexecutable - genericpublic21-09-14 23:1517-10-14 02:02
ReporterRizz 
Assigned To 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Nightly VersionAutomated (specify build number)
Experimental FlagsNone
Option FlagsNone
Internal Build Number2035
Summary0002401: Memories with different timerd equipped on player decay at the same time
Description[function f_testa_archery]
serv.newitem i_mem_prova_arch
new.timerd=12
equip <new.uid>

serv.newitem i_mem_prova_arch
new.timerd=6
equip <new.uid>

[ITEMDEF i_mem_prova_arch]
id=i_worldgem_lg
layer=layer_special
type=T_EQ_SCRIPT
name=Timer Memory
weight=0

on=@create
attr=attr_invis

on=@equip
link=<src.uid>




on=@timer
link.say asdas
return 1


Different timer, same decay time.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
21-09-14 23:15RizzNew Issue
22-09-14 12:52BenNote Added: 0002434
22-09-14 17:06XuNNote Added: 0002435
22-09-14 20:15RizzNote Added: 0002436
22-09-14 20:17RizzNote Added: 0002437
22-09-14 20:18RizzNote Deleted: 0002437
22-09-14 20:18RizzNote Edited: 0002436bug_revision_view_page.php?bugnote_id=0002436#r706
16-10-14 01:31RizzNote Added: 0002479
17-10-14 02:02RizzNote Added: 0002483

Notes
(0002434)
Ben   
22-09-14 12:52   
you do realize you have a difference of 0.6 seconds and the method you used is by far not the most precise way to test it...
(0002435)
XuN   
22-09-14 17:06   
Use this instead of what you have ... also a remove would be nice :)

on=@timer
link.say <serv.timer>
return 1
(0002436)
Rizz   
22-09-14 20:15   
(edited on: 22-09-14 20:18)
Ben, we are talking about 0.6 seconds not 0.06 seconds; you can easy notice the difference.

Anyway with <serv.time>:

[ITEMDEF i_mem_prova_arch]
id=i_worldgem_lg
layer=layer_special
type=T_EQ_SCRIPT
name=Timer Memory
weight=0

on=@create
attr=attr_invis

on=@equip
link=<src.uid>




on=@timer
link.sysmessage <serv.time>
return 0


The 173 number is related to the number of one packet.

http://i39.servimg.com/u/f39/12/69/62/20/cattur20.png [^]

There are almost no differences and when they are.. they are wrong.
(0002479)
Rizz   
16-10-14 01:31   
UP
(0002483)
Rizz   
17-10-14 02:02   
Still the same problem, memories on players decay with incorrect timer.