External tracking and chapter mapping

Map split ManYue chapters to a tracker: upper and lower parts versus one complete chapter

Build a manual chapter-to-story map before checking tracker units so an unfinished chapter is not mistakenly synchronized as complete.

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

Build a manual chapter-to-story map before checking tracker units so an unfinished chapter is not mistakenly synchronized as complete.

Choose a work with different chapter splits

Choose a comic you may read whose exact entry you have located in ManYue and Bangumi or MyAnimeList. For this manual example the local source splits one chapter into upper and lower parts while the remote entry counts a complete chapter. This is an illustration, not a claim about a particular work or platform. Record title, author, language edition and current position. The store lists external tracking under Ultra; entries and entitlements depend on the current version. Without access or an account you can prepare only the paper map.

Record the original position on both sides

In ManYue record the current chapter name, page or recognizable story anchor. In the target platform’s own account page record entry name, current progress and date. Do not write only two numbers, which may use different units. Inspect existing binding and synchronization state; if automatic sync is active and the current interface lets you pause it, record its previous setting and pause while comparing. If the pause entry or automatic behavior cannot be confirmed, make a read-only record and stop binding, syncing and further reading that may trigger a write. Record any change already observed and continue only once doing so is confirmed safe; do not assume a switch exists.

Check work identity and chapter splits separately

First confirm the local work and remote entry correspond to the same original, not an anime, spin-off, another translation or collection. List actual chapter labels in two columns: for example local chapter seven upper and lower might correspond to a complete chapter seven remotely. Verify against opening scene, ending and publisher information. If evidence is insufficient, mark the remote mapping unknown rather than binding by similar numbers. Whether extras count in the main sequence depends on the actual entry; do not simply add one by order. If the remote entry lacks chapter details, do not invent counts in a public catalog. Record available evidence and gaps, then compare again once the content can be confirmed. The personal map is for this reading session and does not alter the source’s chapter structure.

Preserve the boundary of an unfinished chapter

If only the local upper part of chapter seven was read, write “upper read, lower unread” in the manual map and record the previous complete chapter’s ending. Do not claim the platform supports fractional progress or automatically mark remote chapter seven complete. Before syncing, inspect the units and meaning the platform actually offers. If it only accepts whole progress and mapping is unclear, leave synchronization pending until the lower part is read or clearer chapter information is available. A personal note can retain the partial position but is not a platform field.

Verify binding and local target

For an existing tracker binding, inspect the local work and remote entry in the binding management actually visible in ManYue. If not bound, use the actual interface only when title, work type and edition evidence are sufficient. Authorization should use the platform’s normal page; never record passwords or tokens. A successful binding establishes a relationship between records, not proof that the system understands split content or synchronizes page positions. Stop when the entry is unavailable or identity cannot be confirmed; do not choose a near match to finish the exercise.

Read the mapped unit before comparing

Only after pausing automatic sync or confirming that further reading will not trigger an unwanted write, finish the lower local part corresponding to the example remote chapter, checking the connection and ending, then update the manual map with actual status. Do not count local list entries as complete chapters or skip content to reach a remote number. Revisit the platform, observe whether its prior progress changed and record actual changes and time. If automatic sync cannot be controlled or confirmed, stop at the earlier read-only record. If the lower part is missing or correspondence remains uncertain, keep it pending and do not send a guessed value.

Sync once only after confirming the units

Only when account, binding, mapping and intended result are clear, and the current version actually offers manual synchronization, follow the interface and observe success or error. Then check the same account and entry on the platform against the recorded state, not merely the app message. If synchronization cannot be limited to this work, inspect other bindings and decide whether to continue; stop at read-only checks if the scope is uncertain. For an unexpected advance or wrong entry, pause further synchronization and correct using the platform’s actual process; unbinding does not automatically undo a write.

Keep the map and previous settings

Keep date, app version, source, remote entry, evidence for the split-to-complete mapping, observed values on both sides and whether sync was performed. Do not publish private account data, tokens or comic pages. Restore prior automatic synchronization only as appropriate; keep it paused while uncertainty remains. Reopen the local work to confirm the story anchor and position, then check the remote outcome. Mark unperformed synchronization untested. Completion means the unit and verified boundary of each number are clear, not forcing both sources to display the same number.

Connect and bind a tracker; Map position when changing source.

Checked 20 November 2026: Apple lookup lists ManYue 2.0.6 and iOS / iPadOS 15.0 or later; tracker entitlement is in the App Store. The official Bangumi documentation lists subject and episode progress; the mapping is an illustrative manual example, not a claim that the app supports half-chapter progress. No device or platform synchronization test is claimed.