[Logic_]

Quote:

Originally Posted by AmigaBlizzard I can get why you want to kick cheaters fast, but using OnPlayerUpdate is overkill. This callback is called at least 30 times per second FOR EVERY PLAYER. If you have 250 players online, you're executing OnPlayerUpdate 7500 times or more every second. It won't hurt your server when you just transfer all that code to a 1-second timer. Then that code runs 250 times per second, which is more than enough.

Using OnPlayerUpdate as a timer is not an overkill but, a very big mistake.
I've kept my anti cheat timer to call every 1.5~2 seconds.

So for say, my timer will call 2 times in 3 seconds instead of 3. It may not make a very big difference, so why put unnecessary load?

Quote:

Originally Posted by AmigaBlizzard Optimization starts with clearing OnPlayerUpdate. I never used that callback and I never will, because I can see no reason for any code that needs to run 30 times per second.

The only reason why anyone will use it is when they're making an Anti AFK system, since OnPlayerUpdate is not called when they are paused.

---

@OP: You can also use GetServerTickRate when you've lots of players in the daytime and let us know of the result.

PHP Code:

CMD:tickrate(playerid)
{
    new str[25];
    format(str, sizeof str, "Server tickrate: %d.", GetServerTickRate());
    SendClientMessage(playerid, COLOR_GREY, str);
    return 1;
}