ManYue reader-preference rollback: record values before clearing overrides

English translation of the Chinese original, translated on 2026-10-27. Original publication dates, attribution, code and version notes are retained.

Unexpected scrolling or image counts can come from old reader overrides. Establish a working reference and record values before clearing a book or device scope. Reader-preference clearing concerns presentation, and its current prompt must be distinguished from deletion of comics or application data.

Establish the affected scope

Compare the problem book with a working reference, keeping file identity and scene fixed. One affected book suggests its override; several call for device or general-scope inspection. Note recent changes without assuming causation from timing alone. Establish scope before restoring broad defaults.

Record values and a return point

Record mode, orientation counts, scope switches and relevant gestures without exposing account details. Keep a chapter, scene and working bookmark, and test menu access. This settings note helps reconstruct preferences but is not a complete backup of comics or reading records.

Disable the override before deleting values

Disable the book override temporarily and inspect the same scene. Improvement narrows the issue to the override; no change calls for checking defaults and mode conditions. Disabling is not proof of deleted values. Preserve this comparison and note an unsuitable default separately rather than repeatedly toggling without observations.

Clear only the identified book scope

Use the current clear-this-comic reader-preferences control only after identifying its scope. Avoid comic deletion, local-copy cleanup or data restoration flows. Inspect values and behaviour afterwards. If the control is absent, check context and stop with the temporary-disable result rather than choosing a broader similarly named action.

Consider the device scope only when justified

Inspect device overrides only if several books remain affected after book-level checks. Record local values and compare disabling before clearing. Keep another device unchanged where useful. A reset cannot be assumed to reconstruct an old personal configuration; its purpose is an understandable baseline from which to rebuild justified differences.

Verify three practical actions

Test forward/back, menu open/close, and zoom/restore, then reopen the entry. Rebuild a necessary book override one value at a time instead of copying the entire problematic combination back. Verify the actions actually affected rather than treating one successful page turn as proof of every reader operation.

Check content and records independently

Reopen the recorded bookmark and inspect content availability separately. A preference rollback is not a full file-integrity audit, and one working bookmark does not validate every download. State the limited successful result. If a scene differs, check identity and content changes rather than expanding reset scope blindly.

Acceptance and the retained record

Finish with a stable repeatable baseline, recorded old values and an identified or narrowed scope. If behaviour persists, retain reproduction steps, version and mode rather than uninstalling first. Use the book/device/general sequence to investigate, not as an instruction to reset all three every time.

ManYue per-comic preferences: change one vertical comic without changing others; ManYue device preferences: keep distinct phone and tablet controls.

Checked on October 27, 2026: ManYue public version 2.0.3 requires iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. Reader options depend on the installed version and current context. This article describes a checking workflow without claiming step-by-step physical-device or private-server testing, or treating development features as released capabilities.