resources.osucord.moe

To suggest a missing resource, open the GitHub page linked from resources.osucord.moe and either create an issue describing the addition or open a pull request with the change. The site explicitly invites both routes under its "Is something missing?" section, and the list is maintained by staff of the osu! Game Community Discord server with community contributions.

What the site is

resources.osucord.moe is a curated collection of links for osu! players, mappers, and skinners. It is maintained primarily by the Discord server's staff, with contributions from the community, and the same list appears in the server's #osu-resources channel. The page shows a last update date, so you can judge how current the list is before relying on it.

The list is organized into sections such as:

• Official Links — osu! YouTube, Twitter, osu!wiki, official tournaments, community Discord servers, and the ppy blog
• Tablets — OpenTabletDriver, Kuuube's tablet sheets and buying guides, and community firmware projects (with a warning that firmware use is at your own risk and may void warranties)
• Replay and Score Analysis — Danser-Go, o!rdr, Rewind, osu-aim-analyzer, and replay viewers
• Stats Trackers — osu!track, Daily Challenge Stats, osu!Stats, osu!daily, and realtime stats tools

Steps to submit a suggestion

1. Check the list first. Search the page for the tool or site you have in mind. If it already appears in a section, no submission is needed.
2. Go to the GitHub page. Use the "Create an issue" link in the "Is something missing?" section of the site.
3. Choose issue or pull request.
   • Issue: describe the resource, its URL, and which section it belongs in. This is the lower-effort option if you don't want to edit the list yourself.
   • Pull request: add the entry directly to the list file, matching the existing format and placing it in the most relevant section.
4. Explain the fit. State what the resource does and who it helps (players, mappers, skinners). Additions and improvements are both welcome, so fixes to existing entries are valid submissions too.
5. Wait for review. Staff maintain the list, so acceptance is at their discretion; expect the entry to appear only after it is merged and the page is next updated.

Common snags

• Wrong section. A tool filed under the wrong heading is more likely to be sent back; check how similar entries are grouped.
• Duplicate links. The list already covers many popular tools, so search before submitting.
• Firmware and risky tools. The tablet firmware entries carry explicit warnings about warranty and bricking risk. If you suggest something in that category, note the risk so maintainers can present it the same way.
• Stale date. The page displays a last update date; if it looks old, your suggestion may simply be waiting on the next maintenance pass rather than being rejected.

The osu! Game Resources site (resources.osucord.moe) lists five replay and score analysis tools in its "Replay and Score Analysis" section: Danser-Go for local replay rendering, o!rdr for online rendering, Rewind for detailed replay analysis, osu-aim-analyzer for aim mistakes, and Replay analyzer for hit error and timing distributions. A sixth entry, replayviewer, is marked as new and covers replay rendering plus ranked and tournament matches across all game modes. The list is curated by staff of the osu! Game Community Discord server and was last updated 2026-09-27.

The tools at a glance

How to choose between them

The entries overlap, so pick by task rather than by tool count:

• You just want a video of a play. Use o!rdr if you don't want to install anything, since it runs the render online. Use Danser-Go if you'd rather render locally, for example when you have many replays to process or want to avoid uploading them.
• You want to understand why a play went wrong. Rewind is described as analyzing replays in meticulous detail, which suits frame-by-frame review. osu-aim-analyzer narrows in on aim specifically, so it fits players whose misses come from cursor control rather than rhythm.
• You suspect timing or input issues. Replay analyzer's hit error, frametime, and holdtime distributions show whether your hits cluster early or late and whether frame pacing or hold duration is unstable.
• You need coverage beyond standard plays. replayviewer is the only entry explicitly covering ranked play and tournament matches, and it works for all game modes.

A practical sequence for most players: render with o!rdr or Danser-Go to see the play, then open the same replay in Rewind or osu-aim-analyzer to find the cause, and use Replay analyzer if the problem looks like timing rather than aim.

What the page does and doesn't tell you

The listing gives names and one-line descriptions only. It does not include download links, version numbers, platform requirements, or setup instructions for any of these tools, so treat the site as a starting index and check each tool's own page before installing. The page also carries no pricing information, so nothing here should be read as confirming a tool is free.

Related sections on the same page

The site groups resources by purpose, and two neighboring sections are relevant if you're tuning your setup before analyzing plays:

• Tablets — OpenTabletDriver, plus Kuuube's tablet buying guide, Wacom mastersheets, pen compatibility and pen nib guides. Firmware entries (xstarry's and shavit's Wacom firmware, catears124's Gaomon firmware) are flagged as new and carry an explicit warning: use at your own risk, warranty may be voided, the tablet could be bricked, and most tablet features are often disabled to maximize polling rate. The page advises reporting issues to the firmware authors first.
• Stats Trackers — osu!track for pp gains and top 100 scores over time, osu!Stats for finding scores matching certain parameters, osu!daily for profile/score/pp tracking, and realtime stats pages for seeing how many people are playing throughout the day.

Suggesting a missing tool

The page invites additions through its GitHub page: open an issue or a pull request with the resource you want added or the improvement you'd like. That's the route to take if a replay or analysis tool you use isn't among the six listed.

resources.osucord.moe is a curated link directory for osu! players, mappers, and skinners. It collects tools and resources in one place, is maintained primarily by staff of the osu! Game Community Discord server with community contributions, and mirrors the list shown in that server's #osu-resources channel. Use it when you want a vetted starting point for osu!-related tools rather than searching scattered forum threads and wikis. The page notes a last update of 2026-09-27.

Who maintains it and how it stays current

The list is created and primarily maintained by the osu! Game Community Discord staff, with additions from the wider community. Anyone can propose changes: the page invites visitors to open an issue or a pull request on its GitHub page if something is missing or could be improved. That means the directory is community-editable rather than a fixed editorial page, and the "Last update" date is the best signal of how fresh the entries are.

What kinds of resources it lists

The directory groups links by purpose. Based on the page, the visible categories include:

Each entry is a short label plus a link, so the directory works as a jumping-off point rather than a tutorial. For example, if you want to render a replay, the list points you to Danser-Go for local rendering or o!rdr for online rendering powered by Danser-Go.

How to use it effectively

1. Start with the category that matches your role. Players will get the most from replay analysis and stats trackers; tablet users from the driver and buying-guide links; mappers and skinners from the broader tool list.
2. Treat tablet firmware links with caution. The page itself warns that tablet firmware use is at your own risk, can void warranties, could brick the tablet, and often disables most tablet features to maximize polling rate. It also advises reporting issues to the firmware authors first.
3. Check the source before installing anything. Because entries are community-submitted links, verify the destination and the project's own documentation before running tools or firmware.
4. Contribute if something is missing. The intended path is an issue or pull request on the GitHub page, which keeps the list useful for the next visitor.

What it is not

The site is a link collection, not a host for downloads, accounts, or services. The page does not state pricing, login requirements, or download terms for the listed tools, so check each linked project for its own conditions. It also does not replace the official osu!wiki or tournament listings; it points to them. If you need one maintained index of osu! community tools, this directory is a reasonable first stop, with the caveat that third-party links and firmware should be evaluated on their own merits.

The osu! game resources list recommends one open-source driver (OpenTabletDriver), a set of buying and compatibility guides by Kuuube, and several community firmware options for Wacom and Gaomon tablets. The firmware entries carry explicit warnings: they can void your warranty, may brick the tablet, and often disable most tablet features to maximize polling rate. Use the guides to choose hardware, and treat firmware as an advanced, risk-accepted step.

Driver and setup

OpenTabletDriver is the only driver listed. It is open-source, which makes it the default starting point for players who want configurable tablet behavior without vendor software. The list does not document installation steps, supported models, or platform requirements, so check the project's own documentation before switching drivers.

Buying and compatibility guides

Kuuube's guides are the list's reference material for choosing and checking a tablet:

• Tablet Buying Guide — what to consider when picking a tablet for osu!.
• Wacom Tablet Mastersheet — model-level reference for Wacom tablets.
• Wacom Tablet Pen Compatibility Mastersheet — which pens work with which Wacom tablets.
• Wacom Pen Nib Guide — nib information for Wacom pens.

These are most useful before a purchase, or when you already own a tablet and need to confirm pen or nib compatibility.

Firmware options and tradeoffs

The list presents firmware as a way to raise polling rate, with the risk stated up front:

The list's warning applies to all of them: use at your own risk, warranty may be voided, the tablet could be bricked, and most tablet features are often disabled to maximize polling rate. It also says to report issues with the tablet to the firmware authors first.

How to decide

• Just want a working tablet: use OpenTabletDriver and skip firmware.
• Choosing hardware: read Kuuube's buying guide and the Wacom mastersheets before buying.
• Chasing higher polling rate: confirm your exact model appears in the relevant firmware's supported list, accept the warranty and bricking risk, and keep a recovery path in mind before flashing.

The list is maintained by staff of the osu! Game Community Discord server with community contributions and was last updated 2026-09-27. Missing resources can be suggested through the GitHub issue or pull request links on the page.