HLstatsX and the leaderboard era of community servers

The stats page loads before the game does: 41st of 3,112, down two places since Sunday, and the daily awards list shows the USP Master going to somebody else again. Through the 2000s, pages like that, built by HLstats, HLstatsX or PsychoStats from a server's own logs, were why plenty of regulars picked one Counter-Strike server over the ten beside it. That ranking existed nowhere else.

Where the numbers came from

HLstats was Simon Garner's, written for Half-Life in 2001. Tobias Oetzel extended it into HLstatsX for the Source games between 2005 and 2007, and after he stopped, the code went through a fork called ELstatsNEO and came out as HLstatsX: Community Edition, which has carried on under the GPL since 2008. PsychoStats, Jason Morriss's package, did the same job on the same principle.

The principle was that the game server already wrote a line for every kill, connection, name change and chat message. Point logaddress_add at the stats machine and those lines arrived over UDP at a Perl daemon, listening on port 27500 by default in the Community Edition, which parsed them into MySQL for a PHP site to turn into tables. The ranking needed nothing from the game beyond its log, so one install could rank a long list of GoldSrc and Source games, and the Counter-Strike: Source servers still running today can feed it the same way.

Players were tracked by Steam ID, so a new name changed nothing. Everyone started on 1,000 skill points, and each kill moved points from the victim to the killer: five, multiplied by the victim's points divided by the killer's, multiplied again by a modifier for the weapon, and held between 2 and 25 by default. A team kill cost 25 points and a suicide cost 5. Anyone who wanted could type hlx_set icq into chat and put an ICQ number on their stats profile.

What the formula did to the people on it

Because the reward scaled with the victim's standing, killing someone above you paid well and killing someone below you paid almost nothing. The daemon's source carries a comment working through the worst case: a player on 5,000 points who kills a newcomer on 1,000 gains a single point, and if the newcomer kills him instead he loses 25. The fix, an optional cap on that ratio, ships switched off.

So the top of a busy ladder played carefully, and everyone could see who was guarding what. Type rank, top10, next or session in chat and the daemon answered inside the game. When you joined, it announced you to the whole server by position and points, along with the country your IP address resolved to.

The rest of the site was built for arguments. Kill totals earned military ranks, from Recruit at zero through Sergeant Major at 1,000 and Supreme Commander at 30,000, to a last rank called Terminator at 35,000. Daily awards went to the Knife Maniac and the Top Defuser, and the Counter-Strike: Source defaults even had one for Best Latency. Bots were ignored, and so were kills on a server with fewer than four real players. Anyone who went 28 days without an event vanished from the ranking until they came back.

Why it held people on one server

None of those points travelled. A regular on 2,000 points at one server was a newcomer on 1,000 at the next, and the 28-day rule meant that drifting away cost the place you had earned.

The ladder also measured you against people you actually played with, on that server's map rotation, under weights the admin had chosen. That made it local knowledge. Regulars knew who sat third and how they played; newcomers learned the names from the connect messages before they learned the spawns. The stats page tied the server to the clan's forum, and it was the part people opened on nights they did not play.

It had costs. Public numbers invite padding, and they invite accusations, because a jump of forty places overnight looks the same whether it came from a good week or from something else. A formula that punishes deaths also rewards caution over fun, which is not what most admins wanted their busiest hours to look like.

When the ladder moved off the server

Official matchmaking took the job over. CS:GO's competitive mode sorted players into skill groups, and Counter-Strike 2's Premier mode added a visible rating with global and regional leaderboards. Third-party ladders and trackers filled in whatever Valve left out. A rank that follows you everywhere belongs to no particular server. The community server stopped being the place where you were known and became a place to warm up, and the reason to return to one address went with it. There is a wider argument about what matchmaking cost Source communities, and the stats page was one of its first casualties.

The software has thinned out too. gameME, the hosted service from the company Tobias Oetzel went on to run, closed its stats hosting at the end of October 2024. HLstatsX: Community Edition survives in forks with PHP 8 and Docker support. Counter-Strike 2 streams its logs over HTTP, so one of those forks takes them through a small forwarder that hands each line to the old daemon.

Where a server-side ladder still earns its place

It works best where matchmaking has nothing to say. Surf servers and climb servers kept their map-time leaderboards because no official ranking covers them, and retake or zombie servers can still give regulars a number that means something only there.

Anyone adding one now can borrow what the HLstats years learned the hard way. Count only real players, so an empty server at 4am cannot be farmed. Do not punish deaths so hard that the leaders stop taking fights. Show people the name just above theirs, which is what next did, because the next place motivates more than the top ten ever does. Be deliberate about which numbers go public and which stay with the admins, and treat the ladder as one piece of progression that gives players a reason to come back, with other pieces around it.

And keep it local. Once the same ranking covers twenty servers, it starts to behave like matchmaking, and it stops holding anyone to any one of them.