Tick | Bricks Dag, Inc. Help Center

The Countdown Timer Handler is mainly used to limit user actions within a set time period or to perform actions after waiting for a fixed duration. It provides creators with an easy way to control timing-based behaviors.

Local Sync Block

RunMode

one of

List

Defines the execution method when Local Sync is enabled in DEVICE settings and multiple devices run the same application under the same local network.

all: All devices execute the handler when triggered.
main-only: Only the highest-priority device (defined in Local Sync) executes the handler.
minor-only: Only the lowest-priority device (defined in Local Sync) executes the handler.

Properties Block

Init	Boolean Boolean (Yes/No)	Sets whether the handler starts running automatically when the Generator is initialized.
Interval	Number milliseconds	Sets the time interval for each countdown step.
Countdown Start	Number Number	Sets the starting value of the countdown.
Countdown Interval	Number Number	Sets the value by which the countdown changes at each interval.
Repeat	Boolean Boolean (Yes/No)	Sets whether the countdown restarts automatically after completion.
Map	Object Object	Defines mappings between countdown numbers and custom display text. For example, to change countdown values 2 and 1 into "Ready?" and "Go", you can configure these mappings here. Mappings can be defined as strings or numbers.
Map Fallback	Any Any	Defines the default output value when no mapping is found in the Map configuration. Can be set to a string or number. If not specified, the original countdown value will be used.

Events Block

Ticking	Triggered on every countdown interval.
Completed	Triggered when the countdown finishes.

Outlets Block

Countdown

String / Number

Outputs the current countdown value (string or number) to a Property Bank variable.

Operation Block
Inspect this Generator
- Displays the relationship between the Generator, Events, and Property Bank.
Event Routing
- Shows the event/calculation flow, including which bricks/generators/properties are affected. Useful for troubleshooting event dependencies.
Parent Call
- Displays which bricks/generators/property calculations triggered this handler. Unlike Event Routing (which traces downstream), Parent Call traces upstream from the source.
Copy
- Creates a copy of this Generator handler.
Remove this Generator
- Removes this Generator handler.