Understand the listings, copy code, use the download waiting page and send a useful review without creating an account.
Read a collection in five steps
- Find the exact game and confirm the collection name.
- Read each relevant entry and its reported features.
- Check the full code and any explicit related executor information.
- Open the script page and check its title before downloading.
- Keep the entry reference when asking a question or writing a review.
| Signal | Useful interpretation |
|---|---|
| Selected script | The Lua file on the script page. |
| Updated information | A data update, not necessarily a successful execution test. |
| No reviews yet | No approved public reviews for this specific target. |
| Unavailable download | No current eligible file or approved destination is available. |
Frequently asked questions
Does an entry guarantee that a script works?
No. Descriptions and status fields report available source information. They are not a guarantee of execution, safety, compatibility or protection from account restrictions.
Can I download a specific script?
Each script has its own page. Copy and Download on that page refer to the same Lua entry. Open a game collection to compare cards, then open the script you need. Download binds that script and its current code revision; another card cannot silently replace it. Saving a Lua file does not run it.
Can I use the catalog without accepting optional cookies?
Yes. Choosing necessary cookies only keeps the core catalog, language navigation, code viewing, review form and download process available.
Why is my review missing?
New reviews wait for moderation. Only approved reviews become public and contribute to displayed ratings. Avoid submitting the same review repeatedly.
Does no key mean that every requirement is removed?
No. It describes a reported access condition of the named entry. It does not establish platform support, permission under game rules or the requirements of another tool.
What should I do when a download becomes unavailable?
Return to the game or executor profile and check its current state. If the source changed, start a new request. Report a persistent issue with the page address and entry name.
If copying is unavailable, select the visible code manually. The code block can scroll horizontally without moving the whole page. Copying source text does not execute it.
If a waiting page expires or reports a changed item, return to its original collection and begin again. Repeatedly changing query parameters cannot repair a revoked source. For a persistent issue, describe the page, language, entry and time in a message to the contact address.
For review corrections or removal requests, identify the target and quote a short distinctive part of your own review. Do not send sensitive identity documents unless a justified verification need is explained through an appropriate channel.