The blank sensitivity screen after a reset has terminated more tuning projects than any opponent in any lobby. It is also entirely optional. A two-minute habit renders the catastrophe a clerical errand, and this guide assembles the complete Dark Aura backup doctrine: the external written record, profiles conscripted to defined jobs, and a restore procedure designed for the physical truth that new hardware re-prices old numbers.
One axiom commands the doctrine: a backup must reside outside the thing it protects.
The Written Record Is the Policy
Transcribe the entire screen — general, red dot, 2x, 4x, sniper scope, free look — accompanied by the date, the device's name, and any DPI or display alterations in force. Store the record where handsets cannot follow it: a synced note, an email addressed to yourself, paper with a longer lifespan than phones.
Renew the policy whenever a change survives its three-session audit; a stale record restores an abandoned experiment rather than your aim. The audit that triggers renewal is defined in our training testing guide.
Profiles, Conscripted to Jobs
Where profiles are offered, assign each a commission: principal device, secondary device, and one experiment chamber where candidate changes audition without imperilling the proven configuration. Name by commission and date — future-you, stripped of today's context, will be grateful for labels that explain themselves.
The experiment chamber is disciplined tuning's working heart: promotions to the principal profile are earned in audited drills, never conferred by enthusiasm. The philosophy receives its full argument in our panel versus manual comparison.
Restoration Onto New Hardware
Install, transcribe the recorded values exactly, reinstate any DPI election — then recalibrate rather than declaring victory. Identical numbers conduct themselves differently on different geometry: run the two-distance drag audit, adjust the ladder's level while conserving its internal spacing, and file the outcome as a new device entry.
Ponder the asymmetry that justifies the entire doctrine: with a record, migration is an afternoon of fine adjustment; without one, it is archaeology conducted from memory. The physics of the shift is our phone size and DPI guide.
Anchor the Audit to Updates
Bind record-verification to an event that recurs without your remembering: the app update. Sixty seconds reconciling record against screen, per update, intercepts drift at its likeliest and cheapest moment. Our update guide embeds precisely that checkpoint in its procedure, for precisely this reason.
Final Thoughts
External record, commissioned profiles, restoration by recalibration, audit at every update. The premium is minutes, a few times yearly, insuring weeks of accumulated work against a single bad afternoon. Pay it gladly.
