Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] Add argument for specifying path to beatmap #266

Closed
daifkyou opened this issue Jul 26, 2022 · 1 comment
Closed

[Proposal] Add argument for specifying path to beatmap #266

daifkyou opened this issue Jul 26, 2022 · 1 comment

Comments

@daifkyou
Copy link

daifkyou commented Jul 26, 2022

AFAIK and according to the creator of danser-go, there is no way to simply use a beatmap at a certain path.
This is a problem because specifying paths could be useful in some cases:

  • In the absence of an osu! installation (e.g. with McOsu I think) or with multiple osu installations (although this could be solved somewhat with different settings files)
  • When its location is already known, avoiding the overhead of finding the beatmap
    • When using a custom algorithm to determine which beatmap to use
  • Opening beatmaps e.g. from the file manager (with e.g. a custom .desktop file) which could be useful for e.g. previewing maps I guess?

To solve this problem, an argument such as "beatmap" could be added which would allow specifying the path to the beatmap.

@Wieku
Copy link
Owner

Wieku commented Jul 26, 2022

Already denied in #228

Too much of a hassle to add, honestly. Danser can work without osu! as long as you keep Songs folder in stable's hierarchy. Danser can even unpack .osz by itself.

You should use GUI. If you're making a script, you can calculate md5 hash of the .osu file and then launch danser with -md5 flag. Or with -id, if map id is bigger than 200000-ish.

@Wieku Wieku closed this as completed Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants