this page describes the methods of discovering monopd servers.
as far as I can see by looking at atlantik and gtkatlantic there are two different ways of discovering servers, monopigator (used by atlantik) and meta-atlantic (used by gtkatlantic). they both however use XML to describe the servers (its slightly different but we should be able to parse both at the same time), the only big difference is that monopigator uses http where meta-atlantic uses a custom atlantic-like Command->Response Protocol.
== monopigator ==
there is only one monopigator server that I know of (which is hardcoded in the atlantik source) which is http://monopd-gator.kde.org/, to get the server list you just have to request the page and parse the resuling XML.
{{{
}}}
== meta-atlantic ==
as I said earlier these use a custom protocol, a server you can screw around with is at meta.gradator.net port 1240
(like monopd it sends one xml document per line)
Note: the commands seem to be Case-Sensitive
Commands (basically nicked from the create_connection_metaserver function in game.c in gtkatlantic):
* CHECKCLIENT: seems to be a check function for newer gtkatlantic versions? (we probably won't need it)
* SERVERLIST: Returns an XML-Formatted Serverlist
* GAMELIST: Returns an XML-Formatted Game List
'''CHECKCLIENT''':
* Seems to Take 2 Arguments, Package Name and Package Version
'''SERVERLIST''':
* Returns something like the following: {{{
}}}
'''GAMELIST''':
* Returns something like: {{{
}}}