client choices

[cavesomething]

A thought that occured to me whilst discussing a related point on IRC, is that there is no real way of knowing which clients are actually being used with the game today.

gcfclient2 hit CVS last summer, who is using it now?

Has anyone switched to gros' new jxclient following it's release last week?

http://crossfire.real-time.com/screenshots/index.html has screenshots of most of these, but they are rather outdated in places.

[Leaf]

For the year of 2006, here's what the Metalforge server log files show:

Note: at the moment, there is now way to track unique connections. So, if someone logs in 15 times in one day, the server logs will show 15 connections from whatever client & version they are using.

1 CS: connection from client of type < >
1 CS: connection from client of type < CF SDL Client 0.1>
1 CS: connection from client of type < GTK Unix Client 1.5.0>
1 CS: connection from client of type < X11 Unix Client 1.5.0>
2 CS: connection from client of type < X11 Unix Client 1.7.0>
3 CS: connection from client of type < GTK Win32 Client 1.7.1>
3 CS: connection from client of type < X11 Unix Client >
4 CS: connection from client of type < GTK2 Unix Client 1.8.0>
4 CS: connection from client of type < Perl Bot>
7 CS: connection from client of type < X11 Unix Client 1.7.1>
8 CS: connection from client of type < GTK Win32 Client 1.7.0>
9 CS: connection from client of type < GTK Win32 Client 1.8.0>
22 CS: connection from client of type < GTK Unix Client 1.7.1>
28 CS: connection from client of type < GTK Unix Client 1.7.0>
30 CS: connection from client of type < JCrossclient 1.0alpha3>
41 CS: connection from client of type < X11 Unix Client 1.8.0>
42 CS: connection from client of type < JXClient Java Client Pegasus 0.1>
82 CS: connection from client of type < GTK Unix Client >
125 CS: connection from client of type < GTK Unix Client 1.8.0>
172 CS: connection from client of type < GTK Win32 Client 1.8.0 snapshot>


A larger collection from 2005-Jul-29 until 2006-Jan-06

1 CS: connection from client of type < CF SDL Client 0.1>
1 CS: connection from client of type < GTK Unix Client 1.4.0>
1 CS: connection from client of type < SDL Client 3.00 Alpha (Terminus)>
1 CS: connection from client of type < X11 Unix Client 1.2.0>
1 CS: connection from client of type < X11 Unix Client 1.6.0>
1 CS: connection from client of type < X11 Unix Client 1.6.1>
2 CS: connection from client of type < GTK Unix Client 1.2.0>
2 CS: connection from client of type < GTK Unix Client Post-1.6.0-CVS>
2 CS: connection from client of type < GTK Win32 Client 1.5.0>
2 CS: connection from client of type < SDL Client 0.03 Alpha (Kiev)>
2 CS: connection from client of type < X11 C Client>
3 CS: connection from client of type < GTK Win32 Client 1.6.0>
3 CS: connection from client of type < SDL Client 0.02 Alpha>
3 CS: connection from client of type < X11 Unix Client 1.3.0>
5 CS: connection from client of type < CFJavaClient>
7 CS: connection from client of type < GTK Unix Client 1.6.0>
12 CS: connection from client of type < PyClient 0.1>
14 CS: connection from client of type < cfpython>
17 CS: connection from client of type < GTK2 Unix Client 1.7.1>
18 CS: connection from client of type < GTK Win32 Client 1.6.1>
25 CS: connection from client of type < GTK Win32 Client 1.7.1 snapshot 2005-05-21>
27 CS: connection from client of type < DX_CLIENT 125>
48 CS: connection from client of type < X11 Unix Client 1.5.0>
49 CS: connection from client of type < pyclient>
62 CS: connection from client of type < Perl Bot>
70 CS: connection from client of type < JCrossclient 1.0alpha3>
108 CS: connection from client of type < X11 Unix Client 1.7.0>
131 CS: connection from client of type < GTK Win32 Client 1.7.0>
147 CS: connection from client of type < GTK2 Unix Client 1.8.0>
181 CS: connection from client of type < GTK Unix Client 1.5.0>
196 CS: connection from client of type < >
287 CS: connection from client of type < Crossfire Bot>
306 CS: connection from client of type < X11 Unix Client 1.7.1>
319 CS: connection from client of type < JXClient Java Client Pegasus 0.1>
331 CS: connection from client of type < X11 Unix Client >
523 CS: connection from client of type < X11 Unix Client 1.8.0>
1039 CS: connection from client of type < GTK Unix Client 1.7.0>
1296 CS: connection from client of type < GTK Win32 Client 1.8.0>
1321 CS: connection from client of type < GTK Unix Client 1.7.1>
1363 CS: connection from client of type < GTK Unix Client >
2055 CS: connection from client of type < GTK Unix Client 1.8.0>
2477 CS: connection from client of type < GTK Win32 Client 1.8.0 snapshot>
2726 CS: connection from client of type < GTK Win32 Client 1.7.1>

[Ryo]

thanks for the stats, Leaf

[cavesomething]

it would be interesting to map these to playing times and number of unique ip adresses as well,

Is cf client only used by those who connect to a server, get annoyed by its bugs, and then give up, or is it a hard-core of reactionaries that still use it?

[Leaf]

it would be interesting to map these to playing times and number of unique ip adresses as well,

True.

However, as things stand now in the server logging - there are no time stamps with client connections or player logins.

Also, as things stand now - there is no easy way to correlate player logins with what client they are using (for good or bad).

[cavesomething]

The problem isn't that the data isn't available - it is, and it would be relatively simple to map the version string sent to the ip adress of the socket, it is just that there is so much similar data that could be logged in that way, that it wouldn't be possible to sanely store or use it all.