Batch Submission Updates

[psychoangel691]

Hello everyone!

As some of you have already noticed there have been some major changes to our batch submission area. Velocity basically took my list of stuff and made my dreams come true, haha.

Our old way of doing things has become pretty outdated and was hard to manage with 3 separate emails and tons of threads it was easy to get things mixed up. Now everything is all centralized into the batch submission area. You also can now easily see everything that's in queue to be released (unless it's from a private batch). Yes, I said private batches, we do have the ability to make it so you cannot see submissions to a batch that are not your own in order to keep some surprise when it comes to certain events. You'll always be able to see and edit your own submissions though.
Another awesome addition is when you submit your file there are now checkboxes that allow you to indicate if you'd like it to be a token, secret, or purchased file and whether you're okay with your file being held for future events. That will help me build up files for the OT's a lot faster, I was always weary about holding because I didn't want to upset anyone by holding a file for an extended period.

We also no longer need to use threads at all for the judgement of batches, everything will now be done right in the batch submission area. I can assign judges sets right within it, they can leave their notes and ratings on the file in the system, and you'll get a notification any time you get a status change on your file.

Lots of awesome stuff all around and I can't thank Velo enough for making it possible. I think I covered everything but if you have any questions about the new system please feel free to drop them in the thread here or reach out to me on discord

[Psychotik]

Re: Batch Submission Updates

Thanks owlman

[mi40]

Re: Batch Submission Updates

thanks, and conditional queues are still 4 weeks from submission of judge date right? it would be nice to receive a private message from the system saying "your file was judged" or something

[klimtkiller]

Re: Batch Submission Updates

oh cool! i like how i'll be able to get a notification too. could there also be a list of files which havent been accepted?

btw about private files, i don't want to waste my time stepping a file that's already been stepped for ffr, which is why i always check the batch before starting on a file. wouldn't this be a problem?

[gold stinger]

Re: Batch Submission Updates

thanks, and conditional queues are still 4 weeks from submission of judge date right? it would be nice to receive a private message from the system saying "your file was judged" or something

From the work I've seen Velocity do, you should now receive updates to judge scores in the top right of the website next to your username whenever the score (e.g. the [9.5/10]) is updated in the batch for a song, or whenever the status (e.g. from unjudged to accepted or conditional queue, etc.) of a song is updated.

It will be in the same location as notifications for when you receive a DM, a thumbs up or thumbs down on your profile, a profile comment, etc.

And yes, as far as I'm still aware, the status quo on time for conditional queue fixes is still 4 weeks. Only time I think it's been circumvented is when it's needed for immediate release to cover a spot in a tournament or similar situation.

oh cool! i like how i'll be able to get a notification too. could there also be a list of files which havent been accepted?

btw about private files, i don't want to waste my time stepping a file that's already been stepped for ffr, which is why i always check the batch before starting on a file. wouldn't this be a problem?

There's never a guarantee that the same file made by another author will get in, and the submission rules regarding same-song submissions that are around the same difficulty have pretty much been abolished. Also, I'm pretty sure that private batches will only be used in situations where displaying those submissions would affect something like a tournament. It's not going to be a regular practice to privatize open batches.

[HammyMcSquirrel]

Re: Batch Submission Updates

Thank you, Velocity!

[mi40]

Re: Batch Submission Updates

woohoo i just saw the star, that's pretty neat

[Velocity]

Re: Batch Submission Updates

Pleasure doing business.

[psychoangel691]

Re: Batch Submission Updates

oh cool! i like how i'll be able to get a notification too. could there also be a list of files which havent been accepted?

btw about private files, i don't want to waste my time stepping a file that's already been stepped for ffr, which is why i always check the batch before starting on a file. wouldn't this be a problem?

I stated this in the other thread as well, when we were on the email system you guys had NO idea what was being submitted. So it seems like a pretty silly argument to have. We also have done private and internal batches for the OT every year without any issue.

[hi19hi19]

Re: Batch Submission Updates

I stated this in the other thread as well, when we were on the email system you guys had NO idea what was being submitted.

It used to be that the pool of steppers who could actually get things into FFR was so small I could just ask what people were stepping or post on the forums that I was stepping a certain song and that alone would make me reasonably sure there would be no conflicts. For example to this day I have the folder of music that bmah sent me that he was holding for stepping and I don't touch anything that's in there, at least not without telling him.

As the judging in FFR has gotten less strict and the number of steppers submitting has grown, I've found the odds of collisions has grown a lot - I still don't feel great about what happened with Aggressor, for example - and with that in mind I find being able to see everything is nice. More than a few times with the old Batch Search Engine, I heard a song that I was considering stepping then searched it only to find there was already a submission for it, and each time that happened I appreciated that functionality stopped me from investing hours into something that was already envisioned by someone else.
Yes there are solutions like adding in multiple difficulty tags or [Another] but even then I personally prefer not to step on anyone else's toes, and I imagine I'm not the only one who feels that way.

[psychoangel691]

Re: Batch Submission Updates

Okay well then if it's such an issue then I'll abolish the all new song OTs and only use in game files going forward.

[trumaestro]

Re: Batch Submission Updates

It used to be that the pool of steppers who could actually get things into FFR was so small I could just ask what people were stepping or post on the forums that I was stepping a certain song and that alone would make me reasonably sure there would be no conflicts. For example to this day I have the folder of music that bmah sent me that he was holding for stepping and I don't touch anything that's in there, at least not without telling him.

As the judging in FFR has gotten less strict and the number of steppers submitting has grown, I've found the odds of collisions has grown a lot - I still don't feel great about what happened with Aggressor, for example - and with that in mind I find being able to see everything is nice. More than a few times with the old Batch Search Engine, I heard a song that I was considering stepping then searched it only to find there was already a submission for it, and each time that happened I appreciated that functionality stopped me from investing hours into something that was already envisioned by someone else.
Yes there are solutions like adding in multiple difficulty tags or [Another] but even then I personally prefer not to step on anyone else's toes, and I imagine I'm not the only one who feels that way.

I would also point out that the pool of suitable music for FFR has grown a lot. We no longer have 4 files of the newest cornandbeans song in one batch or a 3-way "race" to get a Trisection v2 in queue. We have permission from -hundreds- of artists and Creative Commons licensing allows for countless more.

I don't speak from recent experience, but I think that nowadays you'd either have to step "VSRG meta" songs, or tread on someone's niche like :VS: to risk encountering this problem. But with so much music to choose from, shouldn't this conflict be getting more unlikely?

[psychoangel691]

Re: Batch Submission Updates

I would also point out that the pool of suitable music for FFR has grown a lot. We no longer have 4 files of the newest cornandbeans song in one batch or a 3-way "race" to get a Trisection v2 in queue. We have permission from -hundreds- of artists and Creative Commons licensing allows for countless more.

I don't speak from recent experience, but I think that nowadays you'd either have to step "VSRG meta" songs, or tread on someone's niche like :VS: to risk encountering this problem. But with so much music to choose from, shouldn't this conflict be getting more unlikely?

I was going to point this out myself, but I'm just so over arguing with everyone at this point. So if people are so anti anything being private I just won't run any events that needs private batches anymore. It is what it is.

[klimtkiller]

Re: Batch Submission Updates

I was going to point this out myself, but I'm just so over arguing with everyone at this point. So if people are so anti anything being private I just won't run any events that needs private batches anymore. It is what it is.

I don't think anyone's trying to be argumentative here...people are merely stating a concern. no one wants to spend the time to step a file only to find out it's rejected because the same song is already in queue. it's not like it's a really big issue. one solution could be for there to be a search function in the batch; when you search for a song, it tells you whether or not it's been sent by another user.

[gold stinger]

Re: Batch Submission Updates

I don't think anyone's trying to be argumentative here...people are merely stating a concern. no one wants to spend the time to step a file only to find out it's rejected because the same song is already in queue. it's not like it's a really big issue. one solution could be for there to be a search function in the batch; when you search for a song, it tells you whether or not it's been sent by another user.

Kind of ruins the feature of private batches, as well as numerous issues on that, such as unexpected spelling errors, or people bruteforcing Official Tournament batch song names to figure out submitted content which defeats the purpose of it.

Also kinda ignored my post from the other thread that is parallel in discussion with this one.

oh cool! i like how i'll be able to get a notification too. could there also be a list of files which havent been accepted?

btw about private files, i don't want to waste my time stepping a file that's already been stepped for ffr, which is why i always check the batch before starting on a file. wouldn't this be a problem?

There's never a guarantee that the same file made by another author will get in, and the submission rules regarding same-song submissions that are around the same difficulty have pretty much been abolished. Also, I'm pretty sure that private batches will only be used in situations where displaying those submissions would affect something like a tournament. It's not going to be a regular practice to privatize open batches.

edit: whoops, turns out I am in said thread. Huh. Funny how discussion on a topic blends like that.

Also, there's nothing stopping discussion of people freely talking about what they submitted to batches, even if they are privatized. We have a pretty massive Official Discord that is talkative in all times of the day, and is no shortage of a hub on discussions in all things simfiling. I can understand some level of concern in the possibility of accidentally making charts for the same song under the same relative difficulty, yet the private batch update was only intended for usage where it's needed, and not for blanket prevention of people viewing batch, which is where the argument feels like it's stemming from.