Description
Compare a fictional journey's constant-speed time with availability.
Story planning separates the order of telling from fictional chronology, continuity records and practical writing budgets. Explicit labels, counts and invented calendar rules can make a local convention consistent without deciding narrative quality or inferring facts from manuscript prose.
Compare a fictional journey's constant-speed time with availability.
When to use this tool
Use Character Location Travel Time Gap when checking a supplied story-continuity, chronology, calendar or drafting-budget convention.
How to use the tool and how it works
- Enter availableHours, distance, speed, stopHours. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read requiredHours, slackHours. Use the output convention below.
Compare a fictional journey's constant-speed time with availability. Require nonnegative availableHours/distance/stopHours and positive speed; requiredHours = distance/speed+stops, slackHours = available-required.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| availableHours | Available Hours | Required. Finite number; minimum 0. |
| distance | Distance | Required. Finite number; minimum 0. |
| speed | Speed | Required. Finite number; strictly above 0. |
| stopHours | Stop Hours | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| requiredHours | Required Hours | Required. Finite number. |
| slackHours | Slack Hours | Required. Finite number. |
{
"input": {
"availableHours": 5,
"distance": 120,
"speed": 40,
"stopHours": 1
},
"output": {
"requiredHours": 4,
"slackHours": 1
}
}Limitations and assumptions
- Distance/speed must produce hours; actual route, terrain, travel conditions and story plausibility are not modeled.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use the manuscript, scene outline and the chosen style/calendar policy for a complete editorial review; interpret numerical budgets in their narrative context.
References
Similar or alternative tools
- Scene Elapsed Time Slack
Compare scene duration with action time after simultaneous credit.
- Scene Present Time Reference Gap
Return three signed narrative time offsets.