Post: #17

so ur saying that running a function that fires on all connected players every few minutes would be better than a function that only fires per player every hour?

i will have to disagree on this one, for multiple reasons

1) a function that fires on a per player basis every hour, will obviously only fire every hour that they are online, rarely do multiple players login at the same time, therefore the functions wont be firing at the same time, giving each their own wiggle room as far as resource are concerned

2) since the functions fire on a per player basis, you wont have the immense resource consumption of the allclients firing, if there were say 100 players on, then when all clients is fired its going to take up a good bit of resources, tie that in with firing every X minutes, and ur looking at a resource hog every X minutes rather than just a function firing every so often per players login

3) he was only interested in every hour, so it seems counter productive to have it adding every few minutes when the minutes are of no concern to the outcome of the results, so again u would be trading resource consumption for irrelevant accuracy

i would also like to point out using TAG0 on the left side of a statement is unnecessary as you are defining the tag on the left side, and tag0 is only for statements that may have the opportunity to resolve to nothing rather than 0

firing a timerf function every hour on the player is as accurate as any other way of timing an hour, logging the current server time and counting back from it really wont be anymore accurate than the timerf, not to mention more calls to the server to get the time and adding it to a ctag that gets evaluated later, thus adding to more resource consumption

just my view, i could be wrong, but i am willing to bet that my reasoning endures