HLL Frontline

Servers Tracked

7DR

Live Battles

Frontline Board

Campaigns

All-Time Objective

0 / 25,000,000

0% 25,000,000 remaining

Site Brief

What This Tracks

Purpose

HLL Frontline turns live CRCON server data into a battle theatre. Each tracked server feeds the same campaign layer, so fronts keep their control history instead of resetting every match.

The dashboard shows which maps are heating up and the intel panel breaks down the current totals behind each front.

Active Front Rule

A map is only marked active when a tracked server is currently running that map and at least one player is actually on the server.

If a server is empty, its current map still exists in campaign history, but it does not light up as a live battle.

Liberation Equation

Each poll now blends kill pressure, player-count scaling, and objective hold pressure into the same control bar.

player_factor = min((AxisPlayers + AlliedPlayers) / 100, 1)^1.0 kill_delta = ((AlliesKills - AxisKills) / TotalKills) * 28 * min(TotalKills / 120, 1)^2.0 * player_factor objective_delta = ((AlliedObjectives - AxisObjectives) / TotalObjectives) * 8.0 * (elapsed_seconds / 3600) * player_factor next_control = clamp(decayed_control + kill_delta + objective_delta, -100, 100)

Kills still matter, but holding more sectors now creates a steady pull as long as players are actually present. The player factor dampens low-pop states so quiet or empty servers do not drag fronts unrealistically.

Cooldown And Recovery

Inactive fronts cool back toward neutral over time. The base decay is now 0.10 control per inactive hour, and fronts above the 90% dominance band decay faster the closer they are to full occupation.

That extra late-stage cooldown is what helps an aggressive front fall away faster when the fighting stops instead of hovering near 100% for too long.

Factors That Matter

Kill balance: whichever side wins the kill share still pushes the line in its direction.

Objective hold: controlling more sectors creates a passive buff even without a fresh capture event feed.

Player count scaling: fronts with more live players apply stronger pressure than quiet ones.

Persistence: totals and control survive across matches, servers, and restarts through PostgreSQL storage.

Live state: the active marker depends on real current-map state and non-zero player counts, not just a stale rotation entry.