Arknights: Endfield Essence Tracker
Pick the weapons you want Flawless Essences for, and the tracker lists the Severe Energy Alluvium engravings that can drop the most of them.
Open the Essence Tracker
Preview
Weapons and engravings
Engraving details
How to use
- Click weapons to cycle Track → ★ Priority → Skip. 4–6★ weapons start tracked and 3★ weapons start skipped.
- The Engravings list ranks each location's engravings by how many priority weapons, then tracked weapons, they can drop. Once anything is starred, only engravings that can drop a starred weapon are shown.
- Each row shows the 3 attributes to engrave and the stat to fix. An any slot means every choice there drops the same tracked weapons.
- Click a row to see, per weapon, which rolls it still needs.
Hover a weapon, or long-press it on a phone, for its skill and signature operator.
- Under Locations, hide areas you haven't unlocked.
Engravings that only differ in untracked outcomes are merged into one row, and rows that are strictly worse than another row at the same location are dropped.
Weapons that are announced but not yet released are tracked like the rest, so their essences can be farmed ahead of time. They carry an Announced tag, a striped rarity edge and a dashed outline, and their stats come from preview game data that can change before release. The rarity filters cover released weapons and the Announced filter covers announced ones, so turning off every rarity shows only announced weapons; Skip shown then drops them from the results.
Development
The site is plain static files with no build step. Development tooling needs Node 22+.
npm install # Playwright and its headless Chromium, for browser tests and screenshots
npm run serve # http://127.0.0.1:8000/ (data.json is fetched, so file:// won't work)
npm test # solver, sync, deduction and data tests
npm run test:e2e # browser tests in Playwright's headless Chromium
npm run previews # regenerate the README screenshots
npm run sync # update data.json and icons from game data
Data
data.json is generated from the datamined game data published by cmyyx/cep: weapons, their English names and skill text, the stat names, signature operators, and each Severe Energy Alluvium location's attribute, secondary and skill pools. Weapon icons in images/weapons/ and operator portraits in images/operators/ come from the same source; the sync removes any it no longer references.
- Weapons, locations and stats are keyed by game id (
wpn_sword_0025, world_energy_point_group13, gat_passive_attr_atk), and stats maps each stat id to its in-game name. Saved selections are keyed by id, so renames don't lose them.
npm run sync reads every file from one cep commit, recorded under source, and prints what changed. node tools/sync.js --dry-run previews the changes without writing.- Weapons cep links to a signature operator (most limited 6★ weapons and a few 5★) list it under
operators, with its character id, English name and portraits. Operators cep's character tables don't name yet are looked up in the game's text table from cmyyx/cep-assets. Search matches operator names.
- A weapon cep marks as preview gets
announced: true; the next sync after its release removes it. A weapon or location whose English name changes keeps its old name under formerly, which search and older saved selections still match.
- Nothing in
data.json is edited by hand. A sync that finds an unknown weapon type or a stat without an English name stops instead of guessing.
Deductions
Some answers are in the game data without being linked to the weapon, such as an announced weapon's skill name: the game text can hold exactly one weapon skill name that no weapon uses. tools/deduce.js holds the rules that find these, and the sync fetches the game text only while some data is missing.
The rules only propose. A reviewer weighs each proposal and records a verdict in tools/deductions.json: accepted or rejected, the basis shown to users, and review notes on the evidence and residual risk. The sync then prints:
CANDIDATE: a proposal without a verdict. Nothing is published until one is recorded.REVIEW: a verdict the rules no longer support, because the evidence changed. It is held back until reviewed again.RESOLVED: the game data has filled the gap. The deduction is dropped; compare it with the real data and retire the verdict.
Accepted deductions appear under the weapon's deduced, and the weapon tooltip marks them with an asterisk and a one-line basis.
