Sloppy Modding Checklist

Maintain a modding checklist on osu! beatmap discussions: four cells, each entry tagged by the difficulty it applies to.

Sloppy Modding Checklist keeps a structured modding checklist on osu! beatmap discussion pages, so the list no longer has to be maintained by hand in a separate document. It gathers the beatmap issues worth checking into one checklist, and every entry can carry a link back to the post it came from. Once the extension is installed, an "Add to Checklist" button appears under each post on a discussion page. Clicking it turns that post into a modding checklist entry. The scope, the source and a link to the original post are filled in automatically, the summary is taken from the post text, and any of them can be changed afterwards. A floating button in the bottom left corner opens the checklist page. Entries are sorted into four sections, by scope and by source: - General / Internal: issues with the whole beatmap, raised by the checklist owner - General / External: issues with the whole beatmap, raised by someone else - Individual / Internal: issues with a single difficulty, raised by the checklist owner - Individual / External: issues with a single difficulty, raised by someone else On the checklist page the four sections sit side by side, and the entries inside each one are numbered in order. Every card shows its summary, the difficulty it applies to, its links and its note. Entries can be reordered within a section or dragged into another one, and can be edited or deleted at any time. An Individual entry can be tagged with the difficulty it applies to, one of Easy, Normal, Hard, Insane or Expert. When an entry is added from the discussion page of a particular difficulty, that difficulty is detected from the beatmap's difficulty name or its star rating and filled in; when it cannot be detected, the field is left empty. The tag on the card uses osu!'s own difficulty colors. Clicking the toolbar icon shows how many entries each of the four sections holds and how many there are in total, and provides a link straight to the checklist page. The checklist can be exported to and imported from JSON, with a choice of merging or overwriting on import. There are three ways to sync, and only one is used at a time: - Local sync folder: a folder is chosen, the extension writes modding-checklist.json into it, and the cloud client handles the upload. No app registration and no account sign-in. - WebDAV: a server address, a username and a password. - Dropbox: requires creating an app in the Dropbox App Console and pasting its App key into the settings page. Sync can be set to upload automatically after changes and to import when the extension starts. When both sides have changed, a conflict strategy decides what happens: newest timestamp wins, local wins, remote wins, or ask every time. The settings page shows the total number of entries, the device id, the time the document was last updated and the save status, and can clear the local data. The interface is available in English and Chinese, and follows the browser by default. Data is stored locally in the browser and is not sent to the developer, who has no server that could receive it. The checklist only leaves the machine once sync is switched on, and then only to the server or folder the user has chosen. Adding an entry reads public information from the osu! page — the post author and the beatmap's difficulties — reusing whatever osu! session the browser already has. Exported files contain no passwords and no access tokens. This extension is a personal project and is not affiliated with osu!.