-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Complete the Input device
articles
#9922
Comments
Input device
articlesInput device
articles
i'm not sure we need stubs for all of these, i mean they're not osu terms or anything. wouldn't one article be better? |
for exotic devices, sure, but I imagine that for keyboards, mice, and tablets it's possible to produce something decent that would pass as a separate piece of text |
Tbh I wonder, wouldn't it be good to just delete Beatmania controller, Dance pad, Drum controller and Wiimote. |
I thought the whole wii thing was specifically for the wii's tatacon. maybe I'm getting that horribly mixed up. but anyway yeah per walavouchey and ticclick's comments above, I think it'd be best that only the very standard input types (kb, mouse, tablet, maybe touchscreen) get an article with whatever can be said about them, and then leave the uncommon ones to just a short mention in the index page, if relevant at all. |
Honestly I think getting rid of the useless ones is a better idea in general. They aren't used and I imagine that especially new players will visit |
All the input devices you mention have code in the game to support them. This is why we list them. |
Since it's supported in-code, this is due diligence to document them properly IMHO. It's not really a matter if they're esoteric or niche if they're officially supported. |
Beatmania controller
: stub + dull wordingDance pad
Drum controller
Graphics tablet
Keyboard
: stub + extremely shortMouse
: stub + almost solely about mouse-related osu! options, which is oddTouch device
Wiimote
-- do we need it? looks like it only exists because of mention in osu! optionsThe text was updated successfully, but these errors were encountered: