the reason is that new maps are still getting unranked over this rule
If you're going to make a rule about this then you should realize that the whole quality criteria (which is imo where colours would fit) needs strict guidelines. It would make mappers' lives a hell of a lot easier.tiper wrote:
the reason is that new maps are still getting unranked over this rule
I'm done here. Talking with staff of their mistakes gets you nowhere. Let's just make this rule well-looking.
1) White combo colours, as Zare said, cause bad kiai strobing on some skins. I'd not use "pure white" as definition, because #FFFFFE colour is, nominally, not "pure", but still does the same thing.
2) Pure black combo colour makes hitobjects invisible with 100% dim (and default skin).
Agreed. So many more maps have been targeted due to quality issues that are NOT colours, be it sliders or whatever.tiper wrote:
Let's make it the main point of the thread.Yuzu- wrote:
the whole quality criteria (which is imo where colours would fit) needs strict guidelines.
if the map is intended to play with background then why add a dim option?TheVileOne wrote:
I will argue that playing with 100% dim is not the way the game was intended to be played by peppy. We don't conform mapping standards to whether or not people will be playing with the background visible. It is fully intended to be played with the background. If you choose to dim it, then you will need to solve the issue of blending yourself.
True. But the reality is that peppy had to do that. As a game developer, he couldn't disrespect the countless amount of players who wanted to play without backrounds. Why would you disrespect them now?TheVileOne wrote:
Dim was added to stop people from deleting backgrounds. peppy doesn't want you to use it.
people deleted backgrounds to have a pitch black background. Adding dim merely stopped them from doing so, while still providing them with a way to do so.TheVileOne wrote:
Dim was added to stop people from deleting backgrounds. peppy doesn't want you to use it.
Providing it with a way doesn't sound help.Yuzu- wrote:
while still providing them with a way to do so
We're past the combo colors from my point of view. We're not just talking about those, the thing in discussion atm is that "Quality Standards" need to be set straight. It's not supposed to be a rule, it's a guideline because it's NOT in the ranking criteria. It's up to whoever's qualified to decide if the map meets or not the quality standards. The issue here is that you can't find them anywhere atm, and we need a list for this.TheVileOne wrote:
This should not become an official rule until the team comes up with a consensus on whether it should be allowed or disallowed. In my long career of being a modder, which probably predates Alexs BTW I have not heard of this rule. I have not seen any other BATs or modders mention it and it should have been a written rule years ago if it was an actual rule.
I disagree that any condition that changes the original appearance of the beatmap should be considered as part of any mapping rule.
I've heard once that pure black combo colour is not suggested to use. There was a NTR's (not sure about the mapper, though) beatmap and a shitload of whine about it being unplayable without background.TheVileOne wrote:
I have not seen any other BATs or modders mention it and it should have been a written rule years ago if it was an actual rule.
This could be arguable, but in most cases yes, you're right about this.TheVileOne wrote:
slider ticks do not make a large impact on playability.
Approach circles are almost invisible.DakeDekaane wrote:
tbh I don't see black causing many troubles with default settings as white (if it causes any), so I don't think we should take them into consideration.
Why can't the Ranking Criteria benefit the large portion of players who play 100% dim? I personally feel like black doesn't fit in most cases anyway so yeahZare wrote:
100% is not a default option. If you dim, you do it at your own risk and if needed, should also disable beatmap skin and thus the combo colors.
Competitive>casual, regardless of majority/minority. Where do you think money/donations comes from?Zare wrote:
"large portion"
you mean the 5k players that do it as opposed to the 100k~ casuals that dont? ever heard of the term "vocal minority"?
anyway, this isn't the point, people who dim dont have an issue with disabling map skin (or shouldnt at least, since it wouldnt make any sense to complain, the combo colours are chosen to fit the BG anyway), thus black colors do not affect anyone badly. disallowing them just for that doesnt make sense whatsoever.
I agree on this. Should need rewrite of Zare's rule.those wrote:
On the contrary, making this a rule would allow #FFFFFE or #100000 as a valid combo colour. It should be most effective if the rule included terms "sufficiently non-white and non-black", instead of setting numerical values or using vague colouring.
This. If the mapper doesn't use kiai at all, this rule will be invalidity nevertheless the mapper can't use white.TheVileOne wrote:
Loctav, white during non kiai fountain sections. The guideline would only exist for kiai related things.
Can you give me an example skin?tiper wrote:
It doesn't mean other skins do not cause stobing-related issues during kiai sections.Granger wrote:
I dont see any issues with white... my skin makes all combos white if i disable the beatmap skin and i never ran into any issues related to stobing. Black combo colors on the other hand...
DefaultGranger wrote:
Can you give me an example skin?
Then I can use 254,254,254 or 1,1,1 right (?).Zare wrote:
Do not use pure white (RGB code 255,255,255) or black (RGB code 0,0,0) combo colors. This is to prevent technical issues with some skins as well as strobing within kiai times, and can also help to prevent the hitobjects blending with the (dimmed) background.