> For the complete documentation index, see [llms.txt](https://blackboard.crashkonijn.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blackboard.crashkonijn.com/examples/08_unity_attributes.md).

# 08 Unity Attributes

This example shows you how to use unity attributes in a blackboard.

These files can be found in the /Examples/\[example] and /Blackboards/Examples folders.

## UnityAttributeBlackboard.cs

```csharp
using CrashKonijn.RabbitBlackboard.Contracts;
using UnityEngine;

namespace CrashKonijn.BlackboardPro.Blackboards.Examples
{
    public partial class UnityAttributeBlackboard : BlackboardBehaviour
    {
        // You can use unity attributes to show extra information in the editor
        [Header("Basic Info")]
        private string playerName;

        // The blackboard is rendered in the following order:
        // 1. Fields
        // 2. Lists
        // 3. Computed properties
        // This means that this header and field be lower in the blackboard
        [Header("Arrays/Lists")]
        private int[] someArray;

        [Space]
        private string spacedValue;

        [HideInInspector]
        private float hiddenValue;

        // These attributes won't work
        [Tooltip("The player's health points.")]
        [Range(0, 100)]
        private int health;
    }
}

```


---

# 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://blackboard.crashkonijn.com/examples/08_unity_attributes.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.