1.7 KiB
title, category, tags, contextKey, micro, quickTitle, quickSummary, screenshot
| title | category | tags | contextKey | micro | quickTitle | quickSummary | screenshot |
|---|---|---|---|---|---|---|---|
| Time | Scene Inspector | scene inspector, time, continuity, chronology | sceneInspector.time | Record when a scene happens and how certain that timing is. | Scene time | Scene time helps chronology, age checks, sequence logic and continuity warnings understand when the scene occurs. |
Overview
Time fields tell PlotDirector when a scene happens. Use exact dates when chronology matters, relative time when the draft only needs "later that night" or "three weeks after the funeral", and confidence when the timing is still provisional.
Accurate time helps continuity checks find impossible sequences, age issues, travel gaps and story events that happen in the wrong order.
Time Modes
Exact date-time is best when hours or minutes matter: alibis, overlapping scenes, travel deadlines, injuries, messages, curfews or timed reveals.
Exact date is best when the day matters but the hour does not. This is often enough for birthdays, school days, public events, journeys or multi-day investigations.
Relative or loose timing is useful while planning. "Later that night" may be more helpful than a precise date during early drafting.
The visible date and time fields change depending on the mode. More precise timing gives Timeline, age checks and continuity validation stronger evidence. Looser timing keeps the outline flexible.
Writer Tip
Do not force precision too early. Use exact timing when the story depends on it; otherwise use confidence and relative time to show that the chronology is still being shaped.