> For the complete documentation index, see [llms.txt](https://docs.sandbox.game/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sandbox.game/en/creator/game-maker/docs/behaviours/basic-logic/spawn-point-and-avatars-feature.md). # Spawn Point & Avatar's Feature New in GM 0.10. Introduces team gameplay, varied spawn point setups, and some components applied to avatars (Avatar's Feature). {% hint style="success" %} **COPY/PASTE PARAMETERS** New in GM 0.11! Right click on a behaviour or component to copy. Then open an object, add the same behaviour or component, and right click it to paste identical parameter settings. {% endhint %} {% hint style="info" %} Non-global **Player settings** have moved into this behavior to vary spawning options. {% endhint %} {% hint style="info" %} [Build Singleplayer & Multiplayer Logic](/en/creator/game-maker/docs/build-singleplayer-and-multiplayer-logic.md) - about **\[SP]** or **\[MP]** behaviours or components {% endhint %} ## Spawn Point **\[MP]**

Multiple Varied Spawn Points

Apply to any object (collisions will turn off)

Default in Avatar's Portal

GM Spawn Point behavior sm opt.gif
Included: Avatar's Feature
Apply some existing components to avatars by spawn point (may be used to differentiate teams)
GM Avatar Features sm opt.gif
  • Define where and how players spawn
  • Create team identities
  • Apply equipment settings by spawn point
  • New broadcast type to direct messages to a specific team
### Set a Custom Avatar Select any asset in your Library. \ How to add custom avatars to your library: 1. [Create Assets](/en/creator/voxedit/create-assets.md) in VoxEdit 2. [Upload Assets to Workspaces](/en/creator/voxedit/upload-assets-to-workspaces.md) ### Create Teams Create team name and max players * Use *Team* **Broadcast Type** in other logic to direct messages to a specific team * Use **Team (T)** variables in [Game Rules](/en/creator/game-maker/docs/game-rules.md) to track scores, times, etc. by team {% hint style="info" %} **SPAWN POINT VARIETY & PRIORITY** Players are prioritized to spawn to team spawn points first, then non-team spawn points. {% endhint %} {% hint style="info" %} **RANDOM SPAWNING**\ Players are assigned to teams when entering an Experience. Logic will not modify Teams. {% endhint %} ### Apply Tags to Players ### Override Player Equipment ### Set Spawn Area Size & Shape ### Avatar's Feature (Components) Click **Add Feature** to add a component to all avatars spawned in the selected spawn point. Double click on a feature to edit the parameters. ## Communications {% hint style="info" %} Send a message to a specific team using the *Team* **Broadcast Type** in other logic. {% endhint %} * Avatar's Feature (components) have varied logic to send and receive messages. Learn more: * [Health](/en/creator/game-maker/docs/components/status/health.md) * [Light](/en/creator/game-maker/docs/components/display/light.md) * [Play Sound](/en/creator/game-maker/docs/components/audio/play-sound.md) * [Raycast](/en/creator/game-maker/docs/components/gameplay/raycast.md) * [Trigger Volume](/en/creator/game-maker/docs/components/triggers/trigger-volume.md) * [Visual FX](/en/creator/game-maker/docs/components/display/visual-fx.md) ## Use Cases * Mixed spawn points in one Experience (various team sizes, spectators not assigned to teams, etc). * No team assignments, players spawning in various areas of the Experience. * Apply distinguishing characteristics or specific logic to players through tags, equipment, and Avatar's Features, which may or may not be related to team assignments when players initially spawn into the Experience. For example: coloured uniforms, unique tags, different VFX, etc. * Force players to use equipment assigned for immersion into your narrative. * Allow players to use their NFT equipment by setting **Override Equipment** to *False*. ## Parameter Notes **Avatar Input Configuration** is unlocked when a custom avatar is applied.
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sandbox.game/en/creator/game-maker/docs/behaviours/basic-logic/spawn-point-and-avatars-feature.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.