Leaderboard

* First, be sure that the getstatus exploit is properly removed from the threats. * Take a look at the cpu and memory consumption with top command. If the problem is recent, i.e. there wasn't problems before with same player amounts and same settings, the issue may be external. E.g. the getstatus exploiting, the ET300 which I suspect you are using. 3 MB user.db is not a really big yet and should not cause problems. It is too early to make promises but the networking has been investigated again and it is possible that improvements will be made to the next version.