Imo should be more of common sense thing. White combo color on black bg is fine and vice versa.
This. This isn't only black/white but also how xxdeathx said dark blue as example can be really hard to read with a bad background contrast. No need for a rule, just mention to use no distracting Combo colours with backgrounds. If they plays bad tell them to change, if not it gets nuked somewhen and we're happy.Raging Bull wrote:
Imo should be more of common sense thing. White combo color on black bg is fine and vice versa.
Do not use pure white combo color (255,255,255); it makes Kiai blinding and hurts the eyes.It's true that it has been an old non-written rule... But having it as an official one? That's one of the parameters that falls under the common sense of the mapper and therefore it should be a guideline if you want.
That's basically really really bad when nobody notices that through the modding process and really shouldn't happen. How said, common sense prevents such unqualifies and black/white doesn't need to be unrankable. Adding as guideline instead is way better.Zare wrote:
The thing is that maps are getting unranked over this, I just want something to refer to when that happens so mappers as well as modders can read it up in the RC.
Using that logic, forcing their own combo colors should not be used as an argument since it is not a default setting (maybe it is, correct me if I'm wrong). Combo coloring is meant to provide not only a means to replenish HP but to give an intended experience from the mapper to the player as well. The colors that are on the polar ends of the spectrum make it harder for players to enjoy the mapset to its fullest. In any case, this is really a minor thing - I would suggest making this a guideline as opposed to a rule instead. BAT members can take it on a case by case basis (if its playable and lools fine on the map then leave the colors) and if there is an issue the QAT can handle it.Garven wrote:
Dim isn't a default setting. It's an option. Dark combo colors are only an issue if they blend too much into the chosen background.
Scenario AStefan wrote:
That's basically really really bad when nobody notices that through the modding process and really shouldn't happen. How said, common sense prevents such unqualifies and black/white doesn't need to be unrankable. Adding as guideline instead is way better.Zare wrote:
The thing is that maps are getting unranked over this, I just want something to refer to when that happens so mappers as well as modders can read it up in the RC.
That hypothetical limitation shall only be used in standard, whilst in CtB the white combo colour is the most preferred option (via skinning) for most of the elite players. Also, even having the overlay of the default skin (which is black), there should be enough contrast to read this colour properly, and therefore it shouldn't be applied any limitation of that regard.Garven wrote:
Unless there are other angles presented, the only absolute I'm seeing here is against the white combo color, in which there is an option to circumvent the problem and continue using it.
This falls under the section quality. And if named mapper rejects to improve his map and to fix this debacle then I see no reason to rank the map because of stubbornness.Zare wrote:
Scenario A
"Hey mapper, can you please change your combo colors? These RGB codes aren't allowed!"
"Hey modder, no i won't change this, I can't see a rule that says so!"
This is a awful example. However it says guidelines CAN be broken in special cases and this one would be a case to not break.Zare wrote:
Scenario B
"It's a guideline!"
"There's also a guideline that states to not map songs that are longer than 3 minutes, they're not exactly up-to date or in any way relevant."
Yes that could happens. And we have guidelines for that. At the end it's still the logic behind the question to use 0,0,0 as Combo colour in a beatmap which is completely black or not.Zare wrote:
Scenario C
"Hi I'm a BAT that joined osu! a year ago, I'm ranking this map as it complies with the RC perfectly!"
"Hi I'm the QAT and neither the mapper nor the modders or BATs can be expected to know about this, but this is unrankable and I will need to unrank this map which causes additional unneeded work and stress for everyone!"
That's almost the same as saying that really hard maps would be unrankable since there's only a vocal minority that can play it and actually enjoy it.Shiro wrote:
Yes, there are ways to circumvent this, but only a select portion of the playerbase uses the visual settings, and we should not accept to impair the experience of those who wish to enjoy the game without that panel based on the argument that a vocal minority uses it. That would be the same as disallowing backgrounds, storyboards or hitsounds based on the fact that a certain number of people choose to always ignore them.
That's exactly what I was saying. Re-read my post.Ayu wrote:
That's almost the same as saying that really hard maps would be unrankable since there's only a vocal minority that can play it and actually enjoy it.Shiro wrote:
Yes, there are ways to circumvent this, but only a select portion of the playerbase uses the visual settings, and we should not accept to impair the experience of those who wish to enjoy the game without that panel based on the argument that a vocal minority uses it. That would be the same as disallowing backgrounds, storyboards or hitsounds based on the fact that a certain number of people choose to always ignore them.
I'm just saying, this is a community so you should also think about that vocal minority. You should think about EVERYBODY. It's wrong to just keep their opinions out just because it's not ethical for you.
exactly my pointtiper wrote:
Why do you even discuss the rule that is in force, even though it, for some reasons which I do not understand, wasn't written down in [[RC]] yet? If QATs unrank maps because of black/white combo colors, the rule must be written down. As we can see, they do. That's all.
We don't discuss whether it makes sense. This rule is just not written down in the ranking criterias, but it was in force for years. According to this post, "pure black and white combo colors are forbidden", which, as it's marked red, also was the main reason to unrank the beatmap. I don't understand why anyone would have wanted to keep this rule unwritten.Kibbleru wrote:
i also see absolutely no reason for a player to decline something as simple as changing the combo colors.
Because rules needs to be followed to 100% while guidelines can be ignored if reasoned. And the map is an example of bad usage.tiper wrote:
I don't understand why anyone would have wanted to keep this rule unwritten.
You either can use them, or you can't. Pick one. There is only "use them if you want, and your map WILL get unqualified, as good usage is "subjective" so fuck you" currently.Stefan wrote:
Because rules needs to be followed to 100% while guidelines can be ignored if reasoned. And the map is an example of bad usage.tiper wrote:
I don't understand why anyone would have wanted to keep this rule unwritten.
1) It does make sense.TheVileOne wrote:
This rule sounds like nonsense to me
It seems like I need to say it one more time: there's a beatmap that got disqualified because of pure white combo color. They said, "pure black and white combo colors are forbidden". From then on, you can't call it "a guideline".TheVileOne wrote:
If anything it should be a guideline.
Avoid using pure white as a combo colour as it makes slider ticks hidden while using default skin.
Ask another QATs. They unrank beatmaps pointing pure white and black combo colors as the main reason. I'm sure they can list reasons.Garven wrote:
Why does it make sense?
Beatmap got disqualified because of "absolutely nothing"? Well done, then. Keep on showing nice attitude towards the community.Garven wrote:
contributing absolutely nothing to the discussion
this rule goes from old 2008 or 2009.I can't believe that a BAT with ~1800 kudosu never heard about it.
Should we mention all rules like "don't put objects out of screen", "don't make 300 hitburst look like 100" etcYes, we should. This one is odd and not obvious for newbie mappers.
Should we mention all rules like "don't put objects out of screen", "don't make 300 hitburst look like 100" etcThose are actual written rules.
the reason is that new maps are still getting unranked over this rule