> 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/knowledge/scripting/guides-and-info/patterns/sending-fusion-coils-directly-to-players-hands.md).

# Sending Fusion Coils Directly to Player's Hands

In Halo Infinite's Forge Mode, mode designers may want to be able to send Fusion Coils directly to a player's hands. Since Kong Slayer doesn't give control over when player has a coil it is not a viable base mode to provide this functionality.

This method relies on the following fact of Halo's engine: All carryables are weapons. Fusion coils are carryable.

To send a Fusion Coil directly to a player's hands, you can detect the weapon type of a fusion coil and use that to send one to the player's primary weapon slot. To do this, you can put a coil somewhere out of boundary (outside of the level), get an object reference to it, and you can spawn new ones in players hands with that reference using normal weapon-granting nodes, such as `Give Player New Weapon`.

**Contributors**\
Captain Punch


---

# 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/knowledge/scripting/guides-and-info/patterns/sending-fusion-coils-directly-to-players-hands.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.