How to Submit
Clears can be submitted after signing in and clicking on the Submit Teams button on the Clears page
Submission Criteria
- Correctly choosing the boss, difficulty, and version as some bosses appear in multiple versions.
- Provide a valid direct public link, more information available below. We accepts YouTube, Bilibili, or other links, and the Check button looks for duplicates already tied to a clear or pending submission. Clears from TikTok and ones without a video will not be accepted.
- Fill your team's information with the correct character constellation and weapon refinement.
- Cost is calculated automatically from the team you enter. Some clears are eligible for a Cost Reduction, more on that below.
The Quick Add also supports shorthand such as C0R1 Mavuika or C2 Mona R5 TTDS to more efficiently fill out the information.
How to use Tags
Tags are short labels that explain what is notable about the run. They help viewers gain an overview about the clear, but reviewers still decide the final approved tags.
- You can suggest up to 3 normal tags when you submit. Reviewers can keep, remove, or change them.
- FPS tags such as 30 FPS, 60 FPS, and 120 FPS describe the framerate shown in the proof.
- Ping tags such as High Ping, Low Ping explain ping conditions. Generally High Ping is red pings and Low Ping is green pings.
- Ping Dependent should be used for clears where pings can affect the outcome of the clear.
- Tool and execution tags such as FPS Unlocker, 3rd Party Tools, Macro, High CPS, and Hard Combo flag hard to achieve inputs or outside assistance.
- Cheese should be used for clears that used unconventional methods to clear.
- Over Level is used if any of the party members are above level 90.
- Reduced Cost is used to reduce the cost of a clear, eligibility is explained below.
- No Builds indicate if builds are not included in the video, builds in the description won't count.
- Build Images is used to tell Reviewers that you showcased your builds via images like akasha or artifacter, more information below.
Only suggest tags that are clearly shown or obviously relevant. Wrong tags slow review and are not guaranteed to stay on the final clear.
Cost Reduction
- Use this tag to reduce the cost of your clear. Enter the intended cost instead of the actual cost. Ex: if C1 Yelan isn't used then input C0 Yelan
- Only constellations and refinements that are generally useless, contributing less than 1 second to the clear, or is not used will be eligible for a reduction.
- 5 star weapons with useful effects will not count for cost reduction.
- 120s clears are not eligible for cost reduction that contributes to ANY amount of damage.
- The availability of a character through rewards such as the Anniversary or the 5 star Selector will NOT be taken into consideration for cost reduction.
- Standard 5 star characters will NOT be reduced to 0 cost.
- Cost reduction is only available up until a useful constellation. Ex: C6 Mona can be reduced to C4 Mona but no further.
- Obvious cases will be proved by the reviewer, such as reducing R2 Aquila Favonia to R1 on Bennett. However, for less obvious cases, a prior notice should be given through Discord. Otherwise, it will not go through.
Queue Priority
- Typically a clear goes into the regular queue that takes about 1 day to be reviewed.
- Using the Build Images Tag moves the run into the prioritized queue.
- Build Images does not count toward the normal 3-tag quota.
- ONLY use Build Images when the video really shows build images, such as Akasha or Artifacter screens.
- Misusing Build Images can send your next 5 submissions to the low priority queue.
- Qualified users will enter the automatic queue, more information below.
How To Become A Qualified User
Qualified users enter the automatic queue. To qualify, you need more than 20 approved clears and a 95% or higher strict approval rate.
- Strict approval rate only counts submissions marked Approved. Approved with Edits still appears in your profile stats, but it does not help the qualification threshold.
- The easiest way to qualify is to submit accurate runs consistently: correct boss, boss version, correct character and weapon info, clean public links, and tags that match the proof.
- Avoid preventable denials and edits. Repeated mistakes lower your strict approval rate and delay qualification.
- Automatic queue is still managed manually by the reviewer but it will always be approved.
- All clears in automatic queue still counts toward the "Strict Approval Rate" as an approved clear. However in cases where a clear gets reported and changed then its status will be changed to "Approved with Edits", thus lowering the strict approval rate.
Review Status and Statistics
- Pending means the run is waiting in the review queue.
- Approved means it was published.
- Approved with Edits means the run was published, but a reviewer had to manually fix something like boss, difficulty, time, link, weapon, refinement, constellation, etc.
- Denied means it was rejected and the reviewer will leave a note to explain why.
- Success Rate = (Approved + Approved with Edits)/Total
- Strict Success Rate = (Approved with Edits)/Total
Video Criteria
- Video must be available and public at all times.
- Video should not be shortened or have any parameters. Otherwise it will have an Approved with Edits status.
- Standard YouTube format: https://www.youtube.com/watch?v=f9xuJElsst0
- Standard BiliBili format: https://www.bilibili.com/video/BV1Czu5zsEZE/
- Videos should either be on YouTube, Bilibili, or another source and should be marked correctly.
- If the video source is not from a well-known domain then it will be rejected.
- TikTok videos are no longer accepted.
Common Slowdowns
- Wrong version on bosses.
- Videos that take too long when flipping through pages.
- Character, weapon, constellation, or refinement data that does not match the run.
After you submit, open Profile > Submissions to track whether the run is Pending, Approved, Approved with Edits, or Denied.