UI name in toolbox: timer >|< [VALUE] (s) after [TASK] finished

Block type: Value block, output type Boolean

Definition: A timer that starts when a specific task is finished, and triggers based on > or < comparisons relative to that start point.

When it becomes true:

• Greater than >: After a specified duration has elapsed since the task finished
• Smaller than <: Before that duration has elapsed since the task finished

How to build it:

1. Drag timer >|< [VALUE] (s) after [TASK] finished from Logic category
2. Select operator: > or < from dropdown
3. Connect a task block to [TASK] socket
4. Enter duration value in [VALUE] field (in seconds)
5. Connect to condition socket in WHEN block

Input/Field requirements:

• Operator dropdown: > or <
• [TASK] input: must be type Task
• [VALUE]: numeric input (seconds)

How it works:

1. Task is finished (must meet its finish condition)
2. Timer starts counting from that moment
3. Condition is evaluated based on elapsed time since task finish

Example (Simple):
Block: timer > 180 (s) after [2] icon "Task" finished
Sequence:

1. Task 2 is finished
2. 3 minutes (180 seconds) pass
3. Condition becomes TRUE

Example (Edge Case – Multiple task finishes):
Scenario: Multiple instances of timer > 300 (s) after [task 5] finished
Result: Each completion resets the timer and re-evaluates the condition

Notes:

• Combines task completion with time-based triggers
• Time measured in seconds
• Useful for phased unlocks or time-limited follow-ups
• Timer resets if the task is answered again (if applicable)

Common mistakes:

• Using without ensuring the task actually finishes
• Confusing with timer >|< [H] h [MIN] min [S] s (game duration timer, not post-task)
• Forgetting the field is in seconds, not hours/minutes