> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/reference/protecting-your-code.md). # Protecting Your Code Open scripts have always been an important part of this community. They help creators learn GPC, improve their skills, and understand how other scripts solve real problems and tweak code. At the same time, we understand that some dedicated creators want a way to protect their work from copy-paste uploads, unauthorized edits, or people trying to pass off someone else's work as their own. Compiled scripts were added for that reason. | | Open Script | Compiled Script | | ------------------- | ---------------------------------------------- | -------------------------------------------------------------- | | Source code visible | Anyone can view, learn from, and copy-paste it | Source is hidden and cannot be downloaded or reversed | | Who can upload | Everyone | Only creators who meet the eligibility requirements below | | Purpose | Sharing, learning, community collaboration | Protecting original work from copy-paste or unauthorized edits | **How Compiled Scripts Work** When you publish a script as compiled only, the readable source code **cannot** be downloaded nor reversed in any way. This helps protect the code you worked on while still allowing the script to be shared through the library. As further protection, cross flashing is **not** possible. A compiled script cannot be downloaded and flashed to any device other than the one that originally downloaded it. *** **Eligibility Requirements** Because this feature is meant for trusted and active creators, it is **not** available to every account by default. To become eligible, your activity over the last **12 months** needs to show: * **3** approved scripts * **200** unique downloads * **25** total upvotes * **10** more upvotes than downvotes **Or:** * **1** approved script * **1,000** unique downloads * **25** total upvotes * **10** more upvotes than downvotes These requirements help keep private scripts reserved for creators who have shown consistent, positive contributions to the community. *** **Wildcard Exception** A "**wildcard**" system is also available for creators that helped in the past — just ask a moderator on our [Discord server](https://discord.gg/KuwFMtgVzP) to review the request. --- # 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://guide.cronuszen.com/gpcscripting/gpc-script-guide/reference/protecting-your-code.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.