Fungus Dance :: FFR Batch Submission
Wind0ze - Fungus Dance - paraneumann [7.25 / 10]
OT17 Bounty Batch
PublicEvents
Rejected
https://docs.google.com/spreadsheets/u/0/d/1caYqjxEhD3CxDdJhq1AAAxsf3rlHaG6783cNyvgzXFE/htmlview#
BOFXVII

For low 100s.

Simfile Folder Name

Fungus Dance (Wind0ze)

Note Count

1880

Chart Length

1:59

Average NPS

16.2116

Estimated Difficulty

97.38

First Note

0:03

Ending Note Delay

0:01

Hand Bias

x -38

Framers

0 - 0 1 - 0 2 - 0 3 - 352 4 - 249

Jumps

x 657

Hands

x 90

Quads

x 2

Color Jumps

x 1

Color Hands

x 0

Color Quads

x 0

Most notes in:

1/3 of a Second
10 - 30.00 nps 0.5 Seconds
15 - 30.00 nps 1 Second
25 - 25.00 nps 2 Seconds
48 - 24.00 nps 5 Seconds
107 - 21.40 nps 10 Seconds
210 - 21.00 nps 30 Seconds
561 - 18.70 nps 1 Minute
1020 - 17.00 nps

Color Count

x 496 (26.38%)
x 450 (23.94%)
x 58 (3.09%)
x 784 (41.7%)
x 17 (0.9%)
x 63 (3.35%)
x 10 (0.53%)
x 0 (0%)
x 2 (0.11%)

Largest Note Gaps

0.8s0.37s0.37s0.37s0.37s0.37s0.37s0.33s
35
28
21
14
7

Approved for low 100s bounty.

Permission good (BOF)
Sync good
Metadata good
(Unrelated to the judgement, but I think this is actually closer to 96-97 considering my PB of 2.4)

- 3.535: ghost
- 12.934-13.159: same as 5.697-5.941, not 24ths
- 25.621: move to 25.603
- 32.445: jump
- 39.663: move jump to 39.888
- 40.001, 41.467: no jump
- 43.460: ghost
- 43.846-44.738: the left hand is a bit tricky. Mirror seems to work, though I wonder if it can be eased a bit somehow
- 51.505-51.731: they are just 32nds
- 51.918: move to 51.881
- 52.520: move one of them to 52.558
- 57.144-57.370: they are 24ths

- 1:20.941: hand
- 1:21.731: no hand
- 1:24.888-1:25.227: hands
- 1:27.708: missing
- 1:27.934: no jump?
- 1:28.159: jump
- 1:48.629: move to 1:48.648
- 1:51.618: no hand?

A tricky hand-control chart that actually plays well, with neither hand going too overloaded. A general cleanup would be nice such as quantization here and there, but these are minor points and it overall seems good enough.

Judge Score: 7.50 - Accepted

Fungus Dance - Change Recommended (7.0)

BMS of Fighters perms look fine to me
Metadata is good
Sync is good

00:07.407 - Should be a jump, theres a drum hit here.
00:12.934 - Should be flammed similarly to how you did it at 00:05.715, not a poly.
00:25.452 - No drum hit here, consider a single on 1 to better portray that.
00:25.621 - Not a 32nd, should be flammed on the 48th at 00:25.603

00:30.302 - Consider moving to break up the 5jack on column 1 for better consistency with how jacks are structured through this section.

*00:44.287 -> 00:57.821 - The anchoring through this bit of the file struck me as pretty sloppy. Particularly the usage of 3 and 4 length anchors felt rather inconsistent and hard to distinguish, especially when compared to the to the similar iteration starting @ 01:34.813 where anchors are clearly aligned with the backing synths.

00:47.558 - Missing jump, theres a drum hit here.
00:55.227 - Should be a single, no percussion here.
00:56.975 - These 32nds are ghost notes? Very unclear whats being followed here.

01:20.941 - Should be hand for consistency with 01:20.377 & 01:20.715
01:24.888 & 01:25.227 - Should be hand for consistency with 01:24.663, 01:24.324, 01:23.986
01:49.249 - Hand, see previous notes

Neat little chordjack file. Its fun to play and sets itself apart from most of the existing chordjack found on FFR. The polys forming jumpstreams are rather fun and intuitive breaks from the chordjacks and most of the file makes good use of anchoring. I think the file overall would make for a solid addition to FFR's catalog of chordjack files, however I would personally like to see a bit more refinement to the approach in the starred section above.

Judge Score: 7.00 - Change Recommended

Checking in on the status of this submission, as it's nearing 1 month probationary period with a "Change Recommended" flag, but there's been no acknowledgment of judge notes or fixes submitted.

Files/Songs with the "Change Recommended" tag require at a minimum a response from the Stepauthor in order to continue through the submission system.

I will check back on this at a later date. If it does not receive a response or fix by then, it could risk rejection.

Rejected due to Change Recommended flag and no response.