DATE-TIME CONDITION

UI name in toolbox: date >|< [Y] [M] [D] [H] [MIN] [S] TZ [T]

Block type: Value block, output type Boolean

Definition: Becomes true when the actual date and time reach a specific moment (real-world clock time).

When it becomes true:

  • Greater than >: After the specified date-time has passed
  • Smaller than <: Before the specified date-time

How to build it:

  1. Drag date >|< [Y] [M] [D] [H] [MIN] [S] TZ [T] from Logic category
  2. Select operator: > or < from dropdown
  3. Set year, month, day, hours, minutes, seconds, timezone
  4. Connect to condition socket in WHEN block

Field specifications:

  • Operator dropdown: > or <
  • Year [Y]: whole number, minimum 0
  • Month [M]: whole number, range 1–12
  • Day [D]: whole number, range 1–31
  • Hour [H]: whole number, range 0–23
  • Minutes [MIN]: whole number, range 0–59
  • Seconds [S]: whole number, range 0–59
  • Timezone offset [T]: range -12 to +14 hours

Example (Simple):
Date: 2024 / 12 / 25
Time: 18:00:00
Timezone: +1 (Central European Time)
Result: Becomes true on Christmas Day after 6 PM CET

Important – Timezone handling:

  • Default = your computer’s timezone
  • Must update manually when daylight saving time changes
  • Timezone mismatch causes conditions to trigger at unexpected times
  • Always verify timezone matches your game’s intended region

Example (Edge Case – Daylight saving transition):
If set for 2:30 AM during DST transition (when clocks “spring forward”):
Result: This time may not exist; condition behaves unpredictably

Notes:

  • Uses real-world clock, not game duration
  • Useful for event-based games or scheduled releases
  • Must monitor and update during DST changes
  • Timezone setting is critical for accuracy

Common mistakes:

  • Forgetting to set or verify timezone
  • Not updating timezone when DST changes
  • Using Date-Time instead of Timer for duration-based triggers
Tagged: