I dont have any objections with that.
forum
[Rule] Hitcircles must never be hidden under slidertracks
posted
Total Posts
154
That should be good enough to prevent horrible overlaps, with nothing left to the imagination. Please do it.
But if we do that, people will take the guideline as not absolute and thus automatically deny any attempt at bringing up the approach circle issue. At least we have the authority to say it's not allowed with the curent ruleset. If we don't the supporters are going to abuse it and bring up reasons why they can abuse it. Because even one case of approach circle spam is uncalled for in a ranked beatmap and one example isn't considered overdoing it.
I'd make it a heavily enforced guideline, which can only be broken if there is absolutely nowhere else that a circle could go. Given that there's probably always anywhere else to place an object than under a slider track, this should be very easy to enforce.
Topic Starter
Guidelines shouldn't be broken under normal circumstances. You seem to think that guidelines are just throwaway rules that don't affect anyone because they don't matter.
arleady rejected.
This shall go into Recommendation if you want. Not Guidelines
This shall go into Recommendation if you want. Not Guidelines
You never gave any rationale.
Mappers seem to use guidelines as an excuse to weasel out of changing something, before a benevolent BAT lets the mapper keep that something by ranking the map. Sometimes, even MATs or BATs might make unreasonable suggestions, but if it's an issue that is inexcusable or is disagreed with by several people, then there should be a stricter enforcement of the guidelines.ziin wrote:
Guidelines shouldn't be broken under normal circumstances. You seem to think that guidelines are just throwaway rules that don't affect anyone because they don't matter.
Why can't we just adjust the rule to let Hard's do it. I don't think hidden approach circles have any place in Easy/Normal modes. Hards/Insanes could be allowed within reason.
If we allow this to be added in Normals or lower, then it will just further downgrade our standards of what's acceptable. The beatmapper doesn't need to have hard to read transitions in their normal difficulties.
My two cents is that the rule should stay, but the part applying to partially obscure hitcircles should go, because it's vague. We do not have a reference point on what's partially hidden. I think that it should be clarified that a hitcircle that is 80 percent or more hidden under the slider track is unrankable.
If we allow this to be added in Normals or lower, then it will just further downgrade our standards of what's acceptable. The beatmapper doesn't need to have hard to read transitions in their normal difficulties.
My two cents is that the rule should stay, but the part applying to partially obscure hitcircles should go, because it's vague. We do not have a reference point on what's partially hidden. I think that it should be clarified that a hitcircle that is 80 percent or more hidden under the slider track is unrankable.
Topic Starter
TheVileOne wrote:
this needs to be a rule
D33d wrote:
this needs to be a rule
And this is why we can't have nice things. Guideline is middle ground. Deal with it. Or vote that song 1 and move along. It's only a game, folks.HakuNoKaemi wrote:
this shouldn't even be restricted in the slightest
for Guidelines and Rules it should work too right?
It's only a game, folks.being a game do mean rules and guideline are really stupid like this.
You never gave any rationale.Read my older post. It's starting to get me bored saying the same thing over and over.
You mean this?HakuNoKaemi wrote:
1st) I would agree with those as Recommendation, you're pratically using only Guidelines(all guideline in general) that are broken on 99%, of cases without serious problems.
2nd) Nobody noticed the 1st being included in the 2nd guideline
I have no idea what you're trying to say here.
Stacking under sliderends=stacking under objects.1st) I would agree with those as Recommendation, you're pratically using only Guidelines(all guideline in general) that are broken on 99%, of cases without serious problems.mm201 wrote:
Guideline: Avoid stacking things on slider ends in Normal and Easy difficulties. It can be hard for beginners to tell the timing of these objects.
Guideline: Avoid covering up objects too much with hitbursts, slider tracks, and other objects. It's hard to see them if there's too many things happening in one spot.
2nd) Nobody noticed the 1st being included in the 2nd guideline
Plus it isn't something to be completely prohibited.
Add Recommendations, the add something like that (still need grammar corrections)
Avoid covering objects with other objects in easier difficulties. They can result hard to see, especially if overused, examples are long stacks or even stacks not cued to the song or mapping style.
Topic Starter
Guideline 1 covers Normal and Easy. Can be a guideline, easily.
Guideline 2 covers all difficulties. Too vague to be a guideline, too easily broken.
Guideline 2 covers all difficulties. Too vague to be a guideline, too easily broken.
Overlapping isn't vague at all. I could very easily write an aimod module that spots overlaps and categorizes them based on how severe they are.
#2 is also a catch-all for existing rules including hitburst coverage and unseeable slider tracks--things which there are currently RULES against. Downgrading a RULE to a RECOMMENDATION is just excessive.
#2 is also a catch-all for existing rules including hitburst coverage and unseeable slider tracks--things which there are currently RULES against. Downgrading a RULE to a RECOMMENDATION is just excessive.
downgrading a non-wanted heavy rule for most difficulties to a light recommendation for easier diffs is.
Topic Starter
I see #2 as a guideline against tornado combos and stacking objects underneath slider ends, both of which are commonly used and should never be disallowed. If that is not the intention of the guideline, I need and example of what it disallows.mm201 wrote:
Overlapping isn't vague at all. I could very easily write an aimod module that spots overlaps and categorizes them based on how severe they are.
Tornados should be okay. Some clarification might be needed. I don't like going into too much detail because it tends to be off-putting, even if the phrasing is more tolerant.Stacks should be considered separately.
Thank you for being the first person to say anything constructive about this guideline.
Thank you for being the first person to say anything constructive about this guideline.
Depends. It has already been established that having stuff behind slider tracks is perfectly readable and ok to do in higher diffs, it's just that certain individuals dislike to have that. When it becomes unreadable, then it becomes a problem, however that is already caught in the modding process. While readability is subjective, clusterfucks are quite obvious and should be avoided anyway, if anything for cosmetic reasons.mm201 wrote:
Downgrading a RULE to a RECOMMENDATION is just excessive.
Basically what everyone asked here was the rule to be abolished, and instead we're changing it into 2 parts, a guideline and a recommendation, and I see nothing wrong with it.
edit: will throw some examples in a bit.
After-Spinner notes being covered by Spinner theirselves is another example. Antijumps are another example.
Still not constructive?
A better wording could maybe be better, but my idea is to make peoples AVOID using patterns like that randomly( they are good mostly and easy to link to music and graphic cues, as so, it's better to make it a recommendation)
Still not constructive?
A better wording could maybe be better, but my idea is to make peoples AVOID using patterns like that randomly( they are good mostly and easy to link to music and graphic cues, as so, it's better to make it a recommendation)
Okay let's add a condition to the second one, "completely covered up for the majority of the object's lifetime, enough that a reasonable player would have a hard time noticing the existence of the object."
Those examples are fine and shouldn't be included in the guideline, and I never had any intention to include them.
Those examples are fine and shouldn't be included in the guideline, and I never had any intention to include them.
Avoid covering objects with other objects too much especially in easier difficulties. They can result hard to see, especially if overused, examples are long stacks or even stacks not cued to the song or mapping style.Still proposing this as a Recommendation. Added "especially"
No. Covering gameplay elements in easier difficulties shouldn't be done at all, I thought we already came to a conclusion about that. Stacking =/= covering. The only exception I would throw here is having a back and forth pattern, and that would be limited to normal difficulties. Such patterns can be considered both stacking and covering, making it grey area.
"Too much" is subjective. If one is considered a bad case that affects readability then it's an issue. Whether the mapper does it many times or just once, that's irrelevant, also covering objects with objects is too vague. It has to be sliders or hitbursts, because excessive stacks is very vague and should be treat very differently than the other cases Also it's "They can result in hard to see, "especially if overused" < redundant. Also stacks don't often result in hard to see cases.
I don't really think that should even be mentioned. Because it really depends on the song and how far the notes are apart. You couldn't even recommend it for every case. Keep that in mind that recommendations must be made according to all situations or most situations, and stacking anything on anything just doesn't apply in that way IMO.
I don't really think that should even be mentioned. Because it really depends on the song and how far the notes are apart. You couldn't even recommend it for every case. Keep that in mind that recommendations must be made according to all situations or most situations, and stacking anything on anything just doesn't apply in that way IMO.
that part is important, as stacking cued to mapping style (symmetry, pattern similiarity) or music is easier to spot.Avoid covering objects with other objects many times, especially in easier difficulties. They can result hard to see, especially if overused, examples are long stacks or even stacks not cued to the song or mapping style.Still proposing this as a Recommendation. Added "especially"
A Recommendation can be vague, I'm just making one recommendation out of two guideline.
(anyway, corrected one part...)
I'd rather have MM's version than that recommendation Haku...
But that's irrelevant IMO, because I think that this must be said in the rules.
You must never fully obscure a hitcircle under a slider-track in easier difficulties, because the hitcircle will always be obscured until the slider has run it's course, making for hard to read, and ugly situations.
This I think still needs to be a rule, because I can't think of a good reason to have a hitcircle/slider start at the direct middle of a slider track in a Normal. Why should we even allow it? The negatives outweigh the positives, and it would most certainly be a hard element.
But that's irrelevant IMO, because I think that this must be said in the rules.
You must never fully obscure a hitcircle under a slider-track in easier difficulties, because the hitcircle will always be obscured until the slider has run it's course, making for hard to read, and ugly situations.
This I think still needs to be a rule, because I can't think of a good reason to have a hitcircle/slider start at the direct middle of a slider track in a Normal. Why should we even allow it? The negatives outweigh the positives, and it would most certainly be a hard element.
"easier difficulties" do means "normal" too. I would have said "Easy" only.
Well , modders will prevent something that probably have no sense from arriving to the version that'll be controlled by the MATs/BATs.
Well , modders will prevent something that probably have no sense from arriving to the version that'll be controlled by the MATs/BATs.
I had to rush this. It's unorganized. Skip over to my latest version of the guidelines.
SPOILER
Well yeah, but give me/us modders some slack. If it doesn't work in 99 percent of cases, why should us modders have to constantly tell people not to create bad overlaps because it's not against the rules. I mean us modders have to point out ugly overlaps all the time with this rule in place (although objects touching other objects isn't against the rules).
The main issue with this rule is that it's vague, and controversial. The reason it isn't enforcable is because it's these two things. If we adopt what I suggested above, it will give a clear standard that is considered unacceptable.
The rule covers only total obscure patterns, while the guideline would handle partial obscure patterns. I think this should be the correct way to go, because I've seen so many unappealing cases of notes touching other notes in unappealing ways.The modders manage to handle it, but there should be some standard where we can definitively say this isn't allowed. I say this for one very important reason. It will be the mappers who know what they are doing who will be violating the extreme grey areas of these issues, and those will be the hardest to convince to change their patterns, especially if the only reasoning is because it's too unreadable for x difficulty. People don't always change things for that reason.
Edit: Then again... perhaps there are some patterns that could work in a Normal. I may end up suggesting that this end up being a strong guideline. If they took my version instead of the existing one. Mine is clearer on the subject. But then again I'm not sure, it's all depending on the wording.
This is my issue with separating rules from guidelines. When we had everythin as criterias, they could be taken on a case by case basis. If it's a guideline, we can't right off say it's unrankable, because there are cases where it could be rankable. And there is noone other than MAT/BATs that could have the authority to say whether a broken guideline is/is not rankable.
So if we keep it strictly as a rule, then the bad overlaps will be definitively unrankable. But if it's overall playable, then few modders will even mention it. This is how it's always been. This new system will just mess things up.
I have a very large concern about it. There are some exceptions, but there's not enough of a difference between an unacceptable overlap and an acceptable one for most modders to say is rankable or unrankable. There needs to be some clause on unreadability that needs to be met for something to be rankable under this guideline.
We need an addition like : Any exceptions must have a clear, and logical path, that is not obscured by any hitburst.
Stacks should also be unrankable while obscured under a slider track.
I'll try to edit my version to cover more issues, but I don't think I have time right now.
Edit: I'll make one last note before someone tells me that is subjective. It needs to be!!! There is nothing wrong with saying "I think this is unrankable." NOTHING! It is in our opinion that this pattern violates a guideline/rule, regardless if it absolutely violates it. Some unrankable cases have to be on a case by case basis, and this is definitely one of those cases. It must be stated that subjective criteria must be met in order for this rule or guideline to be enforcable, otherwise it wont be for 98 percent of modders.
I may make a whole thread based off of subjectivity. Because it makes sense that all things subjective; that we are not adding to the rules, cannot be enforced by the modders, because we wont include subjective criteria in the rules/guidelines for it.
The main issue with this rule is that it's vague, and controversial. The reason it isn't enforcable is because it's these two things. If we adopt what I suggested above, it will give a clear standard that is considered unacceptable.
Edit: Then again... perhaps there are some patterns that could work in a Normal. I may end up suggesting that this end up being a strong guideline. If they took my version instead of the existing one. Mine is clearer on the subject. But then again I'm not sure, it's all depending on the wording.
This is my issue with separating rules from guidelines. When we had everythin as criterias, they could be taken on a case by case basis. If it's a guideline, we can't right off say it's unrankable, because there are cases where it could be rankable. And there is noone other than MAT/BATs that could have the authority to say whether a broken guideline is/is not rankable.
So if we keep it strictly as a rule, then the bad overlaps will be definitively unrankable. But if it's overall playable, then few modders will even mention it. This is how it's always been. This new system will just mess things up.
I have a very large concern about it. There are some exceptions, but there's not enough of a difference between an unacceptable overlap and an acceptable one for most modders to say is rankable or unrankable. There needs to be some clause on unreadability that needs to be met for something to be rankable under this guideline.
We need an addition like : Any exceptions must have a clear, and logical path, that is not obscured by any hitburst.
Stacks should also be unrankable while obscured under a slider track.
I'll try to edit my version to cover more issues, but I don't think I have time right now.
Edit: I'll make one last note before someone tells me that is subjective. It needs to be!!! There is nothing wrong with saying "I think this is unrankable." NOTHING! It is in our opinion that this pattern violates a guideline/rule, regardless if it absolutely violates it. Some unrankable cases have to be on a case by case basis, and this is definitely one of those cases. It must be stated that subjective criteria must be met in order for this rule or guideline to be enforcable, otherwise it wont be for 98 percent of modders.
I may make a whole thread based off of subjectivity. Because it makes sense that all things subjective; that we are not adding to the rules, cannot be enforced by the modders, because we wont include subjective criteria in the rules/guidelines for it.
I said sometimes that something that need to be considered case-by-case isn't worth a rules many times actually-
Anyway we don't need to cater rules to modding
example of a normal usable pattern that will be banned by that if it'll be a guideline...
My whole point is limiting this to a recommendation at max, or even deleting it...
Anyway we don't need to cater rules to modding
example of a normal usable pattern that will be banned by that if it'll be a guideline...
My whole point is limiting this to a recommendation at max, or even deleting it...
Edit: Here is my current version. Please consider this instead. I have included a way to make this enforceable as a guideline and will allow less extreme overlap cases to be allowable.
[Guideline] You should avoid partially or fully obscuring a hitcircle under a slider-track in easier difficulties, because the hitcircle will always be obscured until the slider has run it's course, making for hard to read, and ugly situations. Any exceptions must have a clear and logical path, that is not obscured by any hitburst.
[Guideline] You should avoid partially or fully obscuring a hitcircle under a slider-track in easier difficulties, because the hitcircle will always be obscured until the slider has run it's course, making for hard to read, and ugly situations. Any exceptions must have a clear and logical path, that is not obscured by any hitburst.
Good as a guideline now
Agreeing, other people can control it?
Topic Starter
Original:
mm201:
First guideline addresses stacking slider ends in normal/easy, where it is pretty much universally accepted. Second guideline makes sure that overlaps are not complete overlaps if possible, but anyone with a brain can understand that stacked objects do not count, and haku's examples are fine depending on the difficulty.
Hitcircles must never be hidden under slidertracks. Whether a hitcircle is partially or completely under a slidertrack, it is confusing for the player to read. Insane difficulties are the only exception to this rule.
mm201:
Guideline: Avoid stacking things on slider ends in Normal and Easy difficulties. It can be hard for beginners to tell the timing of these objects.
Guideline: Avoid covering up objects too much with hitbursts, slider tracks, and other objects. It's hard to see them if there's too many things happening in one spot.
First guideline addresses stacking slider ends in normal/easy, where it is pretty much universally accepted. Second guideline makes sure that overlaps are not complete overlaps if possible, but anyone with a brain can understand that stacked objects do not count, and haku's examples are fine depending on the difficulty.
continuing?
Slider-end stacks are completely playable in less than 2 days, or even while they start. I can see you can discourage MASS stacking in EASY, not in NORMAL, (MASS Stacking).
Universally accepted? even peoples that plays from a few days say they're easy-to-learn ( the only prerequisite is knowing "osu! IS a Rhythmn game" )
(And guideline is a serious overkill, as the sliderend-stack learning time is completely subjective (vary from person to person )
Avoid placing to many objects near one place? But even: if there will be too many objects in the same place the AR will take care of it and make it playable. More extreme cases are too ugly, rarely used and every-time discouraged by modders.
Slider-end stacks are completely playable in less than 2 days, or even while they start. I can see you can discourage MASS stacking in EASY, not in NORMAL, (MASS Stacking).
Universally accepted? even peoples that plays from a few days say they're easy-to-learn ( the only prerequisite is knowing "osu! IS a Rhythmn game" )
(And guideline is a serious overkill, as the sliderend-stack learning time is completely subjective (vary from person to person )
Avoid placing to many objects near one place? But even: if there will be too many objects in the same place the AR will take care of it and make it playable. More extreme cases are too ugly, rarely used and every-time discouraged by modders.
HD is about memorization, but real HD players make "guessing" hits at some positions when they think an object coulb be hidden behind. I think this is a part of the player ability to play HD on standard.
HD isn't about memorization, FL IS, HD need a good path reading capacity and is more based around you knowing when to hit.
Plus the AR unexpectedly help when too many objects are stacked around the same point, so... yeah the 2nd guideline is to delete
The 1st guideline is actually not generally accepted. You can actually use stacking in Normal freely ( Normal player have played for some days ), Easy players/Beginners have different learning rates, but they easily learn how to play sliderend stacking, and if they can't play them, they usually can't play easies well because they almost started. Deleting seems a good idea.
Plus the AR unexpectedly help when too many objects are stacked around the same point, so... yeah the 2nd guideline is to delete
The 1st guideline is actually not generally accepted. You can actually use stacking in Normal freely ( Normal player have played for some days ), Easy players/Beginners have different learning rates, but they easily learn how to play sliderend stacking, and if they can't play them, they usually can't play easies well because they almost started. Deleting seems a good idea.
If HD was about memorization i wouldn't be able to FC maps with HD on first try.Drafura wrote:
HD is about memorization, but real HD players make "guessing" hits at some positions when they think an object coulb be hidden behind. I think this is a part of the player ability to play HD on standard.
You have some maps wich requires a bit memorization. Don't extend my words to a general view. Of course this isn't like FL but sometimes it's easier to FC HD memorizing some hidden circles. I mean in this mod this is the only hard thing, well some jumpy patterns with only circles could be a bit hard but I don't think this is the hardest stuff for a HD player.Sakura Hana wrote:
If HD was about memorization i wouldn't be able to FC maps with HD on first try.Drafura wrote:
HD is about memorization, but real HD players make "guessing" hits at some positions when they think an object coulb be hidden behind. I think this is a part of the player ability to play HD on standard.
If you take a look to tops, the maps with those hidden circles are the one wich aren't full of HD top40. That's why i said memory is a part of HD skill. But of course HD is also about accu skill (no approach circles) and other...
I was just pointing that /me leaves
HD need pre-pathreading. Means you should see when circles appear, not that you won't do it while playing without HD, and you can use your intuition to know when to click.
agreed! it must be on right direction...eventhough some of it used it...just minimized on using,,,
My bad, sorry about this :s
Drafura take this from an HD player, it is not about memorization. What makes HD worthy of being a mod is the difficulty in snapping to/aiming at each note. I could give you a few examples of maps like this if you'd like to try and prove me wrong.
Topic Starter
HD is all about memorization when hitcircles are underneath other objects, though I guess that wasn't what you were talking about. I usually have to memorize those notes on standard.
No, I agree with Yoda. Hidden makes jumps much more difficult. I guess it goes back to the "eyes on the prize" thing in how aiming jumps is easier when you can see the target.
Memorization does become a problem in poorly designed maps.
Memorization does become a problem in poorly designed maps.
mm201 read my mind and spat out the words <3
Edit: To add to mm201's poorly designed maps: If HD was about memorization, then it would be impossible to 1 shot DT HDs, and I have done so several times now. However, poorly designed maps... not so much.
Edit: To add to mm201's poorly designed maps: If HD was about memorization, then it would be impossible to 1 shot DT HDs, and I have done so several times now. However, poorly designed maps... not so much.
Just wanna point out that the Insane difficulty of this song http://osu.ppy.sh/s/46574 breaks this rule every 2 seconds.
But no one cares because it's Mafiamaster weeeeeeeeee!
But no one cares because it's Mafiamaster weeeeeeeeee!
Mercurial
It was discussed to be deleted directly, so I guess no one has cared about.Zetta wrote:
Just wanna point out that the Insane difficulty of this song http://osu.ppy.sh/s/46574 breaks this rule every 2 seconds.
But no one cares because it's Mafiamaster weeeeeeeeee!
Ah, Stacking shall be permitted in easier diffs.
The player usually won't fail on clicking stacked note if he can complete a standard easy and he can quite play it as not being able to play it will mean the note is offbeat.
By the way the other reason is Are you sure to make stack be used from hard onward?, you really assign them that much difficulty?
Obviously, "Avoid covering objects with slidertracks or with a group of hitcircles in easier difficulties" shall be a good guideline.
Differently, "Avoid stacking on easier difficulties" is not.
Topic Starter
Except it doesn't.Zetta wrote:
Just wanna point out that the Insane difficulty of this song http://osu.ppy.sh/s/46574 breaks this rule every 2 seconds.
But no one cares because it's Mafiamaster weeeeeeeeee!
A) it's a bad rule
B) it hasn't been replaced/fixed officially
C) the stacking, while stupid and idiotic, has fans for reasons beyond my capability of understanding
D) the stacking is done in a consistent, logical, and simple manner.
E) it's not stacking circles.
F) it's insane
After further discussion in #modhelp we've decided to leave this rule as is.