Su, when you PM-ed me server registration was name based. Now it isn't!
Here's how server identification/updates works now:
1) Servers are queried first by hashkey (which is similar to the player hashkey). If multiple servers are found under the same hashkey, the one that is the most current is used.
2) If no hashkey is present, the servers are queried by name. If multiple servers are found under the same name, the most recently created one matching that name is used.
3) Once the server is identified, all of the attributes of the server are compared to see if anything changed (name, port, ip address, etc). If anything has changed, the server record is updated during the request.
Since XonStat does not accept unverified servers in production, path #2 never happens in practice on stats.xonotic.org. It is only there for development purposes, when myself and others turn off server verification in order to test. The end result is that now when you change things on your server, it will update your information similar to how player updates are handled. This means that your server gets an updated name/port/ip when it changes instead of a new server record altogether.
<historical rant>
I know what you're thinking - why was it ever name-based to begin with? Well, it all started with server admins running several servers on the same machine. Back then we didn't plan on creating new keys for this scenario, so the result was several server entries using the same hashkey. This meant that the names were the only distinct thing I could use after the initial hashkey check, so that's what I did. Since that time we've fixed the issue w/ multiple servers on one machine, so the fix was ready to go. I decided this week it was finally time to cut over to the "new" way of doing things.
</historical rant>
asyyy^ | are you releated to chuck norris?