EVERNESS ATLASUNOFFICIAL NTE GUIDES & TOOLSBuilds
Open the Shinku equipment evidence, compare your own recorded runs, and see what still needs current-client testing.
- 01Preview labels↓
- 02Historical role↓
- 03Current check
Shinku build evidence
Review illustrated equipment evidence and its limits before making investment decisions.
Explore ›- 01Loadout A / B↓
- 023 runs each↓
- 03Compare medians
Compare your loadouts
Enter three clear times per setup. A rough time summary is available before you complete a full test record.
Explore ›- 01Find term↓
- 02Read boundary↓
- 03Open evidence
What is still missing?
Review the source and combat checks needed before Atlas can make a current build recommendation.
Explore ›Choose the reference that fits your question
Not sure where to begin? Read how Atlas build pages work before treating evidence, personal notes and comparison results as the same thing.
Understanding an item? Start with the equipment-panel reading example. For character identity and preview mechanics, use the Shinku profile.
Recording a setup? Save the details in the Build Notebook, then keep the encounter and other conditions consistent when entering observations in the comparison tool. A faster recorded run alone does not establish a best build.
Looking for a team recommendation? Team Guides is still in preparation.
How we verify build advice — current evidence status
Identity is not build advice.
Official names and patch context can stage routes, but public build recommendations need combat and source evidence.
Blocked until character data and build sources existBlocks public build pages until the character is promoted from intake.
Requires: characterId, sourceIds, confidence, lastUpdatedBlocks stat priority, rotation, and role copy while combat profile fields are missing.
Requires: combatProfile, roleEvidence, sourceIdsBlocks build recommendations when source records only support identity or patch context.
Requires: statPrioritySource, gearSource, versionLabelAllows version labels, but blocks converting patch notes into build advice.
Requires: versionArchive, buildSpecificEvidenceNo build advice until sources can carry it.
Stat priorities: No build-specific source record supports public priority order.
Best weapons or gear: Gear advice would imply verified combat testing that is not present.
Character rotations: Combat profile fields are still missing in the current character audit records.
Build rankings: Ranked build output needs verified character records and build sources first.