1. 00:55:867 (6) - For the most part you use an additional sample with the piano so there is more impact on it, but here you didn't do so, making this note essentially inaudible and have no actual feedback. This issue reoccurs VERY often in the map but I won't point all instances.
2. 01:21:442 (1,2,3,4,1,2,3,4,1,2,3,4,1,2,3,4,1) - This is a bit odd to play, the jumps don't feel so natural since the flow is linear, making the way you aim your mouse/pen really strange considering the flow is the same but you need to keep changing speed constantly while streaming, Also, nothing in the song justifies these jumps, I'd suggest you to just make a constant stream here. Also, the interaction between these 01:22:642 (1) - Feels a bit wrong considering the fact that you need to suddenly move REALLY slowly even though the flow doesn't break or anything like that, making it very likely that a person will play as if the slider is much faster.
3. 02:52:492 (15) - This slider leads the player towards the wrong direction, whether you use it as a circular motion based thing 02:51:292 (15) - or just linear flow, it doesn't work at both ways, i'd suggest you make this slider point towards the next stream. This issue reoccurs often in the map but I won't point all instances.
4. 02:54:142 (5) - I can't find any reason to break the flow here, this is a consistent sound and it only breaks at 02:54:442 (9) - if anything.
5. 03:08:317 (2) - 03:14:992 (11) - More instances of unjustified flow breaks.
6. 03:21:442 (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16) - Let alone the hitsounding issues I have pointed previously which makes this a bit awkward as for feedback, I'm not sure a stream such as this will fit here. First thing, it's followed by a very slow slider, making it a bit awkward to control when it comes to your movement. Second thing, at this intensity and bpm, a stream that spaces so hard could be a bit of an overkill. I'd recommend you to make a slider pattern, maybe such as this one: https://osu.ppy.sh/ss/5309879
7. 04:02:542 (5) - As pointed on the post above me, this isn't comfortable to play.
8. 04:09:442 (1,2) - This turn doesn't make sense to me, Why'd you put it on the blue tick anyways?
9. 04:38:242 (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16) - Yet again, I'm not sure if SUCH intense pattern would work and play well, I'd suggest a slider pattern here too.
10. 04:58:624 (11,12,13,14,1) - Controversial, but I guess it makes sense.
11. 05:00:730 - A spinner (Which is an intense and rapid motion) doesn't fit a really soothing fadeout, Maybe instead put a slow slider (As I can see you don't have a problem with these) that ends at 05:04:315 - ?

TheArchist wrote:

Xexxar wrote:

ar10 = vomit

no idea why this was chosen...

lower ar's would play much better... as is you have no vision of whats coming so you cant prepare your fingers at all, puts an unneeded amount of focus in reading effort and reaction speed rather than the streaming part. huge disappointment for me cause now I basically have to memorize this to be able to play it well.

Are you... serious right now?

This is a song with 200 bpm spaced streams, which get very extremely difficult to read on lower ARs. There are plenty of cases where songs should be at lower ARs when they should, but this is not one of them.

SnowNiNo_ wrote:

awww DQ, sad ;w;

Okorin wrote:

see ya in 2017?

wendao wrote:

http://puu.sh/pgtST.zip imho it's pretty much better to include default hitnormal than not

Kroytz wrote:

sb coming in

Nozhomi wrote:

Kroytz wrote:

sb coming in

rip XD

1. soft-sliderslide42 has been removed because as Yuii- mentioned, it was a tiny error leaving that one in when completely unused. Now the mapset has an extra 44 bytes to use :3
   
2. 00:05:842 (1) - to 00:22:642 (1) - have been remapped to have cleaner more structured sliders. SV changes were upped a bit and slidertick volumes went down a bit.
   
3. 00:42:592 (1) - Xexxar did some reddit-level math and found that this absolutely 100% needed to be rotated by 3 degrees.
   
4. 02:00:123 (1,2,3,4,5) - The snapping has been "fixed" here. With the help of Charles, Xexxar, and a good 1-2 hours of our time, we managed to find a good spot for these notes. Basically we slid them over by 2/16 and somehow it works.
   
5. 02:33:442 (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,1) - Has been changed to make an accent on the (9). credits to mithew for finding this.
   
6. 02:39:742 (3) - slider-end volume reduced to 40% because the hitsound was quite loud there.
   
7. 04:53:866 (1) - Fixed a bit of the curve on this.

Yuii- wrote:

Why hello there

You are ruining CtB, koliron!!!!!!
Someone stop this map from getting played. This is a pp map!!!!!

Jesus. Since when a pp map is bad? If a map gives a shit ton of performance points means the map should not be ranked because it's bad? I blame a lot of people who actually started talking about this, seriously.

randomizer89 wrote:

if map get tooo many pp... it's system problem of pp, not map problem.

Nelly wrote:

I have no clue whats wrong with BNs heads but right now AR 10 on 7 star maps its NORMAL (even 8 star maps)

Nozhomi wrote:

Tbh I think AR10 is k, since the rhythm is sometimes tricky (as start for example) and the object density is way enough high to keep it.
I have no more conplain with the map. Fixes looks k.

Let's try again ?

Asphyxia wrote:

Disqualified on mappers' request, there will be a storyboard.

Nelly wrote:

Disqualified on mappers' request, there will be a storyboard.

Nelly wrote:

Disqualified on mappers' request, there will be a storyboard.

Kroytz wrote:

Shiguma wrote:

But why does this have to be identical to Blue Xenith? 9.5-10 range works, I would expect someone playing this to be able to read ar10

Kroytz wrote:

@Xexxar: Stop crying and l2p AR10. Your attitude towards me about the AR has been nothing but whining. If the BPM is the deciding factor as to what determines a map's AR, then that's quite a poor argument considering there are a couple of "low-bpm" maps utilizing AR10. If your next argument is,"Oh but those maps are mapped in 1/3 hurr hurr so it's technically 200+bpm" then surely it's not the bpm of the song but the way in which its mapped. The map is perfectly readable at lower ARs, and the map is perfectly readable at AR 10, your argument is just as subjective as the players who are able to read 10.

Yuii- wrote:

Don't worry, I always backup hitsounds.

soft-sliderslide42.wav in case you need it: http://puu.sh/phgkr/13b04ac5fd.wav

Battle wrote:

nelly post near nely wao

gz

Nelly wrote:

Battle wrote:

nelly post near nely wao

gz

What

Fezu wrote:

What the staff should do right now is include a rule that all maps over 5 minutes long needs a storyboard. :^)

Fezu wrote:

What the staff should do right now is include a rule that all maps over 5 minutes long needs a storyboard. :^)

Enon wrote:

i hope no more complains

ComfyWolf wrote:

Glad to see this back. I was about to jump in and just storyboard for you since it seemed like you were taking forever to wait for Cl8n (or whoever took over I don't remember).

Disqualified on mappers' request, there will be a storyboard.

Asphyxia wrote:

Disqualified on mappers' request, there will be a storyboard.

Battle wrote:

nelly post near nely wao

gz

Kroytz wrote:

@Xexxar: Stop crying and l2p AR10. Your attitude towards me about the AR has been nothing but whining. If the BPM is the deciding factor as to what determines a map's AR, then that's quite a poor argument considering there are a couple of "low-bpm" maps utilizing AR10. If your next argument is,"Oh but those maps are mapped in 1/3 hurr hurr so it's technically 200+bpm" then surely it's not the bpm of the song but the way in which its mapped. The map is perfectly readable at lower ARs, and the map is perfectly readable at AR 10, your argument is just as subjective as the players who are able to read 10.

@to everyone else: This is sort of how it looked like before, during the time it was qualified in November: with a few agreements/disagreements on the AR. The only difference is simply due to the fact that it would've been ranked with AR10, and have been accepted perfectly fine without complaints had I not DQ'd. Not to say "I could've gone away with it then" but what I'm saying follows more along the lines of, "it was perfectly acceptable then, and there's no reason why it shouldn't be acceptable now". For what it seems like, it's that everyone just has their preference as to what is "optimal" and that will be an opinion that varies from player-to-player or mapper-to-mapper.

Kroytz wrote:

Look, I'm not sure who's been here the first time it was qualified to where it is now but the time it was first qualified (circa November 2015) the general consensus among the majority of players/spectators/mappers during that time was that a higher AR (higher in this sense would be above 9.5) is best suited in this case as to prevent clutter on the screen. So that gives us a few numbers to work with right; AR 9.5 is the slow end of the optimal AR spectrum and 10 would be the fastest end of it.
Now I've talked to many players ranging from single digits to 5 digits and received a lot of feedback regarding the AR and (un)surprisingly, the optimal AR varied completely. Some users within the top 100 couldn't even read AR10 whereas 4-5 digit players could. Somehow, top players couldn't even get through the first minute of the map (yet they can HDDT 10.3 maps with 99%+ amirite). From the many playtesters, I've only received about a dozen comments regarding the AR. A good half stating the higher AR feels good and the other half saying otherwise, maybe tone it down .2. or .3. But I feel as though the optimal AR for this particular map in its difficulty range is so subjective that it comes down to whether or not you're capable of reading it to begin with. If you can deathstream 200 bpm for 5 minutes straight, reading AR10 shouldn't be a problem.

Kroytz wrote:

OD 10 is too OP for me to use. OD9 is good enough to prevent note locking a lot. Anything lower, you'd get the whole x1 miss and you die Freedom Dive thing.