Launcher statistics

Open Journal -> Launcher statistics. Five sections help you assess launcher use, update results and common failures. Viewing requires the launcher statistics permission.

Period and filters

Field	Purpose
Project	All available projects or one project.
Game server	All servers or one server of the selected project. Available in Games and Errors.
Period	A preset range, calendar year or custom dates. The default is the last 30 days.
From / Through	First and last included days. Dates and times are in UTC.
Chart interval	Automatic, daily, weekly, monthly or yearly. Changes the chart intervals, not the selected period.

Apply changes using the filter button. Dates and the selected project remain in the page address and follow navigation between sections. Moving to Overview, Updates or Hardware clears the server filter: those observations describe the launcher as a whole. Reset restores the initial values.

For long periods, choose months, years or an automatic interval. If the chosen interval is too detailed, increase it or shorten the period.

Overview

Cards show recorded events, installations, launcher sessions, launcher and game launches, completed updates and failures. Charts show their changes over time. Tables below list window actions and launcher versions.

An installation is not a separate player or account. One person may use several installations. A session is a separate period of launcher use. Installation counts from different intervals cannot be added: the same installation may appear on multiple days.

Actions distinguish opening, closing, minimizing, restoring the window, hiding to the tray and restoring from the tray. The versions table uses each installation's latest version within the period and shows up to 20 most common versions.

Cards, charts, window actions and versions share one selected period.

Games

Compare game starts, exits, installations and average game duration. The table lists the project, game server and number of duration measurements. The average includes only exits with a recorded duration; a missing measurement is not a zero-length session.

Starts and exits over time, followed by individual game server results.

Select a project and game server to review one server. In Errors, this filter retains only game-launch failures associated with the selected server.

Project and server filters apply to the cards, chart and table.

Updates

Review started and completed updates, installations, average duration and downloaded volume. Regular and critical updates are shown separately. An update may complete outside the selected period, so a difference between the counters does not itself indicate failure.

Duration and downloaded volume include measurement counts. Not measured means the information is absent. A recorded zero remains zero, such as an update without downloaded files. Downloaded volume sums only completed updates with a recorded measurement.

Update counts, duration and downloaded volume include available measurement counts.

Hardware

Review operating systems, architectures, CPUs, GPUs, drivers, memory and screen resolutions. Each installation contributes its latest configuration within the selected period. Repeated observations from the same launcher do not increase the installation count.

Not every configuration has every measurement. Coverage cards show how much information is available; an absent value is not treated as zero memory or a separate device model. CPU, GPU and driver tables display up to 20 most common values.

Hardware characteristics and measurement coverage for the selected period.

Errors

Cards and a chart show failures and affected installations. The table includes failure type, diagnostic code, component, occurrences and installations, the first and last occurrence in the period, and the version, operating system and architecture of the latest occurrence.

Launcher, game-launch and update failures are distinguished. Compare affected installations first, then use the code and version to investigate a release. The table shows up to 50 most frequent failure groups. It summarizes diagnostic categories, not full error messages.

Failures are grouped by type, code and component, with occurrence times in UTC.

Empty reports and recovery

If there are no observations in the period, counters show zero and averages without measurements are labelled separately. Check dates and project selection or reset filters. A launcher that does not yet submit observations leaves the report empty.

No observations, missing measurements and a failed request are different states.

A warning appears when the report cannot load. Apply the filter again or reload the page; an unavailable report does not mean zero activity.