> For the complete documentation index, see [llms.txt](https://alixanimations.gitbook.io/alixanimations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alixanimations.gitbook.io/alixanimations/fundamentals/getting-set-up/actions.md).

# Actions

{% hint style="warning" %}
For all the actions please see this [page](/alixanimations/fundamentals/getting-set-up/actions/actions-list.md)
{% endhint %}

We have 3 main Actions, 

```
startactions
endactions
markers
```

## StartActions

This action gets called when the animations start, example

```yaml
  test:
    strength: 30
    inOrOut: 1
    location:
      x: 0
      y: 0
      z: 0
      world: "world"
    startactions:
      - "[BROADCAST] Start Animation for %player%"
```

## EndActions

Gets called when the animations ends, example

```yaml
  test:
    strength: 30
    inOrOut: 1
    location:
      x: 10
      y: 10
      z: 10
      world: "World"
    startactions:
    endactions:
      - "[BROADCAST] End Animation for %player%"
```

## Markers

{% hint style="info" %}
Markers are a feature inside blender timeline, please see this [page](https://docs.blender.org/manual/en/latest/animation/markers.html) 
{% endhint %}

Markers gets called when you get in a specific frame, example

<pre class="language-yaml"><code class="lang-yaml"><strong>  test:
</strong>    strength: 30
    inOrOut: 1
    location:
      x: 0
      y: 0
      z: 0
      world: "world"
    markers:
      MyMarkerName:
        - "[BROADCAST] MyMarkerName got called"
</code></pre>

If you want know whats your marker name, you can see it from here\
![](/files/DV2EfONBUmE5rDnZeOx0)

So if for example we want the plugin to do something when the animations gets to Pose we do

```yaml
  test:
    strength: 30
    inOrOut: 1
    location:
      x: 0
      y: 0
      z: 0
      world: "world"
    markers:
      Pose:
        - "[BROADCAST] Pose got called"
```


---

# 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, and the optional `goal` query parameter:

```
GET https://alixanimations.gitbook.io/alixanimations/fundamentals/getting-set-up/actions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.