EVERNESS ATLASUNOFFICIAL NTE GUIDES & TOOLSOpen My AtlasAtlas
Illustrated planning guide

Character Planning Workflow

Turn four independent local tools into one repeatable path from a character idea to your own test evidence.

Status: Editorial workflow · Tool behavior checked September 12, 2026
Source status: Atlas product behavior · Confidence: High for handoff boundaries; no game recommendation claims
One useful loop

Move from a question to evidence you can revisit

Each tool keeps one kind of personal record. Connect them when that helps, or open only the stage you need.

01

Roster

Who are you tracking?

Save the character name and your own collection or progress context.

Roster Notebook ›
02

Build

What did you equip?

Record the loadout, visible values, conditions and private test notes you entered.

Build Notebook ›
03

Team

Who did you test with?

Save the lineup, purpose and the strategy or equipment context you want to remember.

Team Notebook ›
04

Compare

What happened across repeat runs?

Test two loadouts with three recorded runs each, then review the median and range.

Build Comparison ›
Original Atlas workflow diagram. The stages organize player-entered records; they do not score progress or recommend a build.
Controlled handoffs

Know what moves and what stays separate

A shortcut copies only the fields named below. Review the destination before saving because every record remains independently editable.

RouteCan moveStays in the source tool
RosterBuild

Character name, when you choose Add or Replace

Collection status, progress, version and roster notes

RosterTeam

One character name into the next open member slot

Collection status, progress, version and roster notes

BuildCompare

Selected player-entered character, version, team and loadout fields

Private test notes and recorded run times

TeamCompare

Compatible version and a visible lineup summary

Strategy notes, equipment notes, character choice and run times

Everness Atlas handoff boundaries, checked September 12, 2026. Copying is always initiated by the player.
Comparison discipline

Hold the test still before reading the result

Keep fixed

Character and skill levels, Awakenings, team, encounter, difficulty, timing points and starting resources.

Change once

Change the single loadout choice you want to examine. Record three successful runs for each setup.

Read carefully

Use median, range and exact runs as descriptive evidence for your account. They do not create a universal damage ranking.

No required funnel

Start at the stage that answers today’s question

The workflow is a map, not a completion score. Use Character Workspace to review counts and move between the four independent tools without exposing their saved contents.

Changelog

September 12, 2026 — Added the illustrated four-stage workflow, exact player-initiated handoff boundaries and fair-test checklist.