> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/forge/gameplay/sandbox/equipment/equipment-spawning.md).
# Equipment Spawning
This article provides explanations regarding topics related to equipment spawning, covering the different ways equipment can be spawned in Halo Infinite via Forge objects.
## Standard Spawners
### Equipment Dispenser
The Equipment Dispenser is the main spawner for base equipment. It's intended to be placed on the ground.
The standard setup for an Equipment Dispenser is as follows:
* **Equipment:** (user-defined)
* **Static Selection:** Enabled
* **Legendary Variants:** Exclude
* **Randomize:** Every Game
* **Symmetrical Channel:** (user-defined)
* **Navpoint:** Off
* **Initial Spawn Delay:** (user-defined)
* **Spawn Properties:** 343 Default
* **Selective Channel:** None
* **Seed Sequence Key:** EquipmentPadPlacementKey
{% hint style="info" %}
Read about the details about the Static Selection and Spawn Properties [here](/forge/gameplay/sandbox/spawn-properties.md).
{% endhint %}
### Power Equipment Pad
The Power Equipment Pad is the main spawner for power equipment. It's intended to be placed on the ground.
The standard setup for a Power Equipment Pad is as follows:
* **Equipment:** (user-defined)
* **Static Selection:** Enabled
* **Tier:** Power
* **Legendary Variants:** Exclude
* **Randomize:** Every Game
* **Symmetrical Channel:** (user-defined)
* **Navpoint:** On
* **Initial Spawn Delay:** (user-defined)
* **Spawn Properties:** 343 Default
* **Selective Channel:** None
* **Seed Sequence Key:** PowerUpPadPlacementKey
## Specialized Spawners
### Equipment Pod
The Equipment Pod is not used in standard setups, but it still follows the same logic as other spawners. It's only used in Big Team Battle and Last Spartan Standing as ordnance drops. Properties not listed don't matter.
The standard setup for an Equipment Pod is as follows:
* **Equipment:** (user-defined)
* **Static Selection:** Disabled
* **Tier:** Any
* **Legendary Variants:** Exclude
* **Randomize:** Every Game
* **Symmetrical Channel:** (user-defined)
* **Navpoint:** On
* **Initial Spawn Delay:** (user-defined)
* **Spawn Properties:** 343 Default
* **Selective Channel:** None
* **Seed Sequence Key:** OrdnancePodPlacementKey
### Classic Equipment Spawn
The Classic Equipment Spawn is not used in standard setups, but it still follows the same logic as other spawners. It's only used in Infection as the main way of spawning equipment. Properties not listed don't matter.
The standard setup for a Classic Equipment Spawn is as follows:
* **Equipment:** (user-defined)
* **Static Selection:** Disabled
* **Tier:** Any
* **Legendary Variants:** Exclude
* **Randomize:** Every Game
* **Symmetrical Channel:** (user-defined)
* **Navpoint:** Off
* **Initial Spawn Delay:** (user-defined)
* **Spawn Properties:** 343 Default
* **Selective Channel:** None
* **Seed Sequence Key:** EquipmentPadPlacementKey
***
## Source Data
* Discord thread: [Equipment Spawning](https://discord.com/channels/220766496635224065/1535166833781645413/1535166833781645413)
#### Contributors
Okom
---
# 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://wiki.thescriptersguild.com/forge/gameplay/sandbox/equipment/equipment-spawning.md?ask=&goal=
```
`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.