Read coordinate paths in ManYue: distinguish displacement from total distance

An endpoint arrow describes a character’s change of position, not automatically the entire path travelled. Read an original diagram with explicit coordinates and straight segments in ManYue, separating position, displacement and distance. Units come from the problem, not phone pixels or real character measurements, and no map-measuring or automatic trajectory feature is required.

Establish axes and the specified route

Record work, edition, page, panel and legend. Let right be positive x, up positive y and each grid unit one schematic length unit. The original route visits (0,0), (3,0), (3,4) and (0,4) in order, with explicitly straight segments and no hidden detours. Arrows indicate travel order, not wind or gaze. Two endpoints in a real work do not establish this polyline. Separate known endpoints from unknown travel; a missing segment prevents claiming the full distance.

Keep both coordinates at each turn

Pair the coordinates point by point: zero/zero, three/zero, three/four and zero/four. Do not join one point’s x with another’s y into a fictitious location. Screen rotation does not change the source axes; if the page is mirrored, check labels rather than permanently equating screen-left with negative x. Add a visual or textual anchor to each turn so the list remains locatable, not just four numeric strings. Establish coordinate identity before discussing speed or time.

Add non-negative lengths of the given segments

The segments go right three, up four and left three, with lengths three, four and three, totalling ten units. Leftward motion makes the x change negative, not the segment length negative to cancel the earlier three. Axis-parallel lengths are absolute coordinate differences. Diagonal or curved segments require their own stated geometry; do not universally add horizontal and vertical differences. Distance depends on the route, not just the destination, and is not estimated from panels, character steps or reading time.

Subtract endpoints and retain displacement direction

Final minus initial position gives x change zero and y change four: displacement is four upward, magnitude four, not ten and not a destination three right and four up. The x changes cancel in displacement but both horizontal segments count toward distance. Keep the vector and magnitude separately; a non-negative four alone does not state direction. Units remain schematic without a real scale. With no time supplied, do not compute average velocity or speed by silently assuming one second.

A return can have zero displacement and nonzero distance

For an external control, add a straight downward segment of four back to the origin. Distance increases to fourteen while displacement becomes zero. That does not mean no travel occurred, nor does zero displacement uniquely imply fourteen: remaining still or other closed routes also give zero. List the added segment separately and label it a control, not a later event in the work. Without a depicted return, do not replace the main sample’s ten by your invented fourteen. Keep the variant and its changed condition identifiable.

Use a same-endpoint shortcut to test dependence

Create another route directly upward from the origin to the original endpoint. Its distance is four and displacement remains four upward. Matching endpoints with different distances show that displacement does not uniquely determine travelled distance. Equality here follows from a straight non-reversing route, not proof of an available city shortcut. Obstacles, roads and access are unspecified. A shortest geometric segment is not automatically a usable route, and the original detour is not thereby irrational. Check only the stated coordinates and path.

Check omitted segments and changing coordinate frames

When totals disagree, check schematic curves, omitted travel and changes in origin or scale between panels. Changing origin changes position values; compare displacement within a consistent frame instead of subtracting unconverted coordinates from different systems. If arrival is known but travel is not, leave distance unknown rather than filling it with endpoint separation. Screenshot zoom changes neither stated coordinates nor how far the character travelled. Preserve labels and segment arithmetic to locate the actual disagreement.

Leave and return to compare three routes

Leave reading and return to the main diagram. Recalculate distance ten and displacement four upward from its four coordinates, then fourteen/zero for the return and four/four-upward for the direct route. Keep axes, paired positions, route assumptions, lengths, displacement direction and unknown time or physical scale. Explain why leftward three is non-negative distance but cancels an x displacement. Success separates quantities manually without claiming automatic character tracking or unstated speed, energy, scale or accessibility.

Related guides and sources

Checking scene geography in ManYue: follow movement through visual landmarks; ManYue maps inside comics: read the legend before checking a route.

Checked on November 12, 2026: Apple public information lists ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later. See the official App Store for published capabilities; verify specific controls in the installed version.

Method reference: OpenStax: position, displacement and distance travelled. Samples, passages and controls are original exercises. Sources establish definitions and checking methods rather than new automatic analysis in the app. Manual records may be kept externally, and unknown fields should remain explicit. This article does not claim step-by-step testing on a physical device, private server or every output environment.