# Refunds It is common for customers to have basic issues with a script; immediately assume it is the script's fault, and request a refund before any type of communication or ticket has been created. Then after initial troubleshooting; it ends up being a bad installation, or a user-error. For this reason is why refunds are not granted simply upon request if you report an issue with the script. The developer will request that you submit a ticket with the following information: * Any errors in your server-side console * Verifying your installation path * Confirming the script works without any initial settings being modified If the above points appear to be fine; then the developer is going to request additional information related to your server itself so that the developer can take a look personally. Should bugs with the script be present; the developer will release updates addressing the issue. Because you are dealing with digital items; a developer cannot remove your downloaded copy of an addon. *Therefore, a refund is approved in instances where no other possible solution can be provided to address your issue in a proper amount of time; as long as the issue is with the addon itself, and NOT because of user-errors.* Which will be determined by the developer after you create your initial support ticket. --- # Agent Instructions: 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 current page URL with the `ask` query parameter: ``` GET https://vliss.rlib.io/faq/refunds.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.