> For the complete documentation index, see [llms.txt](https://animated-timer.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://animated-timer.gitbook.io/docs/advanced/profiles.md).

# Profiles

## General usage

Profiles allow you to store the current configuration and load it at a later time. By default, AT comes with 12 different profiles. Sufficient profile management is achieved with the the following commands:

<table><thead><tr><th width="198" align="center">Description</th><th width="282" align="center">Cheats enabled</th><th align="center">Without cheats</th></tr></thead><tbody><tr><td align="center">Save configuration at profile &#x3C;name></td><td align="center"><code>/function at-prof:save {name:foo}</code></td><td align="center"><code>/trigger save-profile set 1</code></td></tr><tr><td align="center">View configuration of profile &#x3C;name></td><td align="center"><code>/function at-prof:view {name:foo}</code></td><td align="center"><code>/trigger view-profile set 3</code></td></tr><tr><td align="center">Load profile &#x3C;name></td><td align="center"><code>/function at-prof:load {name:foo}</code></td><td align="center"><code>/trigger load-profile set 5</code></td></tr><tr><td align="center">Remove profile &#x3C;name></td><td align="center"><code>/function at-prof:delete {name:foo}</code></td><td align="center"><code>/trigger delete-profile set 7</code></td></tr><tr><td align="center">List existing profiles</td><td align="center"><code>/function at-prof:list</code></td><td align="center"><code>/trigger list-profiles</code></td></tr></tbody></table>

Note: Loading a profile can be simplified by left-clicking on the command output of the list command. Just click on the profile you would like to try out (either on the name or its \[index], for */trigger* command) to automatically suggest the corresponding profile load command.

<figure><img src="/files/NyqK19UKmtrhkTrFL1M0" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/RMNEShqJfEmSvDdUdArV" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/EqOfMhE7SoOw3crkD2ae" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/o5wzOP41dQ3nRPDGZIcG" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/57w8q1MYuQ5tPsw51LIl" alt=""><figcaption></figcaption></figure>

## Using /trigger

While profile management using */function* is consistent, meaning that you can save, load, etc to / from the same name, and will always access the same profile, management using */trigger* is not. It's designed this way to give players without cheats the ability to access existing (pre-made) profiles.

With triggers it works like this: The score you enter at the save gets appended behind “trigger”, forming a unique name like “trigger0” or “trigger42”, so saving works as expected.

Loading is a bit different though. To load the profile, you first need to know its index, which you can obtain by entering the list command. (the number in square brackets \[]) If you have decided what profile you want to have, run the load command with the index behind your profile. The correct profile should now be loaded. The same principle also applies to the view and delete command.

This functionality may change at a later time, if / when I have a better idea for solving this issue.

<figure><img src="/files/QhTSjfw73vzB0WJREZBJ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/UtF4pXroWoT0wWm8ttPD" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/6Dgo2zJl72xUhECcP72Q" alt=""><figcaption></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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://animated-timer.gitbook.io/docs/advanced/profiles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
