Zettai ni Makerarenai Tatakai ~ Kill the Nyanko :: FFR Batch Submission
suicidaln00b -
Zettai ni Makerarenai Tatakai ~ Kill the Nyanko -
ARM ft. Choko [7 / 10]
May/June 2021
PublicEvents
Rejected
Simfile Folder Name
Zettai ni Makerarenai Tatakai ~ Kill the Nyanko (suicidaln00b)
Note Count
2055
Chart Length
2:39
Average NPS
13.2069
Estimated Difficulty
98.1
First Note
0:03
Ending Note Delay
0:04
Hand Bias
Framers
0 - 0
1 - 0
2 - 2
3 - 332
4 - 247
Jumps
Hands
Quads
Color Jumps
Color Hands
Color Quads
Most notes in:
1/3 of a Second
10 - 30.00 nps
0.5 Seconds
13 - 26.00 nps
1 Second
24 - 24.00 nps
2 Seconds
44 - 22.00 nps
5 Seconds
103 - 20.60 nps
10 Seconds
191 - 19.10 nps
30 Seconds
503 - 16.77 nps
1 Minute
964 - 16.07 nps
Color Count
Largest Note Gaps
3.8s2.1s0.83s0.83s0.77s0.77s0.73s0.63s
Posted at 10:16pm on November 6th, 2021
Zettai ni Makerarenai Tatakai ~ Kill the Nyanko (suicidaln00b) [7.0*/10]
> Permission check good.
> Sync looks good (No changes necessary).
> No issues found within simfile properties.
> No issues found within submission folder contents.
**-Permission needs a follow-up on whether or not this submission meets the permission requirements. The initial submission comment does not give me any information on whether or not the criteria of ‘Blanket, though all songs need to be shortened and contact jimerax beforehand’ is met. The song may or may not be shortened, as this was written before the chart was reviewed, and no proof was given that jimerax was contacted, so this will at-most be CQ’d until this is resolved.
-Going into this chart, 290bpm 24ths is not going to be fun at all for anyone to stream, so I’m going in with the impression that these 145bpm 48ths are going to be hit as jumps, so please keep layering stuff this fast & aggressive in-mind.
-[00:49.803] Missing 4th? Wut
-[00:50.216] This type of aggressive one-hand layering can probably be stayed clear of. If it needs to be done, do it with two hands.
-[01:06.561] Missing 8th.
-[01:20.630] What makes this 48ths but not something like, 01:22.492, 01:22.802, 01:25.802 etc. not 48ths? Should probably all be hands/jumps since it’s rather obscure what defines 48ths and what doesn’t.
-[01:33.561] These are some actually painful minijacked jumps here, since it will be played as [24][13][24][13] 24th jumptrill into [34] 16th jump. With it happening back to back to back 3 times on the right hand, this is an incredible amount of hand stress. The same then happens to the left hand.
-[01:43.182] Callback to the note at 00:50.216.
-[01:46.492] This buzz megatrill that is not necessarily falling to any rhythmic beat is appalling.
-[01:52.699] I get that some of this minitrill stuff is apparent in bursts earlier in the file, but maybe not this fast? There’s a lot of patterns that are pushing for difficulty, and the further it gets into the file, the less fun it is making itself out to be (it’s slower earlier in the file but faster, later).
-[02:08.423] Nothing here?
-Heavily suggest changes regarding notes [01:33.561], and [01:20.630]. Outside of that, file is CQ’d pending the situation regarding the marked note in asterisks (**).
Posted at 8:58am on November 7th, 2021
Thanks for the notes, will look at later.
There's actually information about permissions on IOSYS's website here, starting from where it says "About the use and license out of songs and videos":
https://www.iosysos.com/about.html
The relevant points are as follows, but keep in mind that I just threw this into DeepL and verified with my babby level moonrune knowledge:
イオシス管理楽曲について個人で非営利目的の場合は常識の範囲内でご自由にお使いください。
Please feel free to use the songs managed by IOSYS for personal, non-commercial purposes within the scope of common sense.
*イオシスが制作した楽曲でも「イオシス管理楽曲ではない」ことがあります
Please note that some songs produced by IOSYS may not be "IOSYS managed" songs.
イオシス管理楽曲かどうかは googleスプレッドシート「IOSYS公開データ」の青いシートのF列をご参照ください。
Please refer to column F of the blue sheet in the google spreadsheet "IOSYS public data" to see if it is an IOSYS-managed song.
(If you want to read the rest then just throw it into DeepL, but it more or less just boils down to "don't do dum shit with our songs thanks")
Using the spreadsheet provided, this song in particular is managed solely by IOSYS, so it should be fine to use.
https://docs.google.com/spreadsheets/d/1DJQLrSgfPhxSIH1-rDS_Nwzxm9sektgrZr2ESC-N3dk/edit#gid=991684842&range=D3400
Edit: Anyway, as it stands, FFR's permissions information on IOSYS are pretty outdated. The "contact jimerax" requirement seems pointless if IOSYS already provides permission guidelines. Additionally, there's no mention of songs having to be cut on the IOSYS website.
Posted at 8:09pm on November 30th, 2021
I should probably update this
Only updated 01:33.561 and 01:20.630 since I'm lazy oop
A new chart file was uploaded with the following changes:
----------
Note Count changed: 2048 => 2055
AVG NPS changed: 13.16195 => 13.20694
Hand Bias changed: -12 => -9
Posted at 9:46am on January 5th, 2022
>Status: Rejected
what
at least give a reason
Posted at 12:10pm on January 5th, 2022
Can do, since this was quite a complicated submission (and admittedly, a controversial one).
This was originally judged by Pizza when it was first submitted at https://www.flashflashrevolution.com/batch_submission/batch/?id=963
When it was re-submitted, I approached Pizza about what they thought of the revisions, and found that they were fine granted the CQ stuff that I provided in the above review, so I chose that despite myself wanting to reject it for similar reasons in the first review that it's still too aggressively done. Specifically with 48th bursts, and extended 32nd stream making the difficulty peak of the file. A lot of the notes placed within these are giving off a lot more steam than the music is portraying, even given some of the more recently released files that overstep/exaggerate dubstep, this particular submission exceeds in intensity of others by magnitudes. However, I could not realistically provide a lower score than Pizza's without noting potential judge bias since fixes applied to the file did make the overall file better than its previous submission. Looking back on this, that was an error on my part and I should've bit the bullet on it, and I apologize.
Then, a barebone permission check locked this in CQ, and I received zero update from Kayla (psychoangel691) about this song or your responses until I was given tools to take another look at it. Which is what happened, with a live judge panel to analyze and come to a conclusion of what to do with songs that were stuck in batch in a similar fashion.
Me, bmah and Gradiant (along with a couple other staff members) decided in a 3-1 ruling to reject the file for the above reason, in that it was too exaggerated and it was a rare misjudge on Pizza's part regarding its original submission to batch. Hopefully switching to the two-judge system (which is currently being used right now) helps in resolving these sorts of problems from occurring in the future, and I welcome any feedback (or a few choice words) in my DM's since this is a case of failure within the batch system itself, and I am responsible for it.
Posted at 6:07pm on January 5th, 2022
lol ok fine, I already initially expected this to get rejected for being too dumpy, though I'm mildly annoyed that it took over a damn year to do so
I imagine even if I made a ~21 MSD babby version of this file (say, with the 48th bursts nerfed to 32nds and the long 32nd stream to 24ths) it'd still be rejected on the grounds of being too exaggerated for FFR's taste, so I don't think I'll bother resubmitting this
though I'm still slightly tempted to make an easier version just to see how it plays
anyway time to throw this meme file at some etterna pack or some shit