Back Up and Restore Your Drip Client Settings Without Tears
The blank sensitivity screen after a reset has ended more tuning journeys than any opponent. Yet losing a setup is entirely optional: it survives wherever a two-minute habit exists. This guide assembles the full Drip Client backup system — the written record, profiles with assigned jobs, and a restore routine built for the reality that new hardware changes the feel of old numbers.
One axiom organises everything below: a backup must live outside the thing it protects.
The Written Record Is the Backup
Transcribe the screen: general, red dot, 2x, 4x, sniper scope, free look — with the date, the device name, and any DPI or display modifications you run. Keep it where phones cannot take it: a synced note, an email to yourself, paper that outlives handsets.
Refresh it whenever a change passes its three-session audit; a stale record restores an abandoned experiment instead of your aim. The audit that should trigger each refresh is defined in our training testing guide.
Profiles With Assigned Jobs
Where profiles exist, conscript them properly: main device, second device, and one experiment slot where candidate changes audition without endangering the proven setup. Name by role and date — labels are for the future self who will not remember context you currently find unforgettable.
The experiment slot is the working heart of disciplined tuning: promotions into the main profile are earned in drills, never granted by enthusiasm. That philosophy is argued fully in our client versus manual comparison.
Restoring Onto New Hardware
Install, enter the recorded values exactly, reinstate your DPI choice if you had one — then recalibrate rather than assuming victory. Identical numbers feel different on different geometry; run the two-distance drag test, adjust the ladder's level while preserving its internal spacing, and record the result as a new device entry.
Observe the asymmetry that justifies the whole system: with a record, migration is an afternoon of fine adjustment; without one, it is archaeology. The physics behind the shift is our phone size and DPI guide.
Anchor the Habit to Updates
Tie record-checking to an event that already recurs: app updates. Sixty seconds comparing record against screen, each update, catches drift at the moment it is likeliest and cheapest. Our update guide embeds exactly that checkpoint into its routine, for exactly this reason.
Final Thoughts
External record, job-assigned profiles, restore-by-recalibration, audit at every update. Two minutes at a time, a few times a year — the entire premium on insuring weeks of work against one bad afternoon.
