SphereServer BugTracker - SphereServer
View Issue Details
0001447SphereServerexecutable - linux buildpublic12-07-08 15:0109-02-14 23:47
Monsi 
Beyonder 
normalmajoralways
resolvedfixed 
 
0.56c Nightly 
08-02-2008
None
Command_Sysmsgs, FileCommands, NoHouseMuteSpeech, Buffs, NoPrefix
0001447: Timer MaxValue
The value we can set in our timer is dropping randomly.
We had timers with 3 500 000 time... now our maximum is at 1 850 000. If we set a value greater than that sphere sets it automatically to -1.
This already destroyed our House-Script and will hit our larger spawns if it keeps dropping.
We've tried to restart the sphere and we also restarted the whole box it is running on. No effect so far.
No tags attached.
has duplicate 0001895closed  Time doesn't work properly when serv.time is close to overflow 
Issue History
12-07-08 15:01MonsiNew Issue
12-07-08 15:01MonsiNightly Version => 08-02-2008
12-07-08 15:01MonsiExperimental Flags => None
12-07-08 15:01MonsiOption Flags => Command_Sysmsgs, FileCommands, NoHouseMuteSpeech, Buffs, NoPrefix
12-07-08 15:05MonsiIssue Monitored: Monsi
12-07-08 21:02BeyonderNote Added: 0000004
12-07-08 21:02BeyonderStatusnew => confirmed
12-07-08 22:39MonsiNote Added: 0000005
19-07-08 13:55nazghulStatusconfirmed => assigned
19-07-08 13:55nazghulAssigned To => Beyonder
14-11-10 19:54MrSugarCubeCategoryexecutable - linux => executable - linux build
22-01-11 13:36MrSugarCubeRelationship addedhas duplicate 0001895
09-02-14 23:47BenNote Added: 0001944
09-02-14 23:47BenStatusassigned => resolved
09-02-14 23:47BenFixed in Version => 0.56c Nightly
09-02-14 23:47BenResolutionopen => fixed

Notes
(0000004)
Beyonder   
12-07-08 21:02   
Try backing up your saves, and manually changing the TIME to 0 in sphereworld.scp.
That is a temporary solution that will work if you don't have any serv.time dependant scripts.
(0000005)
Monsi   
12-07-08 22:39   
That's not that easy...
We've around 700 script-files, 100 got serv.time usage. We could reset the serv.load and change all of those 100... but that would still hit the char-age of our players. (we use many things that work with their char-age)

We'll try to change the TIME value in some kind of value as temporary solution...
(0001944)
Ben   
09-02-14 23:47   
Time is now INT64