MXBMRP3 - Usage Survey

Data window: 2026-06-27 → 2026-10-03 (99 days, 82 observed)

_{Generated by tools/analytics_report.py from Aptabase exports - do not edit.}

Unique installs: plugin copies that have reported since 1.26, each counted once however often it is updated. Downloads: installer and zip from GitHub, updates included.

Games

Activity over time

Daily charts omit partial export days (2026-06-27, 2026-10-03); totals include them.

Curves pool all games (GP Bikes and Kart Racing Pro are 1% of launches).

• unique installs: 15,127 · avg new installs/day: 195 (over the last 30 full days)

• share of a day's active installs that are new: 6% (over the last 30 full days)

The first weeks are existing users upgrading, not new ones; averages use the last 30 full days.

• avg launches per active install: 3.8 · avg launches/day: 8,347

• Busiest hour: Mondays 18:00 UTC, 560 launches · quietest hour of the day: 07:00 UTC, 170 launches

• Median session: 16 min · mean: 36 min · 442,670 sessions
• About 269,000 hours in total; sessions left open pull the mean above the median.

Retention

• Half of new installs are still playing with the plugin a month later: 67% after a week, 50% after a month, of 7,690 installs old enough to measure.
• 79% come back after their first day; after the first week the curve is nearly flat.

A floor: an install that stops playing looks the same as one that removed the plugin. The report's first week (existing users arriving) is not counted.

Geography

Achievements

• Achievement tiers earned, median per install: 16% · installs holding at least one achievement: 95% (5,356 of 5,644)

• Achievements unlocked, median per install: 24

• Earned so far: 78 of the 82 listed achievements; the 32 hidden ones are under the fold below.

Feature & HUD adoption - MX Bikes

MX Bikes only (14,928 installs). (GP Bikes 150 and Kart Racing Pro 49 have too few for their own.)

• Median HUDs enabled per install: 5 · median widgets: 7

Too few reports to rank (under 25 installs): Twitch chat (connected) 0 of 2, YouTube chat (connected) 0 of 1.

Too few reports to rank (under 25 installs): Stream Chat 0 of 1, Twitch Chat 0 of 1.

Not charted: Pointer (always on); Spotter (follows the spotter, see Features).

Operating system

13,749 of 15,127 installs report an OS

Plugin version adoption

Each install counts once, at its most recent version; 8 of 15,127 run the prerelease channel.

Crashes (upstream / stability)

Analysed: 69,217 of 71,811 crash reports (1.27.5+ builds, full diagnostics). Excluded: 2,583 from earlier builds and 11 from dev tooling.

• Affected installs: 8,244 of 13,359 running 1.27.5+ (62%) sent at least one crash report

Recorded faults landed outside the plugin (in the game or another module), not necessarily the root cause. Known crashes are grouped by cause, the rest by module.

Crash rate by game

* Kart Racing Pro has 40 installs: a few machines can set this rate.

The Plugin (MXBMRP3) slice (54 crashes) is where the fault landed, not proof the plugin caused it.

Most common crashes

69% (47,442) of reports match the known-crash list.

✔ = a documented workaround.

Not yet catalogued

The other 31% (21,775), most frequent first. unknown+0x0 is an address in no loaded module (likely freed memory).

About this data

The plugin only sends anonymous, aggregate telemetry (no personal data - see the privacy note in the main README). Reporting began in 1.26 (a few stray older builds send only a basic launch event) and expanded through 1.27, so older versions report fewer fields. Percentages are always taken over the installs that actually report a given field, and each chart notes how many installs that is, so incomplete rollout is never shown as a real trend.

Definitions. Unique install - a unique install_id (regenerated if the analytics file is deleted, so a wipe-and-reinstall reads as a new install). Launch - one plugin start (app_started). Active install - an install that launched on a given day. Crash report - one fault caught by the crash handler, saved on crash and sent on the next launch (≈ one per crashed launch). Each install belongs to one game (the plugin installs separately per game); its game, country, and version are its most recently seen values.

Developer/test machines are excluded report-wide (3 installs, 1,472 events): they launch every dev build and deliberately trigger crashes to validate the telemetry, which would otherwise read as phantom plugin crashes.

Unidentified launches are excluded report-wide (5,266 of them, 26% of what the install total would otherwise be, from at least 97 machines): a plugin whose analytics file had become unreadable minted a throwaway id on every launch, so each launch arrived as a brand-new install that never returned. Their launches go with them (1% of launches). The plugin now repairs the file, so this shrinks as those installs update.

What each release line reports (share of its launches):