Public Metrics Transparency
Public Data Transparency
This page explains how L2Votes currently defines a few public data points shown across listing, footer, and Discord-related surfaces. It documents the implementation as it exists in the codebase today, not a marketing summary.
The goal is to make platform-side counting and scoring easier to understand for players, server owners, and anyone reviewing public listing quality. When we change these rules later, this page should be updated to match.
How Active Servers are counted
The footer and other summary surfaces use the approved listing count only. In the current implementation, an Active Server is any listing with status = approved. This count is not reduced by chronicle, launch window, Discord data availability, or premium state.
How Recently Opened is defined
Recently Opened is a narrower filter than Active Servers. A listing must be approved, must currently have server_stage = live, must have a launch_at timestamp, and that launch timestamp must be within the last 60 days and not in the future.
How Discord-linked health signals are measured
The public Discord-facing score currently exposed in the codebase is a 0 to 100 health score. It combines online ratio, 7-day change behavior, invite click activity, data freshness, member-count credibility, and a small recent-activity bonus when enough public data exists.
How server profile health data is reused
On server profile and compare surfaces, the displayed health value is the Discord-linked health score when a linked Discord ranking entry exists. In other words, the server-side health display reuses Discord-derived health data rather than a separate independent server-only formula.
Current health score weight model
The current Discord health score implementation uses these weighted inputs before clamping the result to a 0 to 100 range:
Freshness tiers in the current formula
- Checked within 15 minutes: freshness score 100
- Checked within 60 minutes: freshness score 80
- Checked within 180 minutes: freshness score 60
- Checked within 720 minutes: freshness score 35
- Older than 720 minutes: freshness score 15
These freshness bands describe how recently the Discord data was checked or synced, not whether a server is good or bad.
What this page does and does not claim
This page documents current public counting and scoring behavior. It does not claim that every metric is a full quality judgment, fraud verdict, or promise of future performance.
A high health score does not guarantee legitimacy, uptime, or player satisfaction. An approved listing count does not mean every listed server is equally active. Recently Opened reflects a time window rule, not a review label.
If a listing looks incorrect, stale, or misleading, use the trust pages below to review methodology or report the issue for manual review.