> For the complete documentation index, see [llms.txt](https://docs.motar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motar.com/motar-core-services/intro-to-core-services/devices/motar-sdk-for-unity/prefabs.md).

# Prefabs

## Avatar&#x20;

<figure><img src="/files/6v77ftNcbHyrXqIhYd4V" alt="" width="371"><figcaption></figcaption></figure>

* Allows users to use our pre-made Avatar and add Multiplayer to their Unity application

## Spawn Point

<figure><img src="/files/szl40IymrqU7TEc6ZYeS" alt="" width="371"><figcaption></figcaption></figure>

* Prefab MOTARXR\_SpawnPoint
* Allows users to spawn their MOTARXR\_Rig into a specific location
  * Can have multiple spawn points where user will randomly spawn into one

## Teleport Anchor

<figure><img src="/files/Co2J3J3eQTv33GdJ27Tx" alt="" width="371"><figcaption></figcaption></figure>

* Avatar displays users name & device on UI above their head&#x20;
* Avatar's will fade out as they get too close to one another&#x20;
* Avatar's face will be the users profile photo&#x20;
* Avatar's hands will animate based on device input (Grip/Trigger/Trigger Touch/Thumbstick/Thumbstick touch)&#x20;
  * Hands have some unique poses based on grabbing objects with specific tags&#x20;
  * RoundGrabbable/LCylinderGrabbable/SCylinderGrabbable/WritingGrabbable&#x20;
  * Tags will be automatically added to project when package is imported&#x20;
  * Hands have a Wrist gameObject attached to them that will spawn any "Watch" prefab located in Resources named "MOTARXR\_LefthandWatch" or "MOTARXR\_RightHandWatch"&#x20;
* Supports both Built-In and URP render pipelines&#x20;
  * Toolbar button to convert from one to the other will be automatically added on package install&#x20;
* Sample that contains MultiplayerTest&#x20;
  * A fully put together example utilizing all the features for users to try

## XR Player

<figure><img src="/files/1HEmIh7dXGrggYUxKPsV" alt="" width="371"><figcaption></figcaption></figure>

* Avatar displays users name & device on UI above their head&#x20;
* Avatar's will fade out as they get too close to one another&#x20;
* Avatar's face will be the users profile photo&#x20;
* Avatar's hands will animate based on device input (Grip/Trigger/Trigger Touch/Thumbstick/Thumbstick touch)&#x20;
  * Hands have some unique poses based on grabbing objects with specific tags&#x20;
  * RoundGrabbable/LCylinderGrabbable/SCylinderGrabbable/WritingGrabbable&#x20;
  * Tags will be automatically added to project when package is imported&#x20;
  * Hands have a Wrist gameObject attached to them that will spawn any "Watch" prefab located in Resources named "MOTARXR\_LefthandWatch" or "MOTARXR\_RightHandWatch"&#x20;
* Supports both Built-In and URP render pipelines&#x20;
  * Toolbar button to convert from one to the other will be automatically added on package install&#x20;
* Sample that contains MultiplayerTest&#x20;
  * A fully put together example utilizing all the features for users to try


---

# 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://docs.motar.com/motar-core-services/intro-to-core-services/devices/motar-sdk-for-unity/prefabs.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.
