Quick answer
A day/night system becomes interesting when the same action has different consequences depending on timing. Before launch, the useful guide is a priority list of questions to test, not a fake schedule.
Daylight priorities
Daytime may be better for information, safer movement, public interactions, or choices where visibility matters. These are assumptions to test, not confirmed route rules.
- Speak to characters and inspect public locations when possible.
- Check whether shops, quest givers, or safe travel depend on daylight.
- Record whether combat, stealth, or vampire powers are restricted or riskier.
- Use daylight to gather information before spending limited night actions.
Timing test grid
| Action type | Day question | Night question |
|---|---|---|
| NPC interaction | Are shops, quest contacts, or public witnesses available? | Do contacts disappear, hide, or change dialogue? |
| Combat | Are vampire tools limited, punished, or safer to avoid? | Do vampire powers, enemies, or stealth options change? |
| Travel | Is movement safer, faster, or more visible? | Does travel become dangerous, restricted, or more rewarding? |
| Story choice | Does public timing affect witnesses or consequences? | Does hidden timing reveal alternate branches? |
| Rest/resource | Does resting consume time or reset states? | Does night activity cost health, power, or reputation? |
Night priorities
Night may favor vampire identity, dangerous encounters, hidden routes, or story beats that would be impossible during the day. The guide should track both opportunity and cost.
Missed-window tracking
After launch, every time-sensitive event should record trigger, deadline, recovery options, spoiler level, and whether the window changes endings or only side rewards.
Record the exact action that starts the window.
Record whether travel, rest, combat, dialogue, or cutscenes advance time.
Mark whether the event is recoverable, delayed, failed, or outcome-changing.
Keep ending-related consequences behind explicit spoiler labels.