forum

[Proposal] General RC change regarding CS values

posted
Total Posts
36
Topic Starter
MBomb
Hello there!

CS values below 2, or above 7, are currently considered unrankable, since they require making changes to the .osu file, which breaks the following rule:

Do not edit the .osu file to modify difficulty settings or insert break times in ways that are unintended for each respective game mode. Other .osu file edits such as stack leniency, slider velocity, and skinning settings are acceptable.


However, I feel that these CS values should be allowed, since they function in similar ways to other CS values if the .osu is changed, meaning they don't break anything, and there's even an argument that because of this, they shouldn't fall under the "unintended" category at all, however it is generally agreed that they do.

Whilst these CS values may seem a little ridiculous to both players, mappers and BNs right now, I feel this is partly due to a lack of experimentation and usage of them, due to their current unrankability. However, I feel BNs should be, and are, able to determine whether the usage of these values is acceptable in a map in a case by case basis, rather than them being strictly a problem.

There are already multiple well made maps using these unrankable CS values, both in the loved section and in the graveyard, proving that the concept of making these maps isn't necessarily impossible, and can even work well.

I was originally planning on making this proposal purely for catch, but after discussion in the dev server, someone told me it was worth considering for standard as well.

My suggested change to the wording goes as follows.

Do not edit the .osu file to modify difficulty settings or insert break times in ways that are unintended for each respective game mode. Circle size values from 0 to 10 are acceptable, as these work as intended, even if you cannot reach them through the editor. Other .osu file edits such as stack leniency, slider velocity, and skinning settings are also acceptable.


I'll be honest, this wording can definitely be improved, but I couldn't think of how else to word it.

Please share your thoughts on this!
Sanyi
Would be cool imo, so I am supporting this change unless it causes some sort of problem we haven't figured out yet.
Daletto
I'd like this to be implemented since it opens up a lot of new maybe gimmicky maps and styles which you couldnt provide with current cs restrictions.
Nelly
+1 for me
Nao Tomori
if it doesnt actually break anything in the game i don't really see why not
Ascendance
why not just take the current rule and add "circle size values" to the exceptions list, i don't think it needs it's own sentence about specifics of circle size

or just change difficulty settings to be AR/OD/HP

ranking criteria wrote:

Do not edit the .osu file to modify approach rate, overall difficulty, HP drain or insert break times in ways that are unintended for each respective game mode. Other .osu file edits such as stack leniency, slider velocity, and skinning settings are acceptable.
Topic Starter
MBomb
Would also work, when I was looking at it, I was just thinking it may be a little weird since difficulty values are expressly mentioned in the things not to change (due to them breaking things if you use values that aren't possible I assume), so I separated them, but if people think it's clear enough with them in the exceptions part that works too.
Ascendance
yea I got what you were going for but I'm just tryin to find ways to condense it better since adding an entire sentence purely about CS is probably giving it too much attention

generally agree tho
Pennek
I think the wording Ascendance proposed looks pretty clear. Might also need a clause to restrict decimal abuse. Otherwise we might end up with absurd CS values on some maps
[Shiny]
I think this would be a very nice addition, as you have said, it will help to open the variety to gimmicky or different maps which uses them in a clever way.
My only concern is the limits about them, as I personally think that pushing the limits to 0 and 10 is a bit too much, at least on the higher side. Personally, I think CS0 (actually, it applies to OD/HP/AR as well) works bad, as it doesn't get higher with the HR mod, which is weird in a way, but it's probably intended to begin with (that's probably the reason why they are used at all). However, the fact that there are CS0 maps in the Loved category is a thing, so I guess the public acceptance of them is certain.
On the other side, pushing the limits to 10 seems a bit much, at least for me. I know people can make cool maps with high CS but I personally think 8, or at most 9 is fine. CS10 seems a bit too much. However, limiting the CS is one of the factors that this discussion was brought up so I guess it's contradictory.
But yes, I'm mostly neutral about this. Limiting CS to 2-7 has been always a weird thing to me, but pushing them farer than 1-8/9 would be weird too, just more flexible.

It's still a very interesting porposal anyway, I'm looking forward to this!

Nao Tomori wrote:

if it doesnt actually break anything in the game i don't really see why not

This need to be considered over everything, as I'm sure there is at least one bug when CS goes off the limits set by the editor (2-7).
Karoo13
There are no bugs caused by changing these numbers, but due to how HR and EZ multiply the values by 1.3 and 0.5, the behavior can be unexpected.

CS7.7 and above will all become 10 with HR, CS0 will not increase at all. These are likely the reasons it was restricted from 2 to 7 to begin with.

EZ will bring CS10 from 9.6px to 32px, 3.33x radius, which is quite unbalanced compared to say CS5 32px to 43.2px, 1.35x radius.

Not saying we shouldn't have more freedom as mappers, but due to how these dumb mods were implemented it might cause some score vs difficulty balance issues. If we had the chance to rewrite osu (coughcoughlazercough) it would be a good idea to have the CS value proportional to radius, so HR can do 0.85x and EZ can do 1.3x.
Topic Starter
MBomb
Whilst I do agree that it's a little unexpected behaviour, I don't think it's worth avoiding for this reason, since other difficulty elements also do the same thing of capping at 10 and not being able to go below 0. Whilst it's very rarely used, AR0 is fully rankable and does the same thing as CS0 does in terms of adding mods.

There's an argument for AR and HP not actually affecting gameplay, the same can't be said for OD (at least in standard), which also exhibits similar behaviour.
-Mo-
A quick number crunch just for information (standard). Note how the magnitude of change is greater at higher CS (20% difference in area for our typical values, but going onto 50% difference at the top end).



My initial opinion which was discussed in #modding was that CS outside of the current range for standard was just stupid to play with. CS1 and 0 seems absurdly large and doesn't really add much to the map beyond what CS2 already can. And CS>7 was just... silly.

I kinda wanted to see a good implementation of super high CS in a map before we could consider it, and well, this map kinda does.
Topic Starter
MBomb
Whilst for a different mode of the CS9 map there, this map is a good example of how CS0 can work really well in catch.
tatatat
I think it would be better to petition the developers to change the bounds of CS in the editor, so its accessible to everyone. This has already been done with SV limits in multiple gamemodes.

I personally see no problem with CS 0 through 2, or CS 7 through 8. CS 9 and 10 are too extreme in my opinion (at least for osu! standard)
-Mo-
What do you think about the map I linked @tatatat? That's currently using CS9 and I think they used it rather well.
tatatat
Maybe an ultra specific subset of players can play them, but I think it requires such accuracy that it might be physically excluding to some players. Like mouse players, or people with the tiniest bit of shaky hands. While you can certainly make decent maps at CS 9, are they accessible? Do you need to spend money on a tablet to play them?
abraker
I can't imagine why mouse players would have trouble with smaller circles.
clayton
how does this break the rule to begin with? CS outside of 2~7 does exactly as you'd expect and the game was intentionally designed to have it work from 0 to 10 like every other diff setting.

for clarity i'd add it to the "other edits" exceptions like ascendance suggested
-Mo-
I think it's more CS outside of 2-7 weren't supposed to be used for ranked maps (as suggested by the slider being limited in the editor) despite the game supporting it.
xenal

-Mo- wrote:

I think it's more CS outside of 2-7 weren't supposed to be used for ranked maps (as suggested by the slider being limited in the editor) despite the game supporting it.

HR and EZ cs increase/decrease gets unintended past a certain point. CS 0 means there will be no changes from HR/EZ, and anything past CS 7.7 means HR get caps at 10. A CS/AR/OD 10 map will not change when using HR other than flip the map but would yield more score than a nomod.

While it does work, it doesn't mean that it should be allowed.
LowAccuracySS
im all for increasing the amount of possibilities with mapping- if maps like promethean kings can get ranked while being exceedingly hard for most players, I don't see why cs above 7 shouldn't be allowed /shrug
Sleepteiner
If one of the main issues that people have with removing the rankable limit at CS7 is that higher CS is too extreme, we could implement this kind of thing incrementally. Like, we make CS8 rankable and wait for some ranked CS8 maps to prove that it can work in a way that both benefits mapping freedom and player enjoyment and challenge, then we can consider doing the same for CS9 and maybe CS10.

Personally, I think making at least CS8 rankable would be a positive thing for the community with pretty much no downsides.
Aeonian Sonder
Here's the thing I want to know.
While the rest of the settings like AR and OD have 1-10 settings, why didn't CS get those same settings from the beginning, or at least when someone said "there's only 6 base circle sizes?"
clayton
probably just to limit what were considered extremes at the time. there are ranked maps with CS outside of the range, but most are really old

can't forget this gem beatmapsets/874#osu/6097
[[[[[[
+1
Halfslashed
Personally I think people still can't handle CS above or below 4 very well as a general rule, but there's no real reason to keep restricting things above or below 2-7.
Mister
+1
cant wait for this to be changed
apollodw
+1, player skill will adapt to more precise maps - small circle maps will find their own share of players over time
Astreachan
+1, Did people waited that people were able to read AR10 before ranking them? So why not with CS 0-10?
Dialect
can't wait to get a cs 0 map ranked
DeviousPanda
in regards to this, i feel that CS values from 0-10 could be rankable if it's a core element of the map (so a map made around cs9 that wouldnt work if it was cs7 for example) but at the same time there should be a higher standard in place when using these values, as the ease of execution is alot higher with huge/tiny circle

a good example of a map that uses cs9 as an essential element is beatmapsets/914372#osu/1909836, which by current rules is considered unrankable, but in actuality its a unique challenge coupled with an amazing concept that really deserves to be in the ranked section
Niva

Astreachan wrote:

+1, Did people waited that people were able to read AR10 before ranking them? So why not with CS 0-10?
AR10 has never been unrankable to begin with. The reason why Ranked AR10 maps are rather uncommon compared to other ARs is primarily because there aren't too many maps out there where the AR10 is truly justified in regards to the map's object density and mapping approach (more often than not AR9.x should suffice).

Either way, I have full support for the idea 👍
clayton
this rule debatably already allows you to use CS outside of 2-7, so I think we need to reword it regardless of the CS discussion to get rid of the strange ambiguity of "unintended for each respective game mode"

unless im missing something this is just another way to say:

1. don't make breaks that aren't possible to make in the editor
2. don't use difficulty settings with a value in hundredths place (arguably not "unintended")
3. don't use CS outside of 2-7 (arguably not "unintended")

so I think we should make a rule for 1 and 2, and then scrap the idea behind 3 as most people don't seem to want CS restricted.

https://github.com/ppy/osu-wiki/pull/3588 ?
pishifat
above pr looks okay, i think more could be added though

im seeing lots of posts here about cs higher than 7 being mostly unreasonable to play, but also that it shouldn't be forbidden because tiny circles are useful in a handful of cases

it may help to have something like the last line here in the osu! diff specific rc:


this could allow the cases taht people say necessitate tiny circles, like this one that keeps coming up, while ideally stopping people from doing it for the Lols and making essentially unplayable maps
clayton
seems good, I'll add that

nvm im not cuz none of the diffs have circle size recommendations so far, putting "7 or lower" doesn't really make sense for the lower diffs, and also I'm not gonna make any guesses about what is best for lower diffs in this change. make a new thread about CS guidelines if you want to add this
Please sign in to reply.

New reply