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

Command line arguments are hard to understand #212

Open
smoogipoo opened this issue Sep 1, 2022 · 2 comments
Open

Command line arguments are hard to understand #212

smoogipoo opened this issue Sep 1, 2022 · 2 comments

Comments

@smoogipoo
Copy link
Contributor

smoogipoo commented Sep 1, 2022

It'll probably prevent a lot of confusion if we invert arguments such that all rulesets are processed by default, and then --ruleset=1 --ruleset=2 will be a marker to only process the given rulesets. Along the same line of thinking, --no-converts instead of --allow-converts.

@Coppertine
Copy link

I would think that it could instead use the named rulesets instead to allow for approved custom rulesets in the future. i.e. --ruleset=osu --ruleset=catch --ruleset=xyz

@peppy
Copy link
Member

peppy commented Sep 2, 2022

Yeah, we should be moving away from using IDs, as ShortName is the future way to reference to rulesets (for anything at a client / user-level).

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

3 participants