Thoughts on daily refreshing in games

Many logics in the game need to be refreshed daily, whether it is, or. Here we take the physical strength as an example. The legend of the turret receives physical strength from to every day.

There are many ideas for implementing the daily refresh logic.

1. When a player goes online, it notifies the player to refresh the remaining time and whether the player has received the information. And then send it to the client.

2. Each time a Player opens the panel, a request is sent. When the time is reached, the server pushes over.

3. Each time a Player opens the panel, a request is sent. When the time is reached, the client re-opens the Panel message.

All three can be used, but for the purpose of saving traffic in mobile games, the legend of the turret is the third. It seems unreasonable at first glance. It is actually reasonable. For example, if one server has 1000 gamers and only about 500 gamers are online at the same time, up to 500 of these 200 gamers can be opened at this point. In this way, only 200 messages are pushed at the same time. In the second way, 500 messages are pushed at the same time. In this way, the server's load capacity is actually enhanced.

Thoughts on daily refreshing in games