====== Broken-map reports and exclusions ======

Report missing audio or another broken chart through [[commands:discord|Discord]], giving the room, approximate time, song/difficulty and beatmap link or ID. The map that appears next in the queue may not be the map just played; staff check actual match records before identifying the chart.

===== What an exclusion means =====
Exclusions target **exact beatmap IDs**, not every chart of a song or beatmapset. The reported-audio removals in [[updates:v6_7_28|v6.7.28]], [[updates:v6_7_29|v6.7.29]] and [[updates:v6_7_31|v6.7.31]] are precautionary responses to player reports, not proof that the audio was independently inspected. Historical scores, ratings and research are retained.

From [[updates:v6_7_32|v6.7.32]], operators can update an external exclusion list without a new bot release. Standard, DT and Mania selection, style fallback, replay and playlist writes all respect it. A future catalogue rebuild that contains an excluded row still cannot select it while the runtime policy is active.

===== What players notice =====
The bot checks the local list about every two seconds, with no API requests for the check. Excluded future playlist entries are removed/replaced at a safe between-match point after a server audit. It does not interrupt an already running map or countdown. If an excluded upcoming current item has no replacement, starting it is blocked.

Removing a list entry does not restore a chart already removed from a pinned catalogue, or clear a separate temporary download-unavailability quarantine. A policy change is different from a database rebuild.

===== Operator configuration =====
The hot-reloadable ''beatmap_exclusions_file'' setting points to a service-readable external JSON file. The deployed policy is operator-owned and not writable by room workers. There is no new player or moderator chat command to edit it.

<code json>
{
  "schema": 1,
  "exclusions": [
    {"beatmap_id": 4364911, "reason": "Reported missing audio"}
  ]
}
</code>

Add each affected difficulty separately and save atomically where possible. Maximum file size is 1 MiB. Additional evidence fields may be retained. Invalid/missing updates retain the last valid policy; a newly starting worker with an unreadable configured policy cannot select maps. Runtime protection is not a substitute for exclusion checks when exporting future catalogues: the legacy research export still requires that separate integration.

[[wiki:map_selection|Selection rules]] · [[wiki:queues|Safe playlist changes]] · [[wiki:catalog_refresh|Research and live data]]