WOODHOUSEThe Loftwah Software Factory

Find a project or subject.

157 pages in the index

Esc closes search ⌘ K or Ctrl K opens it

MoreMenu
Measurement & privacyGames × RadioExplore connected productsEdition discoveryExplore the projects

Fighter analytics

Play & engagement

Custom dates
UTC · max 90 days
24 Sept 2026 – 23 Oct 2026 · 30 days · Today is partial1/1 reporting projects for this measure · 7/7 sources reporting · Saved snapshot

This report is frozen at 2026-10-23 04:50 UTC. Refresh these dates · Latest 30 days

Visits · Fighter

Count per UTC day · gaps mean unavailable

Anonymous tab sessions admitted by the collector. Opening another tab or returning after the session boundary may count again; a visit is not a unique person.

Game starts
161
Legacy/test risk
Game completions
107
Legacy/test risk
Active play time
2m 5s
Legacy/test risk
Visits
3
Legacy/test risk
1009-2410-0810-23

Inspect a date to see source values. The data table below works without interactive charts.

Chart data & export

These are daily values for visits. A dash means unavailable. Daily distinct-browser counts must not be added to estimate period-level people.

Visits· UTC dates ·count
DateFighter
2026-09-24—missing
2026-09-25—missing
2026-09-26—missing
2026-09-27—missing
2026-09-28—missing
2026-09-29—missing
2026-09-30—missing
2026-10-01—missing
2026-10-02—missing
2026-10-03—missing
2026-10-04—missing
2026-10-05—missing
2026-10-06—missing
2026-10-07—missing
2026-10-08—missing
2026-10-09—missing
2026-10-10—missing
2026-10-11—missing
2026-10-12—missing
2026-10-13—missing
2026-10-14—missing
2026-10-150legacy
2026-10-160clean
2026-10-171clean
2026-10-180clean
2026-10-190clean
2026-10-201clean
2026-10-211clean
2026-10-220clean
2026-10-230partial

Can we compare these dates?

Coverage for the selected measure. Colour describes evidence, not popularity.

Comparable full dayPartial dayLegacy / test riskBounded / sampledNot measured
24 Sept 202623 Oct 2026
Fighter

The longest available comparable history in this selection is 7 complete daily observations. First collection days and today remain partial. Legacy activity may include tests that cannot be separated.

Have browsers come back?

These are optional browser signals, kept separate for each project. They cannot identify people or establish cohort retention. Daily browser counts do not add up to a period total.

  • Fighter0 returning · 0 reporting browsers

    Distinct opted-in browser IDs observed in this window with an earlier different tab session in retained 90-day history (including same-day returns). Daily distincts are not additive; period totals are unavailable when the raw retention window is incomplete. Clearing/rotating IDs resets continuity; default tab-only visits are outside this cohort.

    No opted-in browser was observed in this window. This zero cannot show whether the wider audience returned.

    Inspect Fighter returns

What changed around this activity?

Dated release observations sit beside the collection and comparison boundaries reported by each source. Nearby dates suggest questions to investigate; they do not show that a release caused a change in use.

This is a reviewed selection, not a complete release feed. Notes are frozen with the report and may precede the selected dates; notes after its last selected day are omitted.

Explore 6 dated release and collection notes
  1. Fighter · Source-owned fight reporting and optional returns released

    Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. Owning release and live public adapter checked. Browser identities are opt-in and partial. Historical QA exposure prevents clean pre-boundary growth comparisons; no new game playthrough or physical observation was performed here.

    Read release evidence · reviewed 2026-10-16
  2. Fighter · Comparison boundary

    The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.

  3. Fighter · fighter · native result sharing

    Exact-main Chromium/WebKit receipts cover real published media, excluded audible-progress reporting, saved shuffle and finished-result PNG/caption journeys. The public page build identifier independently matched this source. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. The reviewed browser receipts use excluded test attribution. They prove scoped behaviour, not real audience listening, score verification or a completed variant platform.

    Read release evidence · reviewed 2026-10-13
  4. Fighter · fighter · radio 1.2.0 release

    Exact-main Chromium/WebKit receipts cover real published media, excluded audible-progress reporting, saved shuffle and finished-result PNG/caption journeys. The public page build identifier independently matched this source. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. The reviewed browser receipts use excluded test attribution. They prove scoped behaviour, not real audience listening, score verification or a completed variant platform.

    Read release evidence · reviewed 2026-10-13
  5. Fighter · fighter · exact radio deployment

    Menu, Settings and Library expose music and both shows. The game audio manager retains authored Battle, Results and Cinema priority, independent effects and opt-in speech; forkable branded versions retain their own presentation. Human listening and physical iPhone remain unobserved. Its current station shuffle does not establish the future shared My Mix contract; optional client 1.2 telemetry is not installed.

    Read release evidence · reviewed 2026-10-11
  6. Fighter · Collection began

    First source-reported collection date. Earlier activity is unavailable; the first day may be partial.

Follow the numbers to their source

Every measure has a definition, a collection boundary and blind spots.

Fighter8 measures available

Live aggregate endpoint · generated

Collection began
2026-08-09T08:22:36.602Z
Comparable history from
2026-10-15T12:02:59.539Z
Source revision
Not supplied
  • Historical counts before 15 October 2026 include unmarked production QA that cannot be separated or subtracted. These are stored reports, not a clean audience cohort; exclude pre-comparableFrom history from growth comparisons and records.
  • Requested windows may include partial coverage. Current UTC day is partial. Stored browser reports are subject to privacy opt-outs, network loss and abuse controls; they are not unique people.
  • Launch/completion counters backfilled only from the raw rows retained at migration; earlier expired history is unavailable. Anonymous daily totals are retained durably thereafter.
  • Visits, engagement, deliberate Quick Fight replay and optional browser cohort measurement start 2026-10-15T14:34:02.048Z; earlier values are unavailable. Browser cohort rows and raw tab sessions expire after 90 days; anonymous daily counters remain durable.
  • Active-time collection starts 2026-10-15T12:02:46.571Z; earlier time is unavailable. Individual raw game and session facts still expire after 90 days.
Fight starts 161Reported activity
Browser-reported non-tutorial fight launches; match IDs deduplicate retries. Exact accepted events, not verified humans.
Completed fights 107Reported activity
Launched fights ending in win, loss, draw or forfeit, attributed to launch UTC day. Abandonment excluded; not a completion cohort rate.
Active gameplay 2m 5sReported activity
Cumulative foreground, focused, unpaused fight seconds with input in the preceding 60 seconds. Loading/countdowns, hidden tabs, idle and radio excluded. Browser-reported, bounded by server elapsed time; launch UTC day attribution.
Tab visits 3Reported activity
Accepted random tab sessions first observed since this metric began; one per tab session (including reloads), attributed to first observation UTC day, with raw tab deduplication retained for 90 days. DNT/GPC, automation and explicit QA excluded. Not pageviews or people.
Engaged tabs 3Reported activity
Tab sessions reaching at least 10 cumulative measured active gameplay seconds across fights. Attributed to the tab visit UTC day; at most once per retained tab. Menus, radio, pause, background and idle time excluded.
Deliberate Quick Fight replays 0Reported activity
Accepted deliberate Quick Fight launches after an earlier completed or explicitly abandoned fight in the same tab. Prior terminal match ownership is checked by the server; retries deduplicate. Automatic progression, tutorial and other-mode replay actions are outside this measure.
Opted-in browsers 0Reported activity
Distinct random browser IDs voluntarily enabled in Settings and observed in this window; never humans. Off by default; expires/rotates after 90 days. Daily distincts are not additive; period totals use distinct retained IDs, not their sum.
Returning opted-in browsers 0Reported activity
Distinct opted-in browser IDs observed in this window with an earlier different tab session in retained 90-day history (including same-day returns). Daily distincts are not additive; period totals are unavailable when the raw retention window is incomplete. Clearing/rotating IDs resets continuity; default tab-only visits are outside this cohort.

What am I looking at?

Anonymous tab sessions admitted by the collector. Opening another tab or returning after the session boundary may count again; a visit is not a unique person.

The chart uses one measure and one unit at a time. Each coloured line belongs to a project; the source totals cover the selected window.

What does it tell us?

We can see when recorded activity occurred and inspect how it is distributed across the selected dates.

No clean growth comparison yet. New collection and legacy test traffic limit the history we can trust.

Last complete week

The most recent complete Monday–Sunday UTC week for each project's own headline measure, against the week before. A record needs exact daily history for two adjacent complete weeks; this is a valid comparison, not only the large movements that raise an operational alert.

No project has two complete comparable weeks yet, so no week-on-week figure is shown. Collection is too recent to compare honestly, and nothing is inferred from it.

Why some projects are not compared (1)
  • Fighter: Fewer than two complete comparable weeks so far.

If you’re assessing the business

Early product instrumentation, with material evidence gaps.

Usage
1/1 projects reporting this measure. 7/7 sources provide some activity. Reports are not verified people.
Retention
No portfolio cohort-retention evidence. Returning browsers, where available, are a narrower signal.
Commercial proof
Revenue, paying customers, acquisition cost and customer value are not measured here.

Use this to ask better product questions. It cannot establish product–market fit, market demand or an investment case.

Read the product dossiers

Report details

Snapshot
78533b3457ba704d348cfc21
Captured
2026-10-23 04:50:18 UTC
Dates
2026-09-24 – 2026-10-23
Time zone
UTC; dates may differ from your local day
Tracking, retention & privacy choices