> 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/low-poly-animated-modern-guns-pack/guides-and-faq/faq.md).

# FAQ

***

<details>

<summary><strong>Does this product work with the UE5 Mannequin skeleton?</strong></summary>

Unfortunately no, it only works with the UE4 mannequin skeleton. We have attempted to retarget it to the UE5 skeleton but ran into issues, especially with the hand and finger placement being inaccurate.

</details>

<details>

<summary><strong>Are third person view animations included?</strong></summary>

No unfortunately there are no specific third person animations, the included animations are mainly intended to be used and viewed from a first person perspective.

</details>

<details>

<summary><strong>The character is not moving around in the demo map when i press the WASD keys?</strong></summary>

This is intentional, the included code is used for demonstration purposes to showcase the animations and models, it's not actually intended to be used in a final product (which is why the character is stuck in place).

</details>

<details>

<summary><strong>Can you provide the Blender source files for the animations?</strong></summary>

No unfortunately not, we generally do not share the animation source files publicly.&#x20;

</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/low-poly-animated-modern-guns-pack/guides-and-faq/faq.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.