> For the complete documentation index, see [llms.txt](https://docs.getcelsius.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getcelsius.net/products/phantom-forces/features-and-modules.md). # Features & Modules Phantom Forces feature groups and in-game tabs. The script opens as a **windowed menu** with three tabs, each split into sections. Menus evolve between updates — the in-game menu is always the source of truth; this page describes the current groups. ## Combat * **Silent Aim** — hit-scan aim with configurable hitboxes, visibility handling, FOV, and target line. * **Triggerbot** — fires when your crosshair is on target. * **Aim Assist** — soft aim assistance. * **Gun Mods** — weapon behavior modifiers. * **Rage** — aggressive options such as force-hitbox and manipulation-based play. ## Visuals * **Players** — player ESP with the usual box, name, distance, skeleton, health, weapon, and chams options plus visibility/team checks. * **World** — world ESP. * **Viewmodel** — viewmodel chams with material and transparency options. * **Weapon** — weapon chams with material and transparency options. * **Tracers** — beam tracers with texture, lifetime, and thickness. ## World * **Sounds** — sound and hitmarker toggles with per-effect sound selection and volume. * **Camera** — custom FOV, third person, no flash, no stun, and related camera control. * **Lighting** — lighting modifiers. * **Movement** — movement options such as speed and related modifiers. * **Exploits** — game manipulation utilities. > The Combat and Visuals sections expose many individual toggles and sliders in-game. Where a specific option matters to a workflow (for example team checks in ESP), it is set per section in the menu. --- # 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.getcelsius.net/products/phantom-forces/features-and-modules.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.