Mackenzie wrote:

Requalification Notice

This has been requalified upon request by the mapper within 12 hours after disqualification. Please check the map nicely and then you are free to disqualify it.

###WTF QUALIFY CAP

monstrata wrote:

Doesn't matter if the sampleset/volume is different. A green line will always override a red line so there can be no errors. Green Line > Red Line. Errors only appear when two red lines or two green lines are stacked because osu won't know what information to take. If there are double red lines, osu won't know which red line's information to prioritize, same with double green lines.

For example: if one green line says 40% volume and 1.2x SV multiplier, but another green line says 80% volume and 0.5x SV, the game might produce a section with 80% volume and 1.2x SV because it doesn't know which to prioritize. I'm unsure what occurs when both green lines have the same information, but errors still occur there too.

However in this case, the dq wasn't necessary.

Spaghetti wrote:

Mackenzie wrote:

Requalification Notice

This has been requalified upon request by the mapper within 12 hours after disqualification. Please check the map nicely and then you are free to disqualify it.

###WTF QUALIFY CAP

someone could've used that to qualify it but u wasted it ;-;

monstrata wrote:

Qualify, then post .

baraatje123 wrote:

Spam the qualify button for 10+ minutes until it works
Then Post

monstrata wrote:

Double lines aren't unrankable when it's red + green tho... Only if its double red or double green. Unless of course, the sampleset/volume/SV etc... of the green line used was a mistake...

monstrata wrote:

However in this case, the dq wasn't necessary.

Azer wrote:

02:22:013 (1) - making this slider last so long really hurt the quality of this map, everyone broke on it, it's a huge jump and I personally expected it to be a regular 3 point return slider

Azer wrote:

02:22:013 (1) - making this slider last so long really hurt the quality of this map, everyone broke on it, it's a huge jump and I personally expected it to be a regular 3 point return slider

Fort wrote:

inb4 hvick FC lmao

Azer wrote:

02:22:013 (1) - making this slider last so long really hurt the quality of this map, everyone broke on it, it's a huge jump and I personally expected it to be a regular 3 point return slider

jesus1412 wrote:

02:39:467 (1,2) - Your 1/8 kicksliders feel too long imo with current distancing. You should consider reducing the distance between them and the next jump in a few cases. This happens multiple times in the map, I won't list them all.

Just jesse thoughts. I didn't read anything from the thread before this post but it seems like more people than just me noticed it.

fartownik wrote:

02:31:013 (2,3,4,5) - this is even worse, especially (4) and (5). Big-blackish 1/8 usage.
02:39:467 (1,2) - Same.

Karen wrote:

whats the diff name?
小妹？

fartownik wrote:

Fort wrote:

inb4 hvick FC lmao

and lmao, that's totally FCable every time AFTER you look it up in the editor, but I don't think a map should require you to do that. The mapping of that part is just subpar.

Asphyxia wrote:

Now that this map is disqualified, your first 2 green lines (00:08:922 - and 00:26:376 - ) are unsnapped by 1 ms. You might want to snap them correctly!

Mercurial wrote:

OH GOD, NOT AGAIN, NOT AGAIN THIS QAT BULLCRAP.

At least, this one is well justified though.

Quality Assurance Team wrote:

Disqualification Notice

Hello!

Unfortunately, the Quality Assurance Team has decided to disqualify this beatmap. The following is a list of reasons and examples for the disqualification. We do not outline every issue in detail, so make sure to take the idea behind each reason and apply it to the entire beatmap as issues might be found in more than the spots mentioned below. If you have any questions, please reply to this post and we will do our best to clarify any misunderstandings.

Xiao Mei 2015

Misleading patterns

• 
  There are multiple 1/8 sliders in this map that are very misleading. They are used in a way that players think there is going to be a small break between, yet there's a large jump into the next object instead.

1. 02:22:013 (1,2) -
2. 02:31:013 (2,3) -
3. 02:31:422 (4,5) -
4. 02:39:467 (1,2) -

If you happen to have concerns about this disqualification, you can contest the decision with this form. Before using this form, please read the instructions carefully.

The Beatmap Nominators may handle this mapset after the issues have been addressed.

Good luck!

###M

Hinsvar wrote:

Udah dibilangin ga percaya sih mz hhe

monstrata wrote:

I'm waiting on Fort. Unfortunately Kuron-kun's bubble isn't going to count .

monstrata wrote:

So, due to new BNG rules since we made changes, I need to rebubble...

So this is (re)Bubble #1.


good luck Fort!!

Krfawy wrote:

We managed remove a doubled timing point at 03:45:683 - so now everything should be rankable. Also testplayed the map (with HT ofc) and played nicely.

#2