Server XML feed updated

[wrtlprnft]

I updated my server XML feed. It shouldn't break anything if you use a real XML parser (and chances are it won't if you use some custom-built WTF code), but maybe you want to know about the new stuff:

• Fixed server versions getting cut off after 30 chars
• Fixed issue where all (or a lot of) servers would be displayed twice
• IPs (that can be hostnames if you use SERVER_DNS, which would be nice for --custom-connect people) aren't cut off now, either
• Port numbers aren't limited to [4534;4540] anymore. I didn't know ports outside of that range were possible when i wrote the script
• Added version_min and version_max attributes. version_min is the network version you need to connect to a server, version_max should be the version of the server itself. Here's a list of the current versions:

  Code: Select all

  // mapping network version to program version
  static char const * sn_versionString[] =
      {
          "0.2.0",   // 0
          "0.2.0",   // 1
          "0.2.5.0", // 2
          "0.2.6.0", // 3
          "0.2.7.1", // 4
          "0.2.8_beta1", // 5
          "0.2.8_beta1", // 6
          "0.2.8_beta2", // 7
          "0.2.8_beta3", // 8
          "0.2.8_beta4",   // 9
          "0.2.8.0_rc1",     // 10
          "0.2.8.0",       // 11
          "0.2.8_alpha20060414", // 12
          "0.2.8.2", // 13
          "0.2.8.3_alpha", // 14
          "0.2.8.3", // 15
          "0.2.8.4_alpha", // 16
          "0.2.8.4", // 17
          "0.2.8.5_alpha", // 18
          "0.2.8.5", // 19
          "0.3.1", // 20
          0
      };

Have fun

[Z-Man]

version_max should be the version of the server itself.

Only if it is empty; otherwise, it is the protocol version of the least advanced connected client, and therefore the protocol version the server tries to use right now (plus additional things the old client can and will safely ignore). This is for the future case that a client may not be able to support all previous protocol versions; even if the server may in principle be compatible with client versions 0.X to 2.2, having both 0.X and 2.2 on simultaneously may be impossible, because, say, 0.X only supports 2D game physics and 2.X only 3D game physics (and 1.X supports both, but we found that too cumbersome to maintain).

[wrtlprnft]

Good to know I mostly added it because it came for free.