The player browser and random slaughter could do with a cleanup.
A few people suggested a separate Inactive Slaughter
Also, I think it would be wise to cache the output arrays, instead of the entire page.
It means that there is still a performance improvement by storing an old copy of the player list, and reusing it, but since the full page is not being cached, it can be user specific.
And THAT means that you can have personalization, for instance, a symbol to show that can attack this player, or if they are your ally, etc.
A few people suggested a separate Inactive Slaughter
Also, I think it would be wise to cache the output arrays, instead of the entire page.
It means that there is still a performance improvement by storing an old copy of the player list, and reusing it, but since the full page is not being cached, it can be user specific.
And THAT means that you can have personalization, for instance, a symbol to show that can attack this player, or if they are your ally, etc.
Invisible War ][
Once again well done cyber, well done. 
As far as the random slaughter thing is concerned, if you include inactives it seems as though that would be easier to cheat... Not entirely positive, just an idea...
As far as the random slaughter thing is concerned, if you include inactives it seems as though that would be easier to cheat... Not entirely positive, just an idea...