# Attributes

### What are Attributes?

Attributes are variables that define and handle numeric gameplay attributes (Health, Cash, Speed, Strength, etc.) in the Reality Gameplay System. These go into a Attribute Set, that handles Replication, Clamping, etc automatically.

***

### When to use a Attribute&#x20;

* Character stats that need to be replicated (Health, Coins, Stamina)
* Values that change frequently during runtime
* Stats that are modified by Gameplay Effects
* Attributes that need clamping (Health cannot exceed MaxHealth)

### When to NOT a use Attribute&#x20;

* Static Data&#x20;
* Non Numeric Data
* Local-Only values that don't need replication

***

### Creating Custom Attributes

{% hint style="info" %}
Currently, you can only create Custom Attributes in Gamemode Mods.&#x20;
{% endhint %}

{% stepper %}
{% step %}

### **Finding and Defining Attributes**

Open your GameData Asset, and scroll down to Attributes. \
Expand Attribute Config, and Scroll to "Enable Custom Attributes 1" and "Enable Custom Attributes 2", each gives you 8 custom attributes.

Simply change the name to define the attribute. (Health, Coins, etc)\
\
To set the base attribute value, you will have to apply an instant Gameplay Effect at Startup, which is covered in the Gameplay Effects section.
{% endstep %}

{% step %}

### Getting Attribute Values

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

{% hint style="info" %}
You cannot set Attribute Values directly in Blueprints. THIS IS ON PURPOSE. You Modify Attribute Values in Gameplay Effects!!
{% endhint %}
{% endstep %}
{% endstepper %}


---

# Agent Instructions: 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://beyond-sandbox.gitbook.io/realitysdk/documentation/reality-gameplay-system/attributes.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.
