EVERNESS ATLASUNOFFICIAL NTE GUIDES & TOOLSOpen My AtlasAtlas

Build a testable team.

A practical method for choosing and comparing your own squad while current recommendations remain under verification.

Status: Usable editorial guide · Recommendation list: In preparation
Source status: Editorial method with source-linked Shinku example · Updated September 11, 2026 · Confidence: High for the workflow; Unknown for named best teams
Repeatable workflow

Turn a team idea into a fair comparison

A useful team guide should explain what to check and how to compare it. Use the same process whether an idea comes from your inventory, a community guide or your own experiment.

01

Read the current client

Record the character labels, skill conditions and activity rules shown on your account.

02

Name one problem

Choose the result you want to improve, such as consistency, clear time or surviving the same encounter.

03

Change one variable

Swap one teammate or one loadout choice while keeping the other test conditions stable.

04

Compare the evidence

Record repeated successful clears, review the median and range, then note what still needs checking.

Character path

Use Shinku without inventing a team list

Read preview labels without promoting current fieldsOriginal Everness Atlas evidence diagram
CONFIRMED PROFILEShinku

The official showcase confirms the character identity and introduction.

OFFICIAL V1.2 PREVIEWCosmos

Attribute label shown on the dated preview card.

OFFICIAL V1.2 PREVIEWCondensate

Compatible Arc label shown on the same dated card.

CURRENT CLIENTUnknown

Capture the active field labels before Team Builder promotion.

Sources: official Version 1.2 card · 17:32 and official character showcase. Preview labels are historical, not a current-client record.

The official Version 1.2 preview card identifies Shinku with the Cosmos attribute and Condensate Arc compatibility. A separate historical in-game panel also labels her Main DPS, but Atlas has not verified those labels against the current Version 1.3 client. Start by checking the same fields in your own client.

Current boundary: the available records do not support named teammates, a best-team ranking or a prescribed rotation. The example shows how to continue productively while those claims remain unverified.

Before each run

Keep the comparison readable

  1. Use the same encounter, difficulty and target whenever possible.
  2. Keep character levels, skill levels and equipment upgrades unchanged unless that is the single variable being tested.
  3. Record at least three successful clears for each setup; do not hide failed attempts in your notes.
  4. Compare median clear time and range. A single fastest run does not show consistency.
  5. Write down control mistakes, interruption or other conditions that made a run non-comparable.

This method can compare two setups on your account. It does not convert clear time into universal damage rankings or prove that one team is best for every activity.

Continue the loop

Move from reading to your own evidence

When will named teams appear?

Atlas will add named team suggestions only after the relevant character fields, combat behavior and team-rule evidence can be traced to current sources or controlled observations. Until then, use community lists as hypotheses to verify in your client, not as guaranteed rankings.

Changelog

September 15, 2026 — Replaced the Shinku preview frame with an original evidence-boundary diagram; named-team fields remain Unknown.
September 11, 2026 — Replaced the internal recommendation-contract screen with a player-facing team testing guide, Shinku content path and direct tool handoffs. Named teams, rankings and rotations remain unavailable pending current evidence.