> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/dev-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/dev-guide/guidelines/code-design/events/action.md).
# Action
An **Action** is an **event** that depends on an **object** to exist.
The **Action**** ****event** should be used when we don't need something to be accessed globally, like a button being pressed, or when we need to listen from something from a specific object.
Declaring
**Actions** have to be declared as the first thing inside a **object** with the **event** keyword.
```
public class ButtonView : Actor
{
public event Action OnButtonPressed;
}
```
Only the **object** that declares the **event** can invoke it.
It is noted that you can use an **Action** to send data too:
```
public event Action OnNumberUpdated;
public event Action- OnItemUpdated;
```
## Using an Action
Let's imagine you have a granade in your character's hand. Pretty common sight in a Low RP server. In the code, usually we would have something like:
```
public class Granade : Explosive
{
public event Action OnPinRemoved;
public void RemovePin()
{
// Do pin removal logic.
OnPinRemoved?.Invoke();
}
}
```
The **OnPinRemoved** **event** will be used to to tell listeners that subscribed to that granade's event that the granade's pin was removed. The relevance of that **OnPinRemoved** **event** is usually for UI related purposes, or running a local animation of a granade pin flying through your screen.
Something like:
```
public class GranadePinAnimationView : Actor
{
private GranadePinAnimation _granadePinAnimation;
private Granade _granade;
protected override OnAwake()
{
_granade.OnPinRemoved += HandlePinRemoved;
}
protected override OnDestroyed()
{
_granade.OnPinRemoved -= HandlePinRemoved;
}
private void HandlePinRemoved()
{
_granadePinAnimation.RunAnimation();
}
}
```
You might even think it would be easier to call it directly, and depending on your logic it might be, but we are assuming that in this case its better to keep the classes decoupled.
---
# 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://ss3d.gitbook.io/dev-guide/guidelines/code-design/events/action.md?ask=&goal=
```
`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.