ManYue fictional timetables: record arrival, departure and midnight dates separately

A smaller clock number after midnight does not mean time moved backwards. Use a fictional three-stop table in ManYue to align dates, arrival/departure columns and elapsed time. This differs from reading calendar dates or reconstructing flashbacks and supplies no real service schedule. Different time zones or clock changes require their own stated conditions rather than this simplified calculation.

Read headers and applicable dates before subtracting times

Record work, edition, chapter/page and table title, then check 24-hour notation, date, time zone and arrival/departure headers. Weekday or date-only operation is a condition of the fictional table, not proof of availability on the character’s current day. Mark missing date or zone unknown instead of supplying today’s device date. Retain service, direction or session identifiers so columns from different runs are not combined. Our three-stop example assumes one time zone and no clock change; every later calculation carries that assumption explicitly.

Write each time as a date plus clock reading

The original table departs the origin on day D at 23:50, arrives at the middle stop on D+1 at 00:05, departs there at 00:08, and reaches the terminus at 00:20 on D+1. D is a practice-date symbol, not a real date or app field. Give all four entries full dates and arrival/departure roles rather than retaining only minute numbers 50, 05, 08, 20. Midnight starts a new day: 00:00 here means the beginning of D+1, avoiding ambiguous “midnight tonight.” For another notation, follow its explanation and retain the original form alongside any conversion.

Split a midnight-crossing duration into two intervals

From 23:50 to next-day 00:20, count ten minutes to midnight and twenty afterwards, totalling thirty minutes. A negative clock subtraction does not establish an erroneous table. Alternatively use one continuous minute axis: departure is minute 1430 from the start of D and arrival minute 1460, differing by 30. Both calculations require the same date assumptions. Without dates, thirty minutes is only a next-day candidate; a longer intervening day or a different service cannot be excluded solely from clock readings.

Calculate dwell separately from total elapsed time

The middle stop’s 00:05 to 00:08 dwell is three minutes. Origin-to-middle takes 15 minutes and middle-departure-to-terminus 12; 15 + 3 + 12 remains 30. Total elapsed time includes the stop, so do not call all 30 running time or add the dwell again to get 33. With an arrival but no departure, dwell remains unknown; one dialogue panel does not establish three minutes. Match arrival and departure to the same stop and service before subtraction instead of combining a terminus entry with another column’s departure and obtaining a plausible but incorrect interval.

Use the legend for missing entries and special symbols

A dash may mean no stop, unavailable data or another convention; a blank does not automatically mean midnight. Read table notes and symbol definitions, marking unresolved meanings explicitly. An origin listing departure only does not require an invented arrival, and similarly for a terminus. Determine whether a footnote applies to one column, one entry or the whole table from its markers. Dialogue about catching the last service does not establish that this particular column is the last; check headers and notes. Record missing information rather than supplying a definite schedule from a character’s motivation.

Do not equate matching clock readings on different dates

In one control, move the terminus date to D+2 while retaining 00:20. Under the same-zone, no-clock-change assumption, elapsed time becomes 24 hours 30 minutes, not 30 minutes. In another control, move middle departure to 00:18: only two minutes remain to the terminus, while total elapsed time stays 30. This distinguishes internal allocation from total duration. Keep controls separate rather than changing both facts and confusing their effects. Real narrative time-zone or daylight-saving changes need the relevant dates and local rules; this simplified subtraction does not replace that conversion.

Troubleshoot cropped columns and copied time digits

If a table spans pages or a crop retains only numbers, return to the full page for stop names, service and arrival/departure columns rather than inventing headings at the crop edge. Enlarge zero/eight and colon/decimal-point distinctions: 23:50 is not 23.5 hours. Searchable text may lose cell alignment, requiring checks on the pictured table. If zoom moves labels off-screen, identify the full table again; moving the viewport is not a column change. Preserve source-versus-copy differences with locations instead of editing the original or treating display uncertainty as the author’s arithmetic error.

Exit and return to check the full arrival-departure chain

Exit the reader and return. Relocate all four times and dates, then recalculate the thirty-minute total and three-minute middle stop without looking at previous answers. Check that 15, 3, 12 sum correctly and explain why the two controls change different results. Save six fields: table identity, applicability conditions, stop/service, complete time, calculation and unknowns. Completion means the fictional schedule and reading conclusion are traceable; fiction or an old pictured table must not guide real booking. A real journey needs current official arrangements separately. This article supplies no current services or guaranteed connections.

Related guides and sources

ManYue: Read in-story calendars by separating date cells, weekdays and story time; ManYue flashback timeline: separate presentation from event order.

Checked on November 10, 2026: Apple public version information lists ManYue 2.0.5, requiring iOS / iPadOS 15.0 or later. See the official App Store for feature descriptions; specific controls must still be checked in the installed version.

Method reference: NIST: time-of-day and midnight notation. Numbers, short passages and controls are original exercises. Sources explain concepts rather than prove automatic recognition or grading in the app. Manual notes may be kept externally. This article does not claim step-by-step testing on a physical device or private server; unresolved content should remain marked for review.