Why competitive rulesets fork and never merge back

Every competitive scene eventually has two rulesets, then three, and they never converge. The maps differ, the round limits differ, the overtime rules differ, and each league is certain its version is the correct one.

This is usually described as politics. It is more interesting than that: a ruleset is a claim about what the game is, and two leagues with different rulesets are not disagreeing about administration — they are disagreeing about the sport.

A ruleset is an argument in list form

Every line encodes a position. Round limits decide whether the game rewards consistency or momentum. Map pools decide which skills matter. Overtime rules decide whether a draw is acceptable, which is a statement about whether the point is to determine a winner or to measure play.

None of those has a right answer, and all of them have consequences that favour some players over others. A ruleset is therefore never neutral, and the people writing it know who benefits.

Why forks happen at predictable moments

After a patch that changes balance. One group adapts the ruleset, another declares the patch bad and pins to the old version. The fork is now technical as well as philosophical.

When a region grows enough to sustain itself. A scene that needed one league to have enough teams splits the moment two are viable. Geography does most of the work here, and the split is frequently amicable.

After a governance dispute. A ruling somebody considers unjust produces a competing league, and the new ruleset's differences are often incidental — the fork was about who decides, and the rules changed to mark the boundary.

That third one is the most common and the least discussed, because nobody announces it that way.

Why they never merge

Merging requires somebody to concede that their version of the game was the wrong one, and by the time two rulesets have existed for a few seasons there are players, results and reputations built on each.

A merged ruleset invalidates history. A team that won under one set of rules did not necessarily win under the other, and nobody wants to relitigate three years of results, so the rational move for everyone involved is to keep both.

This is why the forks are permanent even when the differences become trivial. The difference stopped being the point some time ago.

What this does to servers

Community servers are where the rulesets are actually executed, and a scene with three rulesets needs three configurations: three map pools, three plugin sets, three sets of conventions about what counts as a legal setup.

That fragmentation is a real cost borne by people who had no part in the dispute. A server owner hosting for multiple leagues maintains configurations for each, and a server that picks one has picked a side whether it meant to or not.

You can see the residue on the Counter-Strike listings, where map pools and configurations still cluster into groups that trace back to decisions made by leagues that no longer exist.

The part that is genuinely valuable

Forks are how rulesets improve. A single governing body has no pressure to change anything; competing ones are experiments running in parallel, and the good ideas propagate even when the leagues do not reconcile.

Most of what is now standard in competitive shooters started as one league's deviation. The fragmentation is the cost of that mechanism, and it is not obvious that a unified scene would have produced better rules: only fewer of them.

For anyone running a server

Pick a ruleset deliberately and say which one. A server advertising itself as competitive without stating whose rules it follows is asking every visitor to work it out from the configuration, and most will not bother.

Stating it is a two-line addition to a server description and it filters exactly the right people in: the same principle that makes a listing that says what it is outperform one that says it is the best.