> For the complete documentation index, see [llms.txt](https://drfx-store.gitbook.io/drfx-store-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://drfx-store.gitbook.io/drfx-store-docs/documentation/resources-and-guides/frequently-asked-questions.md). # Frequently Asked Questions Common questions about DrFx purchases, installation, and support. ### Where do I download my purchase? Use your Tebex purchase history. Escrow-protected FiveM assets are downloaded from the CFX Keymaster account linked to the purchase. ### Why is the resource missing from Keymaster? Confirm that you signed in with the same CFX account used during checkout. If it is still missing, open a support ticket with your Tebex transaction information. ### Can I rename the resource folder? Keep the original name unless the product README explicitly says renaming is supported. ### Why does the resource fail to start? Check that every listed dependency starts first, the folder structure is complete, and server.cfg contains the correct resource entry. The first console error usually points to the real cause. ### Can I share or resell the files? No. Do not share paid or escrow-protected files, license access, or account credentials. ### What happens if a product is hidden or removed from the store? The catalog and this documentation can change independently. Existing delivery and license access depend on Tebex and CFX policies, while the live store remains the source of truth for current availability. ### Where do I get support? Join and open a ticket with clear error 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://drfx-store.gitbook.io/drfx-store-docs/documentation/resources-and-guides/frequently-asked-questions.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.