Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Apeuriox/lazybot-renewal/llms.txt

Use this file to discover all available pages before exploring further.

Lazybot’s score lookup commands let you fetch a player’s highest score on any beatmap in seconds. Whether you want a clean score panel with PP breakdown, every score a user has ever set on a map across all modes, or a full beatmap attribute sheet with override support, these three commands have you covered.

/score — Single Best Score on a Map

Aliases: s, pscore Fetches the single highest-scoring play a user has made on a specific beatmap, filtered by the mod combination you provide. On QQ/OneBot, invoking the command as pscore (or passing a panel-version & that resolves to version 3) returns a PP+ quadrant panel instead of the standard score card.
bid
integer
required
The beatmap ID (BID) to query. This is the only required parameter.
user
string
Player name to query. Defaults to the caller’s linked osu! account.
mod
string
Mod filter, e.g. HDHR, DT, HDDT. Leave blank to match any mod combination.
mode
string
Game mode override. Accepted values: osu / o / std, taiko / t, catch / fruits / ctb, mania / m. Defaults to the user’s saved default mode.
algorithm
string
PP algorithm version. Accepted values: 202210, 202411, 202502, 202510, 20260706. When omitted the instance’s server-configured default is used.
version
integer
Panel style selector. On QQ this is controlled by the number of & characters appended to the command. & count 3 (or the alias pscore) renders a PP+ data panel.

Examples

/score bid:4889657
/score bid:4889657 user:Aloic mod:HDHR
/score bid:4889657 user:Aloic algorithm:202502
/score bid:4889657 user:Aloic mod:HD version:2
Algorithm versions correspond to specific rosu-pp algorithm snapshots used during official PP reworks:
  • 202210 — October 2022 (aim rework)
  • 202411 — November 2024
  • 202502 — February 2025
  • 202510 — October 2025
  • 20260706 — July 2026
Pass the version string with @ prefix on QQ (e.g. @202502) or via the algorithm slash-command option on Discord.
Panel version (& suffix on QQ): The number of & characters appended to a QQ command selects the score panel style. Three & characters (or the pscore alias) switches to the PP+ quadrant grid panel. On Discord, use the version integer option.

/allscore — All Scores on a Map

Aliases: as, allscores, ass Returns every score a player has set on a specific beatmap across all modes, alongside partial PP calculation intermediate values. Useful when you want to see if someone has scores in multiple modes or with different mod combinations on the same map.
bid
integer
required
The beatmap ID to query.
user
string
Player name to query. Defaults to the caller’s linked account.

Examples

/allscore 4889657
/as Aloic 4889657
/ass Aloic 4889657
/allscore is currently QQ/OneBot-only; the Discord slash command implementation is pending.

/m — Beatmap Statistics Panel

Alias: map Displays a comprehensive attribute panel for a beatmap under any mod combination you specify. Supports AR, CS, and OD override — meaning you can preview how a map would feel with custom difficulty settings (e.g. for DA mod scenarios), and optionally request a recalculated PP estimate at a target accuracy.
bid
integer
required
The beatmap ID to query.
mod
string
Mod combination, e.g. HDHR, DT. Appended to the BID with +, e.g. 4889657+HDDT.
target_accuracy
float
Target accuracy percentage for an additional PP recalculation (e.g. 98.5).
AR
float
Override the approach rate (0–11). Format: AR9.5 or AR 10.
CS
float
Override the circle size (0–10). Format: CS4 or CS 4.
OD
float
Override the overall difficulty (0–11). Format: OD9 or OD 9.
algorithm
string
PP algorithm version string. Same values as /score. Pass with @ prefix on QQ.

Examples

/map 4889657
/map 4889657+HDHR 98.5 AR9.5 CS4 OD8
/m 4889657 AR10 CS4
/map 4889657+HD 98.5 OD9 AR9.5 @202502
Combine mod overrides with custom AR/OD values to simulate how a map plays with the DA (Difficulty Adjust) mod — useful for tournament mappool analysis or skill-ceiling checks.

Build docs developers (and LLMs) love