United States
SupporterLocking this thread due to bot abuse. Feel free to reopen a new thread if there are any further thoughts.
Stages requested in no particular order but grouped as needed.
Implemented
- DH-9
- DV-8
- GA-8
- IS-10
- IW-9
- JT8-3
- M8-8
- NL-10
- NL-EX-8
- SN-10
- SV-9
- WD-EX-8
- WR-EX-6
- 7-18
- 9-19 Standard
- 10-17 Standard
- 10-17 Adverse
Story Stages
- R8-11 - no kill gate; stage seems too long to be interesting for PRTS
- 11-17 - predetermined squad; need to explore this idea and similar stages
- 12-20
Hell Stages
Hell stages might not happen as it may break the accessibility clause, but need to consider how late these stages are. More research is needed.
Edit: I'd like PRTS attempts for this category first before further consideration.
- H7-4
- H8-3
- H8-4
- H9-6
- H10-1
- H10-3
- H11-2
- H11-4
- H12-1
- H12-3
- H12-4
Event Stages
Includes normal stages, EX stages, and special stages. Anything outside of normal stages are unlikely to be implemented unless it is popular or interesting.
Edit: For EX/Special stages, I'd like PRTS attempts before further consideration.
- NL-S-3
- WR-EX-3
- WR-EX-8
- MB-EX-8
- MN-EX-8
- DH-EX-4
- DH-EX-8
- DH-S-4
- WD-EX-1
- SN-EX-8
- SN-S-5
- IW-EX-8
- GA-EX-8
- TW-EX-7
- IS-EX-8
- DV-EX-8
- CW-EX-8
Some extra thoughts I wrote down, but removed.
Most of the other categories fit the nature that the PvP community is looking for. However, it involves too many stages that are unfit for their current format. This is why the level leaderboard is the most suitable area for them to compete.
It is important to understand that speedrunning and PvPing are similar in nature: the idea to clear the stage as quickly as possible. However, there are 2 distinct differences:
- PvP focuses on a mixture of low step and AFK strategies, whereas speedruns focuses on well-timed and well-executed ability use.
- PvPing takes place in a live settings, usually on streams that host PvP tournaments, where a player's actions affect the time immediately and leave little room for mistakes.
Speedruns are meant to go through a review process before officially recording the time on a persistent leaderboard not meant to adjust. Players can attempt a strategy as many times as they want before submitting, which can lead to some runs taking months or years to complete flawlessly.
Hi @GL1TCH3D, thank you for your continued interest in AK speedruns. I hope my responses below are sufficient for your concerns.
even without glitches, a unit like Mlynar drastically changed the landscape for speedruns, especially in categories like IS (where he obliterated no relics as well).
Operators that decrease the amount of time to clear will not reset the leaderboards. An example would be Horn S1 saving a full second on Anni 3. Conversely, changes to the game that prevent replicating or would overall slow down the run will result in the leaderboards being archived and refreshed.
Our goal is to have 0 leaderboard refreshes annually, but we will take steps to archive if it is necessary. You can view some of those old categories in the Archive leaderboard. We don't foresee Hypergryph making underlying design changes like Digital Extremes does with something like parkour 2.0 (though it was an improvement overall).
My recommendation in this sense is maybe instead of limiting what can be done
Though I responded above with how to handle serious gameplay changes, I want to state here that we are not interested in limiting the player outside of infrequent contests. I will explain this more later, but from my experience, restrictions make things convoluted and feel more like bloating the leaderboards.
So the point of this text block is more to say, what's your vision for accessibility in Arknights?
My vision for accessibility is that anyone can jump into speedruns at any point, no matter their progress.
Yes, having maxed potentials on maxed operators with maximum trust will improve your time in certain scenarios. However, this is for competing at the top 10%. Having this type of account is not a necessity and would create an artificial barrier of entry that would defeat our goal.
We value personal player progress over leaderboard position. Think of the moderator team as not just the individuals trying to keep the playing field fair for everyone, but also the cheerleaders. Whether you are always in 1st place or in 50th place, we celebrate when you, the player, are enjoying yourselves and are showing the willingness to improve your times (this is why we do not reject obsolete runs).
For a newer player who may only have one or two 6* operators, the moderator team should be helpful in guiding the player to completing their goal of a certain time with what they have available. This is why we do not implement restrictions outside of the infrequent contests. We take pride in being the only niche that has access to all operators (267 at the time of this post)! Even for veteran speedrunners, we intend to help them progress and reach their goals.
No matter if you started Arknights last week or on Day 1, your speedrun is still valid for the leaderboards if you have the passion and motivation. My explicit expectation to the moderators is to be there, ready to help, and to cheer any level of speedrunner. This is my vision of accessibility.
Will this be used for new account speedruns as well?
Unfortunately, we do not have plans to use the calculator for New Account speedruns due to the sheer logistics of verification.
There are many many different divisions of New Account categories. Were these popular in communities in China?
To my knowledge, these are more popular in Japan. For specific New Account related inquiries, I defer them to @Hinabu's and @LeSot's expertise.
I wonder if Yostar would allow a specific channel dedicated to the discussion of speedrunning in arknights on the main discord as that could definitely help visibility (indirectly popularity) and accessibility.
This would be great to have, but a related link to the AK Speedruns Discord might be more sufficient. We separated from Cesith's Discord earlier this year for the ability to stay agile and eliminate the need to contact an administration above us when we needed things done.
I am not opposed to the idea for the AKO Discord, but there are some logistical and administrative needs that would have to be implemented beforehand.
Hey runners, I wanted to share the internal guidelines that I personally have used for years and allows new verifiers/mods to understand how to approach a community. These guidelines were originally written by @Celestics who I worked with during my tenure as Warframe supermod. You can view that forum post here.
These four simple guidelines should help you understand what type of categories we are looking to provide for the community. If you have a recommendation for a new category, follow these guidelines when creating it and then contact the mod team so we can review it.
- Consistency: Future changes to the game shouldn't often obsolete runs. In this sense, most categories should be glitchless.
- Accessibility: Any player should be able to get their feet into these runs, and we should help them be able to.
- Popularity: Players should be interested in actually running these categories.
- Sensibility: Categories should just plain make sense from the standpoint of an outsider reading through their descriptions.
Please readd a way to delete variables and categories after archiving. Sometimes experimenting with the structure of the leaderboards leads to mistakes that are now permanent.
We can definitely add in the clarification. Thank you for the suggestion.
This would be viewed as a macro as it is taking more than one action from the keypress, which includes cursor movement, and would be forbidden.
While this script might be considered harmless, we do not want to set a precedent where lines are likely to be skirted. Generally, getting into speedrunning should be as "ready out of the box" as possible. Tools not available within the standard emulator and requiring different software would reduce accessibility.
The lack of built-in customizable controls for the Google Play Games emulator is something to be desired and hopefully Google will implement it in the future. I am also personally hoping for this feature as I would like to permanently move to GPG as it is less taxing on my system.
I'm looking to collapse the Annihilation subcategories (except for DP Printing) into each other, and likely without keeping the star restriction.
Lemme know your thoughts.
Current criteria for PRTS Runs are:
- Popularity: Players should be interested in actually running these categories.
- Kill Gates: Stages should have at least one kill gate that is not the last enemy.
- Can check with PRTS.Map.
No map is off the table, per se, but we would like to avoid dead or uninteresting categories.
The RNG is incredibly enormous and encompasses the entire run, which is a major turnoff for me. It would be a hasty generalization to argue that "X speedrun has RNG unseeded runs why not ours" as their community is not ours and the journey towards completion in their runs vary from Arknights.
I like that the game provides an IGT at the end, so hardware supremacy will not be a determining factor for runs. So I would be interested for at least a Easy or Normal category to be setup.
As for structure, since this is a preliminary and novel category, I would request that the rules are unrestricted initially and then tuned as time goes on.
@Cesith, there's a few easy tools to do this, the simplest is using: https://slashinfty.github.io/yt-frame-timer/. It might not be the most accurate, but it's fairly quick to use for everyone. There's a few other local tools available for free for more accurate framecounting in the event of a dispute.
Also, feel free to copy the standards that was used in another speedgame: [quote]Framecounting Standards • You must provide the first frame, the last frame, and the frames per seconds used to calculate the final time in the description of your submission. • In the case of dispute by a verifier of final time, you will be asked to provide the raw footage used to calculate your final time. If a consensus is not agreed upon by the verifier, a separate moderator, and yourself, the slower of the two times will be used to represent the run's final time.[/quote] Source: https://www.speedrun.com/wf/guide/oe489#ch3_Framecounting
Would it be possible for specific event stages using PRTS to be added to the level leaderboard? The level leaderboard would be suitable, as it will not take occupy space from the main leaderboard, especially when the event is gone.
To avoid adding every stage from every event, I would recommend limiting it to 1 stage per event, and normally the most desired stage for farming, since there will be motivation to create a fast auto there.
Proof of concept videos:
- DH-9 Auto:
- RI-8 Auto (by @dragichav):
[quote=Hinabu]I recommend to start and to stop timer with COST bar moving.[/quote]
Just wanna double check I am understanding correctly.
Ok, so start the timer here? [Frame 563]
And the timer should be running already here? I circled the DP bar beginning to fill. [Frame 564]
Then end the timer here? [Frame 1889]
And to not end it here? [Frame 1890]
