forum

[invalid] [Proposal - osu!mania] Move osu!mania hitsound RC to dedicated page

posted
Total Posts
5
Topic Starter
Ryu Sei
This exact point in audio rules regarding hitsound looks messy:
Beatmaps must be hitsounded. Hitnormals give feedback to the player, and additions (whistles, claps, and finishes) accent the most important parts of the music.
  1. osu!mania beatmaps do not require hitsound additions. This is to allow for easier approachability to osu!mania mappers of different upbringings. It is still highly recommended to use hitsound additions to improve the feel of your beatmaps.
We can move the entire point of osu!mania hitsounding "guideline" to its dedicated page rather than putting it to general RC, so it become this: (see italicized text for changes)

Rules (General)

Beatmaps must be hitsounded. Hitnormals give feedback to the player, and additions (whistles, claps, and finishes) accent the most important parts of the music.
  1. osu!mania beatmaps only require hitnormals. This is to allow for easier approachability to osu!mania mappers of different upbringings. The exception where hitnormals are not required is for keysounds in osu!mania beatmaps.

Guidelines (osu!mania)

It is recommended to use hitsound additions. The hitsound additions will enhance the feel of the beatmap. Keysounded beatmaps are exception.
This is a more direct approach rather than using the current clause that we use before. Any suggestions?
Drum-Hitnormal
i think move the whole HS thing to each mode page.

prevent std hs change accidently break mania, taiko and ctb in future.

hitsound practices are way too different between each mode
RandomeLoL
There was never a hitnormal requirement. No mode requires it. The proposed wording would make them mandatory and that is something that has to be discussed elsewhere.

Speaking of the proposal, I don't think moving it is necessary. At least at the moment. Overall I'd say it makes it a bit messier as well as you are duplicating the keysounding exception.

Also the general RC isn't only for Standard. Each mode has its own RC and changes that would only affect X mode should be written as such.

In short, I don't think the current wording is confusing, nor that a change is needed. If we were to do that with all clauses, it would not make sense to have a General RC to begin with :P . But if it gets moved, it should not repeat exceptions between Criterias like it's currently worded in the proposal.
Topic Starter
Ryu Sei
Apparently this roots to the fact where hitsounding RC is ambiguous at the first place. I would like to close this topic and write another thread to keep it in line.
Sies
Moved and markes as invalid
Please sign in to reply.

New reply