Skip to content
DynarosDynaros Docs

Learn Time

Use this page to understand what Time is responsible for before you look up exact API details.

Core Idea

Section titled “Core Idea”

Time focuses on game time, calendars, schedules, day/night progression, and time queries.

It should answer its own responsibility clearly without taking over nearby systems.

Responsibility Boundary

Section titled “Responsibility Boundary”

Time owns:

  • game-time state
  • calendar rules
  • scheduling
  • day/night progression
  • time-based queries

It does not own:

  • weather simulation
  • crop behavior
  • quest logic
  • world events
  • visual sky implementation

How It Fits

Section titled “How It Fits”

Time should be usable by itself. When other Dynaros products are installed, integrations can make workflows smoother without turning unrelated products into hidden requirements.

Working Model

Section titled “Working Model”
Project or gameplay event
        v
Time plugin behavior
        v
Time validation / state / result
        v
Owning project or related system responds

What To Learn Next

Section titled “What To Learn Next”

Start with the overview if you are still deciding whether Time owns your problem. Use Guides for workflows, Recipes for focused examples, and Reference for exact symbols or settings.