Maintenance for the week of April 6:
• ESO Store and Account System for maintenance – April 8, 9:00AM EDT (13:00 UTC) - 6:00PM EDT (22:00 UTC)
We are currently investigating connection issues some players are having on the European megaservers. We will update as new information becomes available.

Abolish 22hour-cooldowns on dailies, reduce server load.

Ratzkifal
Ratzkifal
✭✭✭✭✭
✭✭✭✭✭
I don't like that certain dailies only reset after 22hours passed instead of resetting along with the pledges. If the game needs to keep track of all the cooldowns everyone has, isn't that also going to be a huge amount of data that needs to be stored? It would probably be easier on the server if that got changed.
What do you guys think? Am I overestimating the impact or is there an advantage to having them run on a 22hour cooldown that I overlooked?

Edit: It has been explained to me how the technical side of the system works and that the server load resulting from the current system is basically zero as long as everyone isn't checking all their timers at the same time. Apparently this change is not an effective way to reduce server load, which is sad.
Edited by Ratzkifal on August 20, 2019 9:54AM
This Bosmer was tortured to death. There is nothing left to be done.
  • RexyCat
    RexyCat
    ✭✭✭✭
    Ratzkifal wrote: »
    I don't like that certain dailies only reset after 22hours passed instead of resetting along with the pledges. If the game needs to keep track of all the cooldowns everyone has, isn't that also going to be a huge amount of data that needs to be stored? It would probably be easier on the server if that got changed.
    What do you guys think? Am I overestimating the impact or is there an advantage to having them run on a 22hour cooldown that I overlooked?

    First do we even know if everything that is running on a timer is on the same server or cluster of server as those other things that resets? Second having two timers for reset might actually prevent that everything is happening at the same time, meaning that you don't get a chain of messages sent to client that need to be handled locally (presented as centre on screen or in chat messages). So I don't think it would reduce performance, it could instead create more problems as during that phase a lot of communication need to be sent and updated. Mail for reward of the worthy need to be on each account, daily writs, daily rewards for log in, dungeons and a lot of other things will also need to be run between server and client.

    //RexyCat
  • Ratzkifal
    Ratzkifal
    ✭✭✭✭✭
    ✭✭✭✭✭
    RexyCat wrote: »
    Ratzkifal wrote: »
    I don't like that certain dailies only reset after 22hours passed instead of resetting along with the pledges. If the game needs to keep track of all the cooldowns everyone has, isn't that also going to be a huge amount of data that needs to be stored? It would probably be easier on the server if that got changed.
    What do you guys think? Am I overestimating the impact or is there an advantage to having them run on a 22hour cooldown that I overlooked?

    First do we even know if everything that is running on a timer is on the same server or cluster of server as those other things that resets? Second having two timers for reset might actually prevent that everything is happening at the same time, meaning that you don't get a chain of messages sent to client that need to be handled locally (presented as centre on screen or in chat messages). So I don't think it would reduce performance, it could instead create more problems as during that phase a lot of communication need to be sent and updated. Mail for reward of the worthy need to be on each account, daily writs, daily rewards for log in, dungeons and a lot of other things will also need to be run between server and client.

    //RexyCat

    Good point. It might all be handled locally on the client. I'm not a tech expert but that does sound like less of a strain for the server since it's not actually happening there. Then again, wouldn't that mean that changing the time on your PC would allow you to cheat the system? So there must be some externam clock running somewhere that your client needs to sync up with.
    I wouldn't be afraid of the change making it worse though, because I am sure the game doesn't record the pledges for every character/account either but only has a switch that changes which pledge you pick up and keeps track of if you completed it that day or not. Otherwise we would have problems every day when pledges reset. Dailies would then work on the same basis that you either did the daily of today already or you didn't and there is only one clock going on at all times.

    Also let's not forget that there are other benefits too. If you come home late friday evening and do mount training etc, then on saturday you'll have to wait until late afternoon to train your mount again instead of being able to do it when you first log in. It does sound more convenient to me if the technical side is not an issue.
    This Bosmer was tortured to death. There is nothing left to be done.
  • LuxLunae
    LuxLunae
    ✭✭✭✭✭
    Ratzkifal wrote: »
    I don't like that certain dailies only reset after 22hours passed instead of resetting along with the pledges. If the game needs to keep track of all the cooldowns everyone has, isn't that also going to be a huge amount of data that needs to be stored? It would probably be easier on the server if that got changed.
    What do you guys think? Am I overestimating the impact or is there an advantage to having them run on a 22hour cooldown that I overlooked?

    Dude.. they just set the time cooldown

    save (time +22 hrs. )

    Then when you walk to check the timer... it only calls it when you look at it

    display (time +22- current time )

    no different than the game saving if you did a quest or not...

    depending on how they do it ..it probably cost a few bytes...
    and since everybody isn't going to all keep looking at their cool down timers all at once, over and over again... it shouldn't really be to costly on server performance...

    I am just guessing though.. I don't know how any of this stuff works...
  • Ratzkifal
    Ratzkifal
    ✭✭✭✭✭
    ✭✭✭✭✭
    LuxLunae wrote: »
    Ratzkifal wrote: »
    I don't like that certain dailies only reset after 22hours passed instead of resetting along with the pledges. If the game needs to keep track of all the cooldowns everyone has, isn't that also going to be a huge amount of data that needs to be stored? It would probably be easier on the server if that got changed.
    What do you guys think? Am I overestimating the impact or is there an advantage to having them run on a 22hour cooldown that I overlooked?

    Dude.. they just set the time cooldown

    save (time +22 hrs. )

    Then when you walk to check the timer... it only calls it when you look at it

    display (time +22- current time )

    no different than the game saving if you did a quest or not...

    depending on how they do it ..it probably cost a few bytes...
    and since everybody isn't going to all keep looking at their cool down timers all at once, over and over again... it shouldn't really be to costly on server performance...

    I am just guessing though.. I don't know how any of this stuff works...

    Okay. I'm taking your word for it, because I am not all that tech savvy.
    Still, the consistency of having it all reset at more or less the same time instead of timers for pledges, writs, mount training, dailies, event tickets, rewards of the worthy geodes, etc sounds to me like a good deal. Just sad that we can't improve server performance that way.
    This Bosmer was tortured to death. There is nothing left to be done.
  • Berserkerkitten
    Berserkerkitten
    ✭✭✭✭
    I reckon one way to fix this mess would be to use some of that sweet crown store money they're making every minute to purchase a bigger hamster. But that's the problem with these guys - they exist to make money, not to spend it.
    Nobody cares about your endless list of terribly-named characters.
Sign In or Register to comment.