Real time tracking of public servers which also shows number of players online, ping time, and a brief summary.
There is currently only one Metaserver as the original has been retired. The new Metaserver is referred to as Metaserver2.
There used to be two running versions of the Metaserver and were referred to as Metaserver1 and Metaserver2. Clients that are being developed under Trunk (2.x) displayed servers listed in both Metaserver1 and Metaserver2. Clients that are under development in branches/1.x (i.e., the release such as 1.11.0 which is also used by my prepackaged Linux distributions) only displays servers listed in Metaserver1.
How to make your server show up on the metaserver:
After you install or configure your server, there is a fill located in etc/ called metaserver2.
The actual location of the metaserver2 file will depend on how the server was originally installed (i.e., by source or by precompiled package, dedicated user account for running the server) so be sure to check the following possible locations:
You will need to make the following changes:
- Line 20, change off to on
- Line 37, change put.your.hostname.here to a valid server or hostname if DNS is set up correctly for that; If not, then use your server IP Address
- Lines 56 and 57, update the comments and keep in mind the suggestions and requirements mentioned in the file
- Lines 63, 64 and 65; This is used to specify or summarize the release status of the archetypes, maps and server code base. Standard is reserved for what is found in SourceForge SVN, anything besides this should be mentioned. For instance, a server with maps that are available for testing might specify Standard + Testing or Standard + Custom
- Line 80 should be updated, if any of them apply, using the defined flags listed in this file
NOTE: It can take anywhere from 5 to 15 minutes for a new server to show up in the Metaserver listing.
Crossfire needs TCP port 13327 open
Metaserver needs TCP port 13326 open