# ManYue flashback timeline: separate presentation from event order

Language: en
Canonical: [ManYue flashback timeline: separate presentation from event order](<https://allluckly.cn/en/guides/manyue-flashback-story-timeline/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-flashback-story-timeline/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-flashback-story-timeline/>)
Published: 2026-11-04T00:00:00+08:00
Modified: 2026-11-04T09:36:55+08:00
Author: Bison

Build a recoverable flashback log from time words, character states and scene evidence, retaining uncertain dates rather than treating reading progress as story time.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-flashback-story-timeline/>), translated on 2026-11-04. Original publication dates, attribution, code and version notes are retained.

The first event shown in a comic may not happen first. When reading memories, dreams or an opening set years later, keep a short external timeline alongside ManYue. This exercise separates presentation order from story chronology within one passage and produces an evidence-based sequence. It does not reorder the comic through filenames or present a manually inferred chronology as an automatically generated timeline.

## Choose an already-read passage with a time shift

Choose a completed short chapter that includes both sides of a transition, and record edition and boundaries. Start with three to six events rather than cataloguing every panel in a long series. Read it intact and label events A, B and C in presentation order, with chapters and visual landmarks. Resolve missing pages or doubtful file order against the source first: a deliberate flashback and a misordered file are different problems. Initially describe what happens without forcing exact dates.

## Record explicit time wording accurately

At each transition, look for wording such as “three years earlier,” “the next day” or “back in the present,” and identify the event it modifies. In an invented example, A is a post-graduation meeting, B is enrolment three years earlier, and C is the next day; those relative relationships suffice without inventing a calendar year. Quote only wording actually present and separate calculations. Attribute dialogue-based dates to their speakers. When wording is absent, mark it unspecified; a darker background alone does not establish a memory.

## Cross-check order through changing states

Check injuries, intact or damaged buildings, and whether characters know each other. Attach state changes that support an ordering. Identical clothes may be uniforms and younger appearance may reflect drawing style, so seek another independent clue. An intact object in B and a broken one in A can suggest B is earlier, but cannot alone exclude repair or a second similar object. Retain alternatives and update when later text resolves them rather than treating a familiar storytelling convention as drawn evidence.

## Write a second sequence without rearranging the book

Beside the log, write the currently supported story order, such as B–C–A, annotating each relation with its wording or state evidence. Leave incomparable events parallel or uncertain instead of forcing a precise line. Keep the original presentation order to discuss why A was disclosed first. Continue reading the original sequence; do not rename archive pages or reconstruct the comic for this notebook. A personal study card needs event labels and return locations, not a chapter of copied images presented as another edition.

## Keep dreams and memories in a separate narrative layer

For testimony, dreams or imagined futures, record whose account it is and its entry and exit points. It may show a believed past without confirming an objective event. Keep that layer apart from the present and allow an unknown label. If an account is later disproved, retain the earlier record because it explains information available to the reader then. Keep conflicting memories with their sources until the work supplies distinguishing evidence; a bookmark label should not decide which is true.

## Create return references for entry and exit

Bookmark pages near both entry and return where supported, then leave and test returning. If bookmarks are page-level, add panel position and a recognisable image description externally. On tall images use nearby objects and actions as well as progress. Pair the two references in your own document if remarks are unavailable. After changing device or edition, verify both still identify the transition; matching chapter names do not establish unchanged boundaries.

## Check the order with a reverse explanation

Hide presentation order and retell the events chronologically, checking each relation against the pages. Then ask why the later event was shown first: perhaps to withhold a cause, foreground a result or follow a viewpoint. Label that as interpretation with support, not an authorial statement. Remove or flag any invented year or action needed to make your retelling work. The chronology may remain incomplete, but every established relation should have recoverable evidence.

## Resolve mistaken transitions and finish the log

A changed frame style is not sufficient proof of a flashback; inspect adjacent wording and the exit. Seventy-percent reading progress is a file coordinate, not a late story date. If the timeline forms a contradiction, check what each relative date is relative to and whether narrative layers were mixed. Finish with presentation order, story order, evidence and unknowns, removing vague summaries without locations. Date later revisions and state why they changed, retaining the original question so the log explains how understanding developed.

## Related guides and sources

[Reading wordless comics in ManYue: separate action order from causal inference](<https://allluckly.cn/en/guides/manyue-wordless-action-chain/>); [ManYue bookmarks and notes: save a page and return to the right place](<https://allluckly.cn/en/guides/manyue-page-bookmarks/>).

Checked on November 4, 2026: [Apple public version information](<https://itunes.apple.com/lookup?id=6753895889&country=cn>) lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the [official App Store description](<https://apps.apple.com/cn/app/id6753895889>) and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual lists, external tools and actually visible controls are identified separately. Code observations do not establish verified behaviour across every release path.