31.10.2018, 00:10
The best way is to just save the results immediately when you change the value of any stats (money, weapons, etc) via a threaded query that doesn't cache any results of the query, so the script doesn't have to 'wait' to finish the query function or even 'watch' it through a callback.
If you are doing it the right it way, using threaded queries without caching the results, it doesn't matter that you sync 100 players every 10mins with just one loop.
It doesn't matter if you loop through them when you use threaded queries without caching the results, as i also stated above.
Quote:
|
Originally Posted by Dignity
 Using a timer is inefficient. Imagine a timer running every 10 minutes on a 100 pb server.
Save when you change something in the script. |
Quote:
|
Originally Posted by Garr
it would be better to have per player timers instead of looping through everyone connected. timers are not resource hogging features lol they work well and you can have a lot of them. heck, thousands of timers doesn't have much of a performance hit.
|