Shulin wrote:
General:
-- The timing is different on every difficulty make sure you fix this, a timing has already been provided so use that on all difficulties for now. Fixed. My math was wrong on several of them.
Normal:
-- Make sure it's correctly snapped.
-- Use a consistent distance snap.
That really is all I can add atm, the timing needs to be the same also so you can make sure it's snapped correctly etc etc.
Hard:
-- Similar snapping issues to Insane. I don't have the time to point them all out, but take examples from the mod on that diff.
01:12:486 (3,1) - Spacing, too far. I've been meaning to fix this. Thanks for pointing this out for me.
01:26:594 (1,2,3,4,5,6) - With so much overlapping it's hard to see what is going on. I like this though. It's a fun feature that only takes one go through to learn. If you don't get the pattern the first time, you'll know the pattern the second time around. IMO it's a lot better than some patterns I've seen on recently ranked maps.
02:06:901 (1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3,1,2,3) - Confusing. The alternative is unstacking them. I might doi that with a higher distance snap.
02:16:007 (3,1) - Spacing, too far. Will be fixed with a higher distance snap.
02:16:374 (3,1) - ^
02:16:740 (3,1) - ^
02:20:512 (3,4,5,6,7) - Barely visible. Will be fixed with the higher snap.
02:57:392 (1,2,3,4,5,6,7,8,9,10,11,12) - Imo you shouldn't space streams like this, hard to play and not very fun. Will be fixed with the higher snap
The main issue here is snapping again, but also the overall distance snap is low... I recommend increasing it so 1/2s aren't so close. It's hard to play when the spacing is so cramped tbh.
Insane:
-- A lot of notes are snapped incorrectly which means I can't test to timing thoroughly.
-- Generally I think a 1/2 snap works the majority of the time.
00:15:792 (3) - Move to white tick at 00:15:859
00:16:388 (4) - Move to red tick at 00:16:455
00:18:971 (3) - Move to white tick at 00:19:037
00:19:567 (4) - Move to red tick at 00:19:633
00:20:229 (6) - Add a return.
00:22:712 (3) - Move to red tick at 00:22:777
00:25:244 (3) - Move to white tick at 00:25:309
00:26:218 (5) - Move to 00:26:283
00:26:478 (6) - End at the white tick.
00:29:461 (3,1) - Spacing. I see where the pattern was going but the jump is kinda unexpected.
00:50:274 (3) - Move to white tick 00:50:339
00:50:862 (1) - Red tick 00:50:927
00:51:254 (2) - Red tick 00:51:319
00:52:234 (5) - Move to white tick 00:52:300
00:53:811 (2) - To 00:53:877
00:54:008 (3) - To 00:54:074
00:54:271 (4,1,2,3) - 1/2.
00:55:839 (1) - End on red tick 00:57:580
00:58:742 (1,1) - Huge jump, tone it down a little.
00:58:871 (1) - Move this so it syncs to the bpm change at 00:58:945
01:04:804 (1,1) - 1/2.
01:06:025 (1,2,3,4) - ^ ~ I'll stop pointing out snapping now I think I've given enough examples.
01:11:084 (1,1) - Jump like this is too far.
01:18:788 (1) - Move to 01:18:852
01:30:311 (2,1,2,1,2,1,2,1,2,1,2,1) - The way you've positioned these is awkward to play, especially after the end of the slider.
01:41:288 (1) - The spinner is unrankable, must get at least 2000 in auto.
01:45:769 (1) - ^
01:47:262 (1) - ^
01:48:886 (1) - ^
02:06:901 (1,2,3,4,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,3,4,5,1,2,3) - For this whole section the rhythm isn't really evident, and the spacing doesn't help either.
02:15:763 (1,2,3,4,5,6,7,1,2,3,4,5,6,7,8) - This stream is really awkward to play.
02:17:778 (4,1) - Spacing, too close.
02:18:267 (2,3) - ^ too far.
02:20:390 (2,3,4,5,6,7) - Confusing.
There is a lot to do here, imo you should remap this. Then keep testing, testing, testing and playing until it plays well.
On a side note, this song will be difficult to map. I wouldn't recommend it for a new mapper, personally. Maybe that's just my opinion, but with the bpm changes and weird rhythm it will take a LOT of work to get this right.
i'll finish this post when I fix insane mode.