Basketball Bros Update Tracker: What We Can Verify

Current verified baseline

CrazyGames identifies Blue Wizard Digital as developer, January 2020 as release date, and March 20, 2025 as last updated. It describes browser play, same-PC two-player, Franchise, Shooting Practice, and private Host or Join games.

It lists WASD plus G and arrow keys plus L. This is a metadata baseline, not proof that every mode, character, animation, or balance value stayed unchanged.

• Source checked: CrazyGames BasketBros page.
• Fact-check date: July 30, 2026.
• Displayed last-update date: March 20, 2025.
• Itemized official patch notes located on that page: none.
• Evidence level: published platform metadata.

Why an update date is not a changelog

A platform can update a listing, integration, compatibility layer, description, thumbnail, or game build. Without patch notes, the date does not reveal which applies. Assigning a character, move, or mode to March 20 would be speculation.

When a source publishes only a date, this tracker will report only the date. If an official developer post later describes the contents, we can add that source and revise the entry with a separate modified date.

Do not treat CDN timestamps as release notes

Developer tools may expose asset names, response headers, cache ages, or storage dates. Those describe delivery and caching, not necessarily a feature launch. A file can be copied or revalidated without changing gameplay.

A Last-Modified header, version-like query string, or cached asset is only a clue. We will not turn CDN metadata into a patch claim without a public source or reproducible comparison.

Use three evidence levels

A simple evidence label keeps the tracker honest. “Officially documented” means a named developer or platform explicitly described the change. “Platform metadata” means a public listing supplied a date, control, mode, or developer field without detailed notes. “Observed, not officially documented” means a repeatable interface difference was recorded with context but no official explanation was found.

Rumors, copied snippets without a source, search-result dates, and one person's memory do not qualify as tracker entries. They can become leads for verification, but they should not be presented as facts.

Run a reproducible change check

When a possible change appears, record the page URL, date and time, browser, device class, game mode, and the exact text or behavior observed. Repeat the observation in a fresh session before comparing it with the previous baseline. Change only one condition when possible.

• Capture the public source title and direct URL.
• Quote only the short field or label needed to identify the change.
• Describe the previous and current states without guessing at the cause.
• Check controls, menu labels, modes, and visible version text separately.
• Assign an evidence level and state what remains unknown.
• Never publish private account, room-code, or network information as evidence.

Tracker entry template

Each entry should be compact enough to audit later. Use this structure: verification date; claimed change; affected mode or interface; source URL; evidence level; reproduction steps; previous baseline; current observation; unresolved questions; and editor note. If no trustworthy source explains the change, say so directly.

The modified date on this article should change only when the tracker content changes. It should not be advanced automatically by a deployment, a cache refresh, or a scheduled publication job.

How readers can submit a useful correction

A useful report names the current menu or mode, explains exactly what differs, and links to a public primary source when one exists. Screenshots can support visible text, but they should omit account details, private messages, and room codes. A report should also state the observation date because browser games can change between sessions.

We will prefer developer and platform documentation over third-party summaries, and we will mark uncertainty when primary documentation is missing. That may make the tracker shorter than a rumor roundup, but it makes every listed claim easier to inspect and correct.