Places that more than one player has joined this server from, the most players first. Several accounts behind one address are often alts (or a household); a player with several addresses is not a concern on its own. An IPv6 address is shown as its /64 prefix, which is what identifies a household.

Every account, whatever server it plays on. A developer account can see and join the servers that are developer access only (set on Manage servers) - tick Developer to make an account one, and untick it to take that back. Accounts are the people, players are what they play as: the Players column lists the players an account has on the servers that are running.

Sign-ups by source

Which advert or site each account came from: its link's ?ref= or ?utm_source= tag (with utm_medium and utm_campaign after it), or else the site that linked to us. Direct / unknown is everyone else, and every account made before this was recorded. Counts the accounts the search above leaves in, so search for a source to see just that.

Puts a crowd of players on a sandbox server to see how it copes. Each account is loadtestN@test.com (N counting from 1, password "loadtest") with pro mode, and its player is called loadtestN. A set up gives every player nine level 10 cities with heroes, fortifications, troops and resources (the Insta War Account item), has each city heal automatically, keep its gate open and work to the pro mode goals - with the first city also the war city - and leaves the bots paused. Only when the load test is switched on do the bots start. A server that restarts always comes back with it off and every load test bot paused.

Set up

Makes the accounts that are missing and a set up player for every one of them. Accounts and players that are already there are kept - one that is already set up is left alone. This can't be done while the load test is on.

Load test