> For the complete documentation index, see [llms.txt](https://threadforge.gitbook.io/threadlink-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://threadforge.gitbook.io/threadlink-documentation/designer-reference/procedures.md).

# Designer Procedures

## Declaring a spawn point

1. Add the identifier to `Threadlink User/Native Domain Injectors/Nexus.SpawnPoints.User.txt`.
2. Save. Generation runs automatically.
3. The spawn point becomes selectable wherever spawn points are configured.

## Adding a tunable value to an entity

1. Add the field identifier to `Vault.Fields.User.txt` and save.
2. Open the entity's Vault, add a field with that identifier, select its type, and enter the value.
3. Select the **Serialised** or **Transient** backing.

## Declaring an input context

1. Add the mode identifier to `Dextra.InputModes.User.txt` and save.
2. Provide the identifier to engineering for binding to an input action map.

## Browsing and editing Vaults

1. Open **`Threadlink ▸ Vault Browser`**.
2. Search or scroll to the Vault, select it, and edit its fields on the right.

## Making an asset loadable

1. Assign the asset to an Addressable group under a stable name.
2. Map it through **`Threadlink ▸ Addressables ▸ Mapping Window`** and select **Apply**.

## Placing an audio zone

1. Add an **AuraZone** and an **AudioSource** to a GameObject in the scene, and assign the source's clip.
2. Give the zone a name unique within the scene.
3. Set **Radius Coefficient** and **Influence**.

## Working rules

* Never type a name as a string. Declare an identifier, save, and pick it from the dropdown.
* Removing is safe. Renaming breaks existing references, so coordinate it.
* Read the console summary after each generation pass.
* Give Addressable assets stable names and final groups before mapping them.
* Tell engineering about any rename of an identifier that code may use.