> For the complete documentation index, see [llms.txt](https://mrcscripts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mrcscripts.gitbook.io/docs/scripts/ufo.md). # UFO Alien UFO event with abductions, experiments, and server-wide objectives. ## MRC UFO ### Quick links * [Install Instructions](/docs/scripts/ufo/install-instructions.md) ### What is MRC UFO? MRC UFO is a FiveM resource for immersive alien UFO events. Admins (or players with the right item) can trigger an abduction event. Players can become aliens, abduct others, and run experiments. ### Features * Flyable UFO ship with tractor beam. * Abduct players with interactive beam mechanics. * Alien experiments with rewards. * Alien hub / prison for abducted players. * Tin foil hat protection against abductions. * Configurable experiments, loot tables, and shop. ### Requirements * A FiveM server * [community\_bridge](https://github.com/TheOrderFivem/community_bridge/tree/dev) (must start before `mrc-ufo`) * Framework: QBCore, QBox, ESX * Inventory, target, and input systems supported by `community_bridge` --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://mrcscripts.gitbook.io/docs/scripts/ufo.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 `build a script that syncs our docs to a CMS` 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.