Snows -Soshite Kiseki- :: FFR Batch Submission
Winter 2023 Seasonal Batch
PublicTokenPurchasedSecretEvents
Rejected
Simfile Folder Name
snows -Soshite Kiseki- (TheTrueXfish)
Note Count
3838
Chart Length
4:05
Average NPS
15.8399
Estimated Difficulty
89.61
First Note
0:03
Ending Note Delay
0:01
Hand Bias
Framers
0 - 0
1 - 0
2 - 0
3 - 5
4 - 230
Jumps
Hands
Quads
Color Jumps
Color Hands
Color Quads
Most notes in:
1/3 of a Second
10 - 30.00 nps
0.5 Seconds
14 - 28.00 nps
1 Second
24 - 24.00 nps
2 Seconds
41 - 20.50 nps
5 Seconds
94 - 18.80 nps
10 Seconds
186 - 18.60 nps
30 Seconds
550 - 18.33 nps
1 Minute
1061 - 17.68 nps
Color Count
Largest Note Gaps
0.33s0.33s0.33s0.33s0.33s0.33s0.33s0.33s
Posted at 5:30am on October 19th, 2023
I forgot to fill in the credit in the metadata bruh.
A new chart file was uploaded.
Posted at 4:18pm on October 19th, 2023
This time I put the wrong artist in the metadata wtf is my brain doing..
A new chart file was uploaded with the following changes:
----------
Artist changed: DJ Sharpnel => Jea
----------
Posted at 4:46pm on December 5th, 2023
Fixed up a few spots, I think this file is ready now tbh
A new chart file was uploaded with the following changes:
----------
Title changed: Snows -Soshite Kiseki- => snows -Soshite Kiseki-
----------
Note Count changed: 3818 => 3838
AVG NPS changed: 15.75733 => 15.83987
Hand Bias changed: -36 => -28
Posted at 10:39pm on January 21st, 2024
snows -Soshite Kiseki- (TheTrueXfish) [6.5/10]
- Perms, metadata, sync are good
Jeez, absolutely no break in the file?
0:21.313-0:41.923 - Cool jump utilization there, however I feel like the jump variation is quite limited , you have a few segments where you repeat the same placements instead of having a different, unique one (ex: 0:36.938-0:40.482 - Two times [12][24] in the same segment)
0:31.622 - Missing jump
0:45.636, 0:45.959, 0:50.791, 0:51.113, every other instance of this - What are these jumps going to?
0:54.174, 0:54.335 - Inconsistent reverse jump usage, compare to prior segments
1:23.974 - Missing jump, as a result remove also the 4th jump prior
1:28.807 - Missing jump - remove appropriate upcoming 4th
1:33.961, 1:34.284 - Missing jumps, take into consideration notes above
2:20.192-3:00.946 - I like the motif for the 8th jumps, where you do two of the same column and one alternating. Although I wished to see some motif for the 4ths as well. In any case, pay attention closely to your variation in the 8ths. Sections like 2:20.515-2:23.897 only utilize jumps on [14] and on [12] while sections like 2:25.025-2:29.052 and 2:35.334-2:39.361 utilize 3 unique jump placements
3:27.525 - Weird that this jump repeats with the 4th prior. Every other instance of this section have 3 different jump placements
3:52.654-4:02.964 - The alternating jump segments play kinda arbitrarily, for the first segment you do [12][14], but on the 2nd segment you do [12][34] where instead you could mirror it to [34][14] etc.
Fairly standard jumpstream file with absolute no goddamn break, I think that's a first for that kind of difficulty?
This is quite decent, but there are a few technical stuff that are overlooked which require to be revised before I can confidently determine this as accepted.
I don't like how the 32nd rolls are almost always descending, when many parts should come off more as ascending notes. May be subjective, but I think it fits better that song.
There could be a bit more consideration for the flow at the intro in terms of PR, since the melody is sparse and all that you can take is just the single 16ths.
Posted at 10:40pm on January 21st, 2024
snows -Soshite Kiseki- (TheTrueXfish) [7/10] -FR-
PERMS OK
SYNC OK
31.622: Jump. 21.313 has it.
44.992: Why is this a jump and not 44.670? The same sound at 42.415 isn't layered as a jump.
46.281: What is This jump for??
50.147: Shouldn't this jump be on 49.825?
55.946: Again, why jump here?
1:22.847: Why no jump here but jump on 1:22.525? Both have piano and vocals.
1:28.807: Why no jump there but a jump on 1:23.652? Both have melody. Arguably 1:26.229 too should have it, and also the 16th at 1:31.465, and also 1:33.961, etc etc.
2:09.400: Missing jump, vocals.
The chart is very standard js stam. It makes sense for the most part, but there are noticeable layering issues (or at least concerns) to be checked. FR for a solid check up on that layering because it's basically a main element of such a chart. PR is fine I guess, and not many noticeable motifs to follow but that's understandable for such a long and sustained js chart.
Posted at 5:14pm on January 24th, 2024
Rejection upheld
I agree with the main criticisms both Op and Deam list out regarding the layering here. A js stam chart should at bare minimum have that correct.
Another major issue I see with this is a number of unnecessarily long anchors to nothing that hamper the chart's flow. Generally want to avoid anchors >4 notes unless they're going to something in a chart like this. This gets harder to do as you increase the layering but if you can work it out, the chart will have an increased sense of flow. Some notable example spots include
43.381 - 4/2 anchors
56.671 - 3
1:56.916 - 3
etc.
On a more subjective note, more could have been done to make this a more interesting chart. From smart/climactic use of OHTs or anchors to perhaps introducing more of a tech/non-constant-js element in certain parts. It's otherwise kind of monotonous to play. Part of that is just the song, so you really need to extract every little interesting part of the music here imo.
I'm not entirely opposed to the idea of this chart, even if the main idea of pure js stam sticks around. But this needs some improvements first - both layering and anchor control. Too much for an FR rating to catch.