Skip to content

[UX] Separate File > Save > Collection (.db/.osdb) per format #128

@sebastienOillic

Description

@sebastienOillic

Reason
This proposal stems from a user experience issue that I've had from using the software.
Namely, I was trying export collections made through osu lazer and import them back to osu stable.
The issue that I had was that the default format used .db and when I tried to download all beatmaps missing from stable, the program would claim the beatmaps were unknown due to the fact that only a hash was used to designate the beatmaps in the .db file.
The issue was resolved after switching the export to the .osdb format.
However, it felt logical/natural to me to assume that the information about the beatmaps would be the same regardless of the format.

Proposal
Spilt the File > Save > Collection (.db/.osdb) in 2 to underline that the 2 file formats have a different output type / intent.
It would be also preferable to have a tooltip on long hover to explain the intent of the format.
For example :

  • .db : Intended for replacing a collection database on Osu! stable
  • .osdb : Indented for sharing collections with other users through CM and beatmap downloading

Of course these wordings are merely suggestions and I'm pretty sure there are imprecisions in what I've laid out in these wordings.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions