> For the complete documentation index, see [llms.txt](https://fantasy-scripts.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://fantasy-scripts.gitbook.io/docs/f.a.q.md). # F.A.Q **Frequently Asked Questions** **Can I get a discount?**\ We do not offer individual discounts. Any promotions or sales we run are applied equally to all customers. *** **Do you offer custom scripts or freelance work?**\ At this time, we do not provide custom development. *** **Can I purchase scripts as open-source?**\ Only scripts listed in the “Open Source” category on our Tebex store are available in that format. If a script is not listed there, it is not available as open-source under any circumstances. Should this change, we will make an official announcement on our [Discord](https://discord.gg/nC5dpETEwy). *** **I’m having trouble setting up a script. Can you help?**\ Yes. All of our scripts come with detailed installation guides, configuration files, and helpful tips. If you still need assistance, you can reach out through our Discord support system. *** **Am I allowed to resell or share the scripts?**\ No. Reselling, redistributing, leaking, or sharing our scripts in any form is strictly prohibited. --- # 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://fantasy-scripts.gitbook.io/docs/f.a.q.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.