Nah, no changes ;_;
[TimingPoints]D: ?
0,222.222222222222,4,1,1,75,1,0
0,222.222222222222,4,1,1,75,1,0
360,164,8222,2,0,B|328:144|352:88,2,75.0000005960464,0|8|0
Derekku wrote:
XX:XX:XXX (A,B) - The hitburst from A is covering up some of B's repeats. Yes, it's a kick slider, but the repeats should still be visible.
Yes, it's not likely that a player will read a kick slider based on its repeats. However, the hitburst from the previously stacked note is hiding part of the slider, which is unrankable.
I suggest to save AR:9 for [Champion] and use 8 for this one.Plays too slow, i'll keep AR9 in both sorry ><
Add a pause-overlay to avoid skin mixing, please.iF you can make for me that will be great. I'm not able to make it now. I'm not at home
Due to some hidden reverse arrows some repeating sliders might turn out unrankable, mainly these ones: 00:44:444 (1) & 01:15:999 (3,1,2,1). I'm not 100% sure if this diff will get affected even if it's going for approval, you better check those sliders with some BATs.The only way to fix them is just increase a bit spacing between them, that is the onliest way.
IMO the difficulty jump from [Advanced] to [Experienced] is too big.just AR is greater.
And I mean playing it, not by star rating.
Aside that it's a pretty good mapset.
Star~
I am not so agree with using taiko hitsound here, original is still fine.Sorry, but it seems for me good D:
Your message is too short. Please do not post messages like "star", and make sure you are constructively adding to the thread in question.OH GOD WHAT THE HELL IS THIS.
[advanced] and [middling] have duplicated red timing sections.New Ranking Guidelines wrote:
When skinning gameplay elements, complete sets of elements must be skinned. For instance, if you skin hitcircles, you must include a hitcircle.png, hitcircleoverlay.png, approachcircle.png, and a slider border color (this can be done by adding the line "SliderBorder: 255,255,255" (using RGB values) under the [Colours] section of each .osu file). The same logic applies to hitbursts, cursors, numbers, and anything else of this nature. If you didn't intend to skin an element in the set, then using the templateskin's version is okay. Setting a SkinPreference is also acceptable (e.g. forcing the default skin).
Hum?New Ranking Guidelines wrote:
This is a working document. The rules are not going to be strictly enforced yet