With the "recent" rewrite of the metadata ranking criteria, new guidelines, allowances, and rules were introduced, many allowing for more stylization and others being more direct compared to what they were before. One of these new additions was the allowance (or specification) that markers, such as `(TV Size)`, `(Cut Ver.)`, and `(Game Ver.)` may use alternate casing as long as it fits the song. This may also apply to `feat.` markers, as those are standardized by osu! ranking criteria as well. This would not apply to names, as those are expressed by the artists and should not be changed.
For example, this would allow for someone to write `SONG TITLE (TV Size)` as `SONG TITLE (TV SIZE)`, which allows for more stylization by the mapper while also staying objective and true to the artist's intention with the song title.
This has been observed a couple of times, namely with this map using a lowercase `(tv size)` marker and this map using an uppercase `(GAME VER.)` marker.
My proposal would be to allow more freedom in this while still keeping titles objective.
This would mean that someone could map `CHOIR JAIL (TV Size)`, which has normal capitalization within the marker, and make the title `CHOIR JAIL (TV SIZE)`, which fully uppercases the marker. This does not affect searchability as none of the characters are actually changing. osu! search isn't case sensitive, like a .
This would serve the following use:
* Someone wants to rank a song but the previous ranked map of the song uses/doesn't use a stylized marker, and the mapper wants to do the inverse of that (either make it stylized or make it normal.)
This would NOT apply when:
* A song already has a marker that is spelled the same way as an osu! marker and uses a specific casing. For example, a song called `GENERIC SONG TITLE (Nightcore Mix)` could not be changed from that, as the artist has already intended for the marker to be capitalized a certain way and it is already spelled as osu! dictates. A song called `GENERIC SONG TITLE (Video Game Mix)` would still be written as `GENERIC SONG TITLE (Game Ver.)` as the entire marker must be standardised and isn't already spelled as osu! dictates.
In summary, this proposal is to allow mappers to use alternate casing for markers when applicable and ignore ranked consistency. The use for this would be when a mapper does not like the casing of the previously ranked map and wants to have more/less expression within it.
For example, this would allow for someone to write `SONG TITLE (TV Size)` as `SONG TITLE (TV SIZE)`, which allows for more stylization by the mapper while also staying objective and true to the artist's intention with the song title.
This has been observed a couple of times, namely with this map using a lowercase `(tv size)` marker and this map using an uppercase `(GAME VER.)` marker.
My proposal would be to allow more freedom in this while still keeping titles objective.
This would mean that someone could map `CHOIR JAIL (TV Size)`, which has normal capitalization within the marker, and make the title `CHOIR JAIL (TV SIZE)`, which fully uppercases the marker. This does not affect searchability as none of the characters are actually changing. osu! search isn't case sensitive, like a .
This would serve the following use:
* Someone wants to rank a song but the previous ranked map of the song uses/doesn't use a stylized marker, and the mapper wants to do the inverse of that (either make it stylized or make it normal.)
This would NOT apply when:
* A song already has a marker that is spelled the same way as an osu! marker and uses a specific casing. For example, a song called `GENERIC SONG TITLE (Nightcore Mix)` could not be changed from that, as the artist has already intended for the marker to be capitalized a certain way and it is already spelled as osu! dictates. A song called `GENERIC SONG TITLE (Video Game Mix)` would still be written as `GENERIC SONG TITLE (Game Ver.)` as the entire marker must be standardised and isn't already spelled as osu! dictates.
In summary, this proposal is to allow mappers to use alternate casing for markers when applicable and ignore ranked consistency. The use for this would be when a mapper does not like the casing of the previously ranked map and wants to have more/less expression within it.