> For the complete documentation index, see [llms.txt](https://docs.infimagames.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infimagames.com/product/tactical-fps-animation-packs/guides-and-tutorials/editor/holstering-and-switching-weapons.md).

# How to Carry and Switch Weapons

Carry two weapons in the showcase and switch between them, with the holster and draw animations, and see the holstered weapon on the body.

{% hint style="info" %}
This page is about our demo showcase Blueprints. The Blueprints are mainly meant for showcase purposes, and aren't intended to be used as an FPS template out of the box.
{% endhint %}

#### Table of Contents

* [Introduction](#introduction)
* [Before You Start](#before-you-start)
* [Carry Two Weapons](#carry-two-weapons)
* [Holster and Draw](#holster-and-draw)

***

### Introduction

***

In this guide, I'll show you how to give the showcase character two weapons, switch between them with the holster and draw animations, and see the holstered one on the body. In the asset names, a draw is called an Equip.

Each showcase map starts the character with only its own weapon, so the number keys switch nothing until it carries more. I'll use the Pistol. For the Assault Rifle, use `L_TFA_AR_Showcase` and `DA_TFA_AssaultRifle` instead.

***

### Before You Start

***

You need a second data asset to carry.

* With one pack, use your own copy of the weapon, such as `DA_MyPistol`. [How to Customize a Weapon's Settings and Fit a Scope](https://docs.infimagames.com/product/tactical-fps-animation-packs/guides-and-tutorials/editor/add-a-weapon-and-scopes.md#customize-a-weapons-settings) shows how to make it.
* With both packs, carry the Pistol and the Assault Rifle. `DA_TFA_AssaultRifle` is in `Weapons/AssaultRifle/Demo/Data`.

***

### Carry Two Weapons

***

{% stepper %}
{% step %}

#### Select the Demo Character

1. Open `L_TFA_Pistol_Showcase`.
2. Select the character in it.
3. In the Details panel, select its **WeaponComponent**.
   {% endstep %}

{% step %}

#### Fill the Loadout

1. Add two entries to **Loadout**, `DA_TFA_Pistol` and your second data asset, such as `DA_MyPistol`.
2. Set **Weapon Config** to `DA_TFA_Pistol`, the first one.

The Loadout is the list of weapons the character carries, in slot order.

<div align="left" data-with-frame="true"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2F8RsDmiHWDRvS910F70hB%2FSL-HOL-01.png?alt=media&amp;token=621ca079-54f4-4aeb-8511-d7543c1d0460" alt="" width="470"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Test It in Play

1. Hit **Play**.
2. Press **2**. The Pistol in hand plays its holster animation, then the second weapon is drawn.
3. Press **1** to switch back.
   {% endstep %}

{% step %}

#### See the Holstered Weapon

Press **P** to switch to third person. The weapon that isn't in hand waits on the body, a pistol on the outside of the right thigh and the Assault Rifle across the back.

<div align="left"><figure><img src="https://3271331258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuuZjeeFspZ4mvcxHpS6M%2Fuploads%2F5MuNImSXh7buO0iTptRv%2FSL-HOL-02.png?alt=media&amp;token=460decb4-55c3-47ae-8c8e-2d33668366b0" alt=""><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

That's it! The number keys 1 to 4 draw the first four weapons of the Loadout. There's no fixed limit, and each weapon keeps its fire mode and grip while it's holstered.

<details>

<summary>How the Loadout and switching work</summary>

* Every Loadout weapon spawns at the start. The Weapon Config's weapon goes into the hand, and it's added as the first slot when the Loadout doesn't list it. The others wait on their holster sockets.
* **Switch Weapon** (Index) plays the holster animation of the weapon in hand, then draws the one in that slot, 0 being the first slot. **Cycle Weapon** (Direction) steps through the Loadout, skipping empty slots. Both return **Started**, which is false when the switch was refused, for example while another action plays or the weapon is jammed.
* When the character is destroyed, its weapons, their magazines and attachments, and any item in its hand go with it.

</details>

<details>

<summary>The holster sockets</summary>

Each data asset names where its weapon waits, in **Names > Sockets > Socket Holster Attachment**. Both sockets are on `SKEL_TFA_Mannequin`.

| Socket                | Bone       | Used by                                                    |
| --------------------- | ---------- | ---------------------------------------------------------- |
| `SOCKET_Holster_Back` | `spine_05` | The Assault Rifle, across the back                         |
| `SOCKET_Holster_Hip`  | `thigh_r`  | The Pistol, on the outside of the right thigh, muzzle down |

Two weapons that use the same socket wait in the same place. A holstered weapon only shows on a full-body mesh, so you see it in third person. On a character of your own, the skeleton needs these sockets, see [Copy the Sockets From Our Skeleton](https://docs.infimagames.com/product/tactical-fps-animation-packs/guides-and-tutorials/editor/use-the-weapons-on-your-own-character.md#copy-the-sockets-from-our-skeleton). Without them a holstered weapon is hidden, with its magazine and laser, until it's drawn. The laser turns off while its weapon is holstered.

</details>

***

### Holster and Draw

***

Press **H** in the showcase. The weapon goes into its holster and comes straight back out, so the holster and draw animations play back to back.

{% hint style="info" %}
The packs don't include unarmed animations, so there's no empty-handed state. See the Unarmed Config note on [Weapon Component (BP\_TFA\_WeaponComponent)](https://docs.infimagames.com/product/tactical-fps-animation-packs/guides-and-tutorials/reference/blueprints/weapon-component-bp_tfa_weaponcomponent.md).
{% endhint %}

With an empty weapon, the locked slide changes what plays.

* The Pistol's empty holster (`Holster_Empty`) lets the slide go forward as it goes in.
* The Pistol's empty draw (`Equip_Empty`) pulls the slide back and locks it, so it comes out ready for an empty reload.

{% hint style="info" %}
The Pistol also includes quick holster and quick draw montages, `AM_TFA_FP_Pistol_Holster_Quick` and `AM_TFA_FP_Pistol_Equip_Quick`, with `AM_TFA_TP_Pistol_Holster_Quick` and `AM_TFA_TP_Pistol_Equip_Quick` for third person. The showcase doesn't play them, so they're there for your own setup.
{% endhint %}

<details>

<summary>How the holstered weapon swings</summary>

A holstered weapon swings a little on its socket. Each data asset sets it with **Holster Jiggle Amount**, **Holster Jiggle Stiffness** and **Holster Jiggle Damping**.

</details>


---

# 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.infimagames.com/product/tactical-fps-animation-packs/guides-and-tutorials/editor/holstering-and-switching-weapons.md?ask=<question>&goal=<user_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.
