> For the complete documentation index, see [llms.txt](https://speedtutoruk.gitbook.io/door-interaction-kit-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://speedtutoruk.gitbook.io/door-interaction-kit-doc/support/variables-fields-not-appearing-in-inspector.md).

# Variables / Fields Not Appearing in Inspector?

### Adding New Fields to the Custom Inspector

{% hint style="warning" %}
The video below will explain how to add fields or variables to the DoorInteractable script as it uses a custom inspector
{% endhint %}

{% embed url="<https://drive.google.com/file/d/18uY9fKvp95RKpm7bbVBXQGCs415wP6WO/view?usp=sharing>" %}

### Code Examples:&#x20;

1. Add a field as below into the **DoorInteractable** script

```csharp
[SerializeField] private GameObject exampleField = null;
```

2. Open the **DoorInteractableEditor** script - At the top of the script created a new property with the same name like:&#x20;

```csharp
SerializedProperty exampleField;
```

3. Find the **OnEnable()** method and add a new find property reference as below:&#x20;

```csharp
exampleField = serializedObject.FindProperty(nameof(exampleField));
```

4. In the methods below that, find a place for your new field. I've grouped them together to make it more readable. Add a property GUI field:&#x20;

```csharp
EditorGUILayout.PropertyField(exampleField);
```

### Understanding Custom Editors:

{% hint style="info" %}
Below is a ttuorial I made to highlight the usage and examples of custom inspectors / editors&#x20;
{% endhint %}

{% embed url="<https://youtu.be/xFtFWmiW7IE>" %}


---

# 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://speedtutoruk.gitbook.io/door-interaction-kit-doc/support/variables-fields-not-appearing-in-inspector.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.