behind you :: FFR Batch Submission
QwertyVibin - behind you - Akimalo [7.5 / 10]
Winter 2022 Seasonal Batch
PublicTokenPurchasedSecretEvents
Rejected
https://www.flashflashrevolution.com/vbz/showpost.php?p=4782258&postcount=384

Simfile Folder Name

behind you (QwertyVibin)

Note Count

794

Chart Length

1:19

Average NPS

10.3565

Estimated Difficulty

68.77

First Note

0:03

Ending Note Delay

0:01

Hand Bias

x -12

Framers

0 - 0 1 - 0 2 - 0 3 - 0 4 - 115

Jumps

x 226

Hands

x 1

Quads

x 1

Color Jumps

x 0

Color Hands

x 0

Color Quads

x 0

Most notes in:

1/3 of a Second
8 - 24.00 nps 0.5 Seconds
11 - 22.00 nps 1 Second
17 - 17.00 nps 2 Seconds
30 - 15.00 nps 5 Seconds
68 - 13.60 nps 10 Seconds
128 - 12.80 nps 30 Seconds
359 - 11.97 nps 1 Minute
661 - 11.02 nps

Color Count

x 408 (51.39%)
x 281 (35.39%)
x 0 (0%)
x 105 (13.22%)
x 0 (0%)
x 0 (0%)
x 0 (0%)
x 0 (0%)
x 0 (0%)

Largest Note Gaps

0.47s0.47s0.3s0.3s0.3s0.3s0.3s0.3s
35
28
21
14
7

Behind you (QwertyVibin) [8/10]

PERMS OK
SYNC OK

18.951: The rolls don't really match the song too well. Consider something like 4323(14)213(24)

20.801: For better PR, do (14)(14)4 here. 22.851 does it well.

22.476: Ghost note.

23.901: Move to col 2, not same note as the preceding 4th. See 33.501 for example.

24.801: (12) here, not the same as the preceding (23).

28.851: Just a suggestion, but here a 43432 would break from the 2-hand stuff to emphasize the fade-in.

29.901: No big deal, but better to not have this 8th on the same column at the 8th jack that follows it.

35.001: Nothing really justifies the change here. Should either be (13)(13) or (23)(23).

39.651 & 40.851 & 42.051, etc: Inconsistent with the intro where the piano notes are jumps.

57.351: Same concern as 18.951. Something like 1232(14)342(13).

1:00.801: (23) here.

1:05.601: Same as 1:00.801. Could be (34) for variety.

1:05.901: Same concern as 29.901.

1:07.101: Here, moving to column 3 could be justified to have the following 16ths be 12123 to match 28.851. (Would need to slightly adapt the PR on the following 8ths)

1:15.051: (24) or something, not jumpjack.

Super cute chart. Most notes are suggestions to really polish the motifs. Good job there.

behind you (QwertyVibin) [7/10]
>Perms, metadata, sync good

9.501-9.651 - Why minijack?
14.151 - Should be jump
17.301-17.750 - Why jump? No kick
18.951-19.176 - Fix PR. Compare 18.651-18.875
19.701 - Move to 4 for minijack noise
20.601-20.901 - Should be [14][14]4
21.501 - Move to 2 to avoid unintentional minijack
22.251 - Please use a different jump pattern from 21.951 (something that isn’t [13])
23.901 - Move to 2
24.801 - I suggest changing this to [12] for better jack PR
25.851-26.451 - I suggest [13]4[12]431[23]
28.101 - Move to 4
29.151-29.301 - I suggest [23]3
29.751 - Move to 3
30.051-30.501 - Maybe make the jack go on the 1 lane so it doesn’t collide with the 3 lane of the previous nearby 16ths
31.251 - Move to [24]
32.151 - Move to 4
33.951-34.101 - I suggest [14]4 b/c right now the [2] lane is colliding with the minijack noise and the non-minijack noises
35.001-35.151 - These two jumps need to be the same jump pattern, see the previous times you’ve done this type of pattern
36.051 - Move to [34]
36.801 - Move to [34]
39.538 - Missing note
49.951-49.101/50.151-50.301/51.351-51.501/52.551-52.701 - Why minijack?
52.701 - Move to 2
55.701-56.151 - Why jump? No kick
57.051-1:15.576 - Basically apply everything I pointed out from “18.651-37.251” to this entire section
1:15.651-1:16.101 - Fix PR. Compare 37.251-37.701
1:16.701 - Why hand? Compare 38.451, which at least had a special explosion noise

>>Layering is good, but I’m surprised you weren’t consistent with the song’s theme of vocal minijacks (which was your intent to begin with, shown from 22.851-23.301 for example)

Wondering what the situation is on this file, as it has been over a month to submit and receive fixes, and no acknowledgement of judge notes have been submitted, despite the "Change Recommended" flag on the file, which at a bare minimum, requires ticking the box to "acknowledge judge notes" on the bottom of this page where notes are.

Moving to rejected. If fixes happen to be applied, or wish to submit in the future, please re-submit to a currently open batch.