What is here
1352 values for 182 players, 120 of them with a tablet area, and a page for each of the top 10,000 ranked osu!standard players. Ranks and top plays come from osu! itself and are kept current. Setups are rarer and harder to get right, which is why each one carries its source.
Where values come from
Each value has one of six marks beside it. The shape says what kind of source it has, and the ring around it empties as the value ages.
- From the player The player said so themselves. Nothing outranks this.
- Measured Worked out from data rather than typed in. Today that is how much of a player’s top 100 was set on lazer, counted from the osu! API.
- Sourced Read from somewhere the player controls, such as their profile or a chat command, with a link to it.
- Community Sent in by someone else and checked before it was shown.
- Stale Not confirmed for two years. It is still shown, because an old area is better than none, but it is marked.
- Conflicting Two sources disagree. The better one is shown and the other is listed under it.
Click the mark on any value to see every claim behind it, best first. When sources disagree the order is: the player, then measured, then sourced, then community. Within one kind the newest wins.
The 2024 database
Most setups here today come from the first version of this site, which collected them in 2024 from players and from people who watched them. Those values keep their 2024 dates. Most have now passed two years, so they show as stale until someone confirms them again.
What comes from osu!
Ranks, performance points, accuracy, play counts and top plays come from the public osu! API. The top 10,000 ranks are refreshed once a day. Players with a setup on record, and the top 1,000, also have their profile and best 100 plays refreshed.
The live numbers in the top bar and on the home page come from the same API’s feed of passed scores, which this site reads every few seconds and stores. Each score says which client it was set on, which is where the stable and lazer split comes from.
Tablet areas
An area is drawn to scale in millimetres on the tablet it was measured on. Tablet dimensions come from OpenTabletDriver’s configurations. Where a player’s tablet is not known the area is drawn on a plain surface and nothing is said about how much of the tablet it covers. Where the position of an area is not known it is drawn centred and labelled as assumed.
Export gives an OpenTabletDriver command, the values to type into osu!lazer, or your own driver settings file with only the area changed. The file is read in your browser and is not uploaded.
Profile pages, chat commands and suggestions
Two sources are a player’s own words and change when the player changes them: their osu! profile page, and the replies their Twitch chat bot gives to commands such as !area or !keyboard. Where a player’s profile links their Twitch channel, the site reads the channel’s public command list on Nightbot, StreamElements and Fossabot about once a day, along with the profile page. Values from them are marked with the source in its own words, such as “Twitch !area”, and when a command changes or goes away, so does what it said here.
A language model (Claude) reads these texts and answers in a fixed form: which field, what value, and the exact words it was read from. Nothing it says is taken on trust. A value has to fit what its field can hold, an area has to fit the tablet it is on, and a value the model was not sure of is dropped. How often it is right is measured against real texts labelled by hand: on 180 chat commands from 27 players that were never used to adjust it, 151 of the 154 values it would have published were right (98%), and on the 554 texts it was adjusted against, 626 of 630 (99%). It runs unattended only while that stays above 95%. It will still be wrong sometimes, which is what the pencil on every row is for.
Anyone can suggest a value from a player’s page, with a link or a few words on where they saw it. A link to a screenshot, a paste or the player’s own profile is fetched and checked automatically, and a copy is kept in case the original goes away. Other sites are not fetched; a person looks instead. A suggestion appears on the page once it is accepted, marked as coming from the community, with its date.
Replays and what is measured from them
For the top 1,000 players and anyone with a setup on record, the site downloads the replays of their best plays from the osu! API, a few a minute, and keeps them. Each one is played back through the site’s own copy of the game’s rules and the result is compared with the 300, 100, 50, miss and combo counts the game recorded for that score. The stats page says how often the two agree. Where they do not, the replay says so when you watch it, and the marks on it may be a slider end away from where the game put them.
Values marked as measured come from these replays: which keys a player taps with and how evenly, whether they alternate, how steady their timing is, and for stable replays the height of the game window, which shows in the size of the steps the cursor moves in. A measured value needs at least three replays that agree and is never typed in by anyone.
Replays are drawn with the default osu! skin and hit sounds from ppy/osu-resources, used under the Creative Commons Attribution-NonCommercial 4.0 licence.
Correcting something
Every row has a pencil that opens a short form in place: the new value and where you saw it, such as a stream, a video or a message from the player. A player with nothing on record has an “Add a setup” button that does the same. What is waiting, and what was decided, is on the suggestions page.
If you are a player and want your page changed or removed, use removal and takedown. Being listed is opt-out: a removal request from the player is always honoured.
What this site is not
osuconfigs is a fan site. It is not affiliated with or endorsed by osu! or ppy Pty Ltd, and it does not host or modify the game. It reads the osu! API within its published limits.