> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/metaverse/build/elements/timer.md).

# Timer

{% hint style="info" %}
A Timer can help you count up or down and create timed interactions.\
You can use this for quiz, games and more. This will help you measure or limit the time taken by someone to complete a section or the whole experience.
{% endhint %}

### Step 1: Add a Timer&#x20;

You can add a Timer to your experience by clicking on the '**+**' icon in the left bar and selecting ‘Timer’ under 'Gamification section.

<figure><img src="https://2186043722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2FmDDW5Tz8JbBU4FVqUyNR%2Fimage.png?alt=media&amp;token=fe55502d-e92c-4371-a77e-36d89b9c8a98" alt=""><figcaption><p>Adding a Timer</p></figcaption></figure>

### Step 2: Adjust the Timer

{% hint style="info" %}
The reliability of the timer element is **increments of 0.25 seconds**. So if you have a rule that says when Timer matches 7.2 seconds, it will probably trigger at 7.25 seconds.
{% endhint %}

The right panel provides different options to customize your timer.

You can switch between count up/count down, control the Minutes/Seconds, Autoplay option, and choose the font and its weight, adjust the placement.

<figure><img src="https://2186043722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2FjCSepywZb7zBJg8m7HmJ%2Fimage.png?alt=media&amp;token=125a39a7-48ea-4c24-9dd1-83c66c93084e" alt=""><figcaption><p>Timer adjustments</p></figcaption></figure>

## Example Experience

Here's a sample experience for a count up timer:

You can add 'Rules' to enable the timer to begin and stop or toggle.

Here are the rules used in the above example experience.&#x20;

{% embed url="<https://rnghud.gmetri.com/timer__1>\_" %}
Timer - Sample experience
{% endembed %}

Below are the set of rules used in the above example:

<figure><img src="https://2186043722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mgll1jjQMRTVj7p6n7g%2Fuploads%2FPJFEY7zo6vfieBrjcoby%2Fimage.png?alt=media&amp;token=fc8b9aee-08ac-4a6a-bd2d-c8bf58c943e6" alt=""><figcaption><p>Rules used on Timer</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gmetri.com/metaverse/build/elements/timer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
