How to Suggest a Missing Resource to osu! Game Resources

Updated

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.