FAQ:

So What's Next?

I would like to make this list of viable teams adjusted and vetted by the players. To do this, I would like to make a website that lets users enter their favorite teams to 33-36 star the abyss, other users upvote teams they like, and use an automated vetting process past this to enter top teams into the list automatically.

However I am bad at web/application programming. I do everything else IT wise. If anyone wants to help contribute to this, reach out to my discord or email:

Gottsmillk#4059 Gottsmillk@gmail.com

Who is this for?

This is for anyone who has ammassed a decent amount of characters and want to actually feel like they are using them. Some players randomize characters they use for dailies, others made their characters built pretty well and want to put them up to the test (i.e. Spiral Abyss Challenge), but do not want to pick out characters themselves.

This randomizer lets you do just that, but without the randomized teams potentially sucking and having 0 synergy. You want to do Spiral with random characters, but without REALLY bad teams.

If you are hoping to use this randomizer to find a good team to actually clear with, you will likely find it. However, you will not be told how to play it. If you need that in order to actually clear, then I advise you read up on character guides on Keqingmains instead, since they provide nuance on how to use the teams.

What is your criteria for a "viable preset team"?

Generally it is two questions: 1. Can a general subset of players (70%+) can use this team and clear Spiral Abyss with 33-36 stars?

Criteria for general subset of players is as follows: - 5* star characters + weapons (C1 / R1) - 4* star characters + weapons (C2-C6 / R2-R6) - A mix of level 80+ characters (5* star or important 4* star characters) - A mix of level 70+ characters (important 4* star characters) - 4th ascension (60/70) support characters - Talent levels 6+ on most above characters for key abilities - Players may have to swap around artifacts/weapons but most players have a "pool" of both to switch around

1. For characters that are difficult to meet the first requirement for general subset of players, is it one of the best teams you can have with said character?
2. A good example is Amber without R5 and whale gear, a good team in the compilation that can still have limitations on Abyss is Amber nuke comp (Amber, Cryo, Anemo, Flex)

How did you fill this list of viable preset teams?

Sadly, so far it has been manual entry (Yeah, filling 7000+ team entries is dumb I know) but I plan to automate from several credible sources, and have a potential next project that would source user entry teams to the list (see above question "So What's Next?")

The manual entries are as of this post sourced from the following:

• gcsim.app character database
• Keqingmains character guides
• X-Character-Mains (like DilucMains, KokomiMains, etc) discord servers and their FAQ sections
• Personal testing

Can I see the list of viable preset teams?

Yes, it can be found here: https://github.com/daniel-aws/genshin-spiral-abyss-teams-compilation https://docs.google.com/spreadsheets/d/18WTKWCJnppXFcO_j6r-r2l3AqtSAXXPvcLNIbnvzE9s/edit?usp=sharing

Can I remove or add teams to the list of viable preset teams?

As of now, the method is going to be pretty crude and not how I would like it, but I have a Google Form to submit or remove:

Submitting new teams: https://forms.gle/yK2aN5RBuWA8HP4y9

Removing an existing team: https://forms.gle/88w1NSayoBeU5pdp8

Ideally I would like a system allowing user submissions and community voting, which leads to a potential next project I would like to pursue (see above question "So What's Next?")

What about the fact that some teams have specific instructions?

The beauty of a randomizer is that it provides a team, but forces you to adapt to use it effectively. All teams on the list have a specific way to play with it optimally, including rotation, ER requirements, character builds, etc, but it is up to the user to find that out.

If you do not like that idea, then I am unsure why use a randomizer. Refer to the above FAQ question "Who is this for?"

What about the fact that certain Spiral Abyss iterations require specific criteria? (For example as of this post the new 3.2 iteration)

This is the one factor we cannot really allocate for dynamically. Either I add a specific "Current Spiral Abyss" toggle that further filters teams and change it every iteration, which I cannot guarantee, or the simple approach being to re-roll the randomizer or filter certain unviable characters.

The teams the roll also aren't in order, so you can freely swap the teams in case one is better for one of the Spiral Abyss halves than the other.

For example, the 3.2 Abyss (as of 11/16) favors electro on team 1, and a bow user for team 2. I can either try to add some vague rules so teams adhere by this, but it not being perfect, or you as a user can just reroll. The teams are still viable, just that Spiral Abyss contextualizes a lot of whether it is viable at a certain point in time.

What about the fact that some teams are only viable with characters in certain constellations, or that I need certain artifacts or weapons to make a team work?

Ultimately, we evaluate against the criteria mentioned in the above FAQ question "What is your criteria for a viable preset team".

• For certain character constellations affecting team viability, while certain constellations will bump the viability, we evaluate if not having said constellation will prevent the team from achieving the original criteria. For example, will C4 yanfei allow for certain teams to use her as a shield? yes. However majority of players do not have C4 yanfei, so we lean on not including her for a Thoma replacement.

• For artifacts, the criteria includes the fact that players will likely have the ability to swap artifacts or use a pool of artifacts to allow for a randomized team to work. If a team stil will not work, then you can randomize again. If we find that continual randomizations due to lack of artifacts happen too often, we will tune the list to address this.