final case classTimeOfDayMessage(time: Long, unk: Long = 1092616192L) extends PlanetSideGamePacket with Product with Serializable
Sets Auraxis time for a continent (zone) on the client.
Use the slash-command /time to view the current time in the event window.
Auraxis time is represented as a standard military twenty-four hour clock, displayed in hours and minutes.
Time is set per zone on map loading.
Time affects, primarily, ambient light on surfaces.
It goes from full daylight, to twilights, to slightly darker nights, though the actual intensity will differ by zone.
Auraxis time is weird.
The data from the server is deconstructed into both a current time and a rate of progression.
The lower the value, the lower the rate; the greater the value, the greater the rate.
The rate is the product of the number of "cycles" between the current time and an origin time and a base interval.
The current time is constrained to a looping twenty-four hour interval.
If no time is set, the client starts counting from 10:00 at an initial rate of about one Auraxis minute every four or five real seconds.
Setting the current time to 1107296256 sets the current time to 00:00 with an indeterminate, but slow, rate.
Time is normally initialized somewhere within an interval between 1174405120 and 1207959296.
Setting the current time extremely high (near the numerical maximum) can cause psychedelic rendering.
(Setting the time to 4294967040 exactly will reduce the rendering system to gibberish.)
The interval from 1178164736 (~03:18) to 1203765248 (03:18) is about a full twenty-four hours.
That is a count of 25600512.
This member is added by an implicit conversion from TimeOfDayMessage to
any2stringadd[TimeOfDayMessage] performed by method any2stringadd in scala.Predef.
This member is added by an implicit conversion from TimeOfDayMessage to
StringFormat[TimeOfDayMessage] performed by method StringFormat in scala.Predef.
Sets Auraxis time for a continent (zone) on the client. Use the slash-command
/time
to view the current time in the event window. Auraxis time is represented as a standard military twenty-four hour clock, displayed in hours and minutes.Time is set per zone on map loading. Time affects, primarily, ambient light on surfaces. It goes from full daylight, to twilights, to slightly darker nights, though the actual intensity will differ by zone.
Auraxis time is weird. The data from the server is deconstructed into both a current time and a rate of progression. The lower the value, the lower the rate; the greater the value, the greater the rate. The rate is the product of the number of "cycles" between the current time and an origin time and a base interval. The current time is constrained to a looping twenty-four hour interval.
If no time is set, the client starts counting from 10:00 at an initial rate of about one Auraxis minute every four or five real seconds. Setting the current time to 1107296256 sets the current time to 00:00 with an indeterminate, but slow, rate. Time is normally initialized somewhere within an interval between 1174405120 and 1207959296. Setting the current time extremely high (near the numerical maximum) can cause psychedelic rendering. (Setting the time to 4294967040 exactly will reduce the rendering system to gibberish.)
The interval from 1178164736 (~03:18) to 1203765248 (03:18) is about a full twenty-four hours. That is a count of 25600512.
Auraxis time
consistently 1092616192; does nothing?