Learn

BAR Fight in 60 seconds, and the small print.

What these numbers are, where they come from, and what they do not tell you. Read the short version first. The rest is here when you want it.

The short version

Five things to know

About a minute to read. Map examples use published data; illustrative examples are labelled.

1 minute read

Choose a map for live examples

Words explained

The glossary

Every "?" on the site opens one of these. Each word has its own link, so you can send it to someone.

How rankings work

What the score measures, and what it does not

All maps use the same completed-unit model. It compares what a player did in five-minute steps with reference players in the same situation.

See the rankings

The four things that make the score

Weights are design choices, not measured shares of victory.

Combat balance 45%

Normal metal value of finished enemy units destroyed, minus finished units lost to enemies.

Metal income 20%

Recorded income, including reclaim and game-rule income.

Energy income 10%

Recorded energy production, including energy that could not be stored.

Fighting units built 25%

Normal metal value of finished fighting units and defences; not exact spending.

Who gets a ranking, and how firm it is

  1. 1

    Eligible

    A latest recorded OS above 30, and at least 5 scored games across 3 UTC dates.

  2. 2

    Established or early

    Established needs at least 10 scored games across 5 dates, and at least 60% usable coverage among games long enough to score. Early uses the same calculation. Stars mark the first three places, not confidence in the evidence.

  3. 3

    What counts in a game

    Games under 8 minutes are context only. Scoring leaves out the last 3 minutes of each game and uses five-minute steps through minute 30.

  4. 4

    Compared with whom

    Reference players in the same map version, format, starting layout, game and engine version, settings and time interval. The player being scored is left out, and each reference account counts equally.

  5. 5

    Fewer dates, closer to 50

    The score moves toward 50 when fewer playing dates were recorded. The likely range shows how much it changes when those dates are resampled.

What the score is not

  • It is not official OpenSkill, a win chance or a share of team victory. Win rate adds no points.
  • Final-attacker credit misses assists. Income can be unhelpful. Completed units may never reach a useful fight.
  • The range does not measure every possible source of bias.

Data and limits

How the data works

BAR Fight turns public Beyond All Reason replays into player comparisons, map statistics and position rankings. These numbers describe recorded games. They do not tell the whole story of a player or a team.

Where the data comes from

Active comparisons and statistics use Gex, a community project that extracts measurements and unit events from public replays. Earlier Supreme Isthmus captures remain archived for verification. They are not used in active Gex-only comparisons. Each match is counted once. Position playback uses recorded 30-second Gex observations; construction progress and simulation-based team coaching remain unavailable.

The official replay archive is the source of public games. This is not a complete record of every BAR match. Imports can be delayed, captures can be incomplete, and private games are not included.

Games, players and missing data

A game is one match. A player game is one player's appearance in one match: an 8v8 match can contribute 16 player games. Account IDs keep a player's history together when their name changes.

Coverage is the percentage of selected player games with usable measurements. Missing values stay missing; they are not treated as zero. A game can support an economy chart while lacking the unit events needed for an opening chart. Each chart keeps its own denominator, so different coverage percentages can be correct.

Position rankings exclude completion-based measurements from captures known to predate completion recording. Their economy and other usable evidence remain available. Recovered factory releases can restore timings for produced units, but cannot establish complete building coverage or a complete fighting-force score.

Openings and build timings

Our featured map answers use players with a recorded replay rating of OS 40 or higher, including exactly 40. That is a reference group of experienced players, not proof every choice was good. Explore lets you change it.

The first fighting unit means the first completed mobile fighting unit in the recorded event data. Commanders, builders, buildings and static defences are excluded. Units completed at the same recorded time are shown together.

Compare's first-five-minute chart shows each faction's units separately and gives the number of usable games for each player. Older Gex captures can contain unit creations with every completion time set to zero. A successful import alone does not establish opening coverage: games without any recorded opening completion evidence are excluded from this chart, rather than counted as zero builds. Coverage is checked for the unit being compared; usable mobile-unit data does not establish building coverage. Within usable unit coverage, a player's absent unit still counts as zero. These samples can cover different dates and factions; the same starting position does not make their histories identical.

Statistics uses the same evidence rule for Opening measurements recorded in its all-map datasets. An imported game without usable finish timestamps is marked unavailable. Existing lifecycle, economy and combat measurements remain available. Missing finish times are recovered only when retained evidence supports them; existing completion times are preserved. Some older games have usable unit timings while building timings remain unavailable. Creation times and resource totals are not substitutes.

Build timing uses the first recorded completion of the chosen unit or group for each selected player game. The typical time is the median among player games where it was observed. The middle half runs from the 25th to the 75th percentile. The percentage reaching a build uses all selected player games with usable unit events, including games where it never appeared. Games do not have to last 20 minutes to contribute.

Grouped constructors or economy buildings combine explicitly selected units with a similar purpose across factions. Their costs and abilities are not assumed equal. Receiving a unit and building it are different questions; transfers do not prove payment.

Map positions and game versions

We combine opposite starting spots only when the map layout supports that pairing. Unclear starts remain outside a named position. A starting spot gives context, but a player can change responsibilities during a match.

Map versions stay separate. Featured timing summaries can include several game patches; their labels say which filters were used. In Explore you can narrow an answer to one game version. A common timing is a description, not a deadline: pressure, teammates and enemy choices can make a different build appropriate.

Which numbers use which lens

The same word can mean a different group of games on different pages. This is the lens each part of the site uses.

Public map summaries are refreshed offline and show their data dates. Rankings are a separate daily publication and can have a different date.
WhereWhich gamesCan you change it?
Position guides and HomePlayers with OS 40 or higher, Large teams with 16 players, finished builds, one map version.Open the same question in Explore.
ExploreThe scope shown above each answer. Most captured answers use OS 40 or higher in Large teams. Opening orders use all ratings and formats.Yes: position, rating, faction, format, game version, dates, player.
RankingsPlayers with a latest recorded OS above 30 and enough scored games, scored against reference players in the same situation.Map, format and position.
CompareThe map, dates, format and position you choose. Both players use the same filters.Yes.
In-game widget and Discord botThe widget covers Supreme Isthmus v2.1, human 8v8 games of at least five minutes, over the last 30 UTC days. The bot reads the same published data.The bot lets you pick a map and position.

Still not sure what a number means?

Ask. Data questions are one of the topics on the contact form.