Clientsided Time Calculation

[Twinny]

Originally Posted by coreys

He's Twinny. He get what he wants.
Or else.

Doubt it. Seems common perception that I'm a Graal terrorist. I probably can't request anything now .

[coreys]

Well that's just stupid.

[Skyld]

On Windows, timevar2 is the number of seconds since the client was opened.
On Linux/Mac, it is the number of seconds since 1st January 1970 (see UNIX time).

On the serverside, timevar2 is representing the time in France I guess, while on the clientside on Linux/Mac, it is representing the local timezone.

If it is important that your time is the same for every user, then run your calculations serverside, since Linux/Mac users will get time relevant to their timezone, and Windows users will get something altogether completely different.

[DustyPorViva]

This will let you have the accuracy of timevar2, while keeping your time the same as everyone elses(though I haven't tested it with others to compare the time).

PHP Code:

function onActionserverside() {
  if (params[0]=="getdiff") {
    temp.timedifference=timevar2-params[1];
    triggerclient("gui",name,"senddiff",temp.timedifference);
  }
}


//#CLIENTSIDE

function onCreated() {
  triggerserver("gui",name,"getdiff",timevar2);
}

function onActionclientside() {
  if (params[0]=="senddiff") {
    this.timedifference=params[1];
    onTimeout();
  }
}

function onTimeout() {
  temp.time=timevar2+this.timedifference;

  setTimer(0.05);
} 


[xXziroXx]

Geez, just have a serversided DB calculate the time every second and set it as serverr variable(s) then have the clientsided system read those

[DustyPorViva]

serverside variables are the bane!!!!

[Skyld]

Originally Posted by DustyPorViva

serverside variables are the bane!!!!

What?

[DustyPorViva]

Nothing, I just try to avoid server.variables as I've always been told they can 'cause a bit of lag or some such when they pile up.
Either way I don't see the need of constantly transferring serverside timevar2 when you can just sync it with the clientside timevar2

[Skyld]

Originally Posted by DustyPorViva

Nothing, I just try to avoid server.variables as I've always been told they can 'cause a bit of lag or some such when they pile up.
Either way I don't see the need of constantly transferring serverside timevar2 when you can just sync it with the clientside timevar2

There is no problem using serverr. variables when scripts on the clientside are actually making use of them. However, you should think about what information really needs to be sent over to the clientside for regular use, and not use serverr. variables for things that you can put into database NPCs, for example.

[HolySheepy]

im avoiding servside timeouts because i was told they lag xP

[coreys]

Originally Posted by HolySheepy

im avoiding servside timeouts because i was told they lag xP

...Only when you're doing a very large amount of work every .05 seconds...

And Dusty, why bother doing that if you can just do everything serverside in a DB NPC or a weapon.

PHP Code:

function onCreated() {
  getTime();
  timeFlags();
  onTimeOut();
}
function onTimeOut() {
  getTime();
  timeFlags();
  setTimer(1);
}
function getTime() {
  this.t_var = int(timevar2); 
  this.t_second = int(this.t_var%60); 
  this.t_minute = int((this.t_var/60)%60); 
  this.t_hour = int(((this.t_var/60)/60)%24); 
}
function timeFlags() {{
  serverr.time.second = this.t_second;
  serverr.time.minute = this.t_minute;
  serverr.time.hour = this.t_hour;
  serverr.time.stamp = getTimeStamp();
}
public function getTimeStamp() {
  if (serverr.time.second == NULL) 
    temp.second = "0";
  else 
    temp.second = serverr.time.second;
  if (serverr.time.minute == NULL) 
    temp.minute = "0";
  else 
    temp.minute = serverr.time.minute;
    
  if (serverr.time.hour == NULL) {
    temp.hour = 12;
    temp.hour = temp.hour @ ":" @ temp.minute @ ":" @ temp.second @ "AM";
  }
  
  else if (serverr.time.hour > 12) {
    temp.hour = serverr.time.hour-12;
    temp.hour = temp.hour @ ":" @ temp.minute @ ":" @ temp.second @ "PM";
  }
  
  else temp.hour = serverr.time.hour @ ":" @ temp.minute @ ":" @ temp.second @ "AM";
  temp.timestamp = serverr.time.month SPC serverr.time.day @ ", " @ serverr.time.year SPC temp.hour SPC "CST";
  
  return temp.timestamp;
} 


Ziro originally showed me how to do those time calculations, but I lost 'em a while back and I had to figure it out on my own.

Anyways...

[DustyPorViva]

Because then there's no need to transfer data between the client and server. The way I did it, the only time information is sent is once, from then on it uses comparison to retrieve the same time as everyone else, all on the clientside.
It's just more convenient to have something like the time on the clientside for fast and smooth access, since most things related to time(seteffect, lights) are on the clientside.

[Inverness]

Serverside timeouts are 0.1 seconds minimum.

[killerogue]

Originally Posted by Inverness

Serverside timeouts are 0.1 seconds minimum.

Everyone's been telling me 0.5. -/-

[xXziroXx]

Originally Posted by DustyPorViva

Because then there's no need to transfer data between the client and server. The way I did it, the only time information is sent is once, from then on it uses comparison to retrieve the same time as everyone else, all on the clientside.
It's just more convenient to have something like the time on the clientside for fast and smooth access, since most things related to time(seteffect, lights) are on the clientside.

Serverr. strings never actually gets transfered between the client and the server, they are just serversided variables that can be read on the clientside.

Originally Posted by Inverness

Serverside timeouts are 0.1 seconds minimum.

Correct.

Originally Posted by killerogue

Everyone's been telling me 0.5. -/-

Wrong.