> 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-shooter-pack/getting-started/introduction.md).
# Introduction
**Welcome to the documentation for the Low Poly Shooter Pack (LPSP), a complete first-person shooter template for Unreal Engine.**
This pack provides everything you need to quickly prototype or build a fully functional stylized FPS game, including weapon systems, AI, multiplayer replication, animations, VFX, UI, and 3D models.
***
## Try the Free Demo
Take a moment to try the **Low Poly Shooter Pack Demo**! It’s a quick way to see everything in action.
Exploring the demo will give you a solid understanding of how the systems work before you start customizing your own project.
Download the Demo (Windows 64-bit)
***
## Project Overview
{% embed url="" %}
***
## First Person Animation Showcase
{% embed url="" %}
***
---
# 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-shooter-pack/getting-started/introduction.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.