i still don't like how you written it but i kinda want the packet structure
but what they said is completely right , at nextco a 50 check on a thread took 300 more mb rams and the cp usages was 99% , source was crashing and ping was 1500
you won't feel how this may be important unless you host the server
i got no problem with the variables definitions but one , which is the following
you are simply not saving that values anywhere , you should save it at db so it does not show this to everyone everytime they enter ex. market
instead of using a main threat you could use other methods for example jumping/tele methods , kill/die methods , addingexp methods
make it a decent system , a table for each flag with entinity ids and handle events on the perfect method to cost you less cpu cycles , and by using tables do a simple however efficient method maybe at kernel to calculate how many points he got and how many points he still need