Guide
Publishing and moderation
Scripts are sold and given away through the Lynx marketplace. Publishing runs from the web dashboard; the in-game tab only installs and runs.
States
| State | Meaning |
|---|---|
| draft | You created the item. Only you see it. |
| pending | You uploaded a version and requested approval. A moderator will review it. |
| published | The version is live. Buyers can install it. |
| removed | A moderator took the item down. |
Publish a version
- Create the item as a draft: name, description, price, tags, up to three screenshots.
- Upload the bundle. The backend reads
manifest.json, records the version and the capability list, and signs the archive. - Write the changelog for that version.
- Request approval. The item moves to pending.
An item has one live version and at most one pending version. Uploading a new bundle while one is pending replaces the pending one.
Review
A moderator sees the manifest, the capability list, the changelog and the source. Approval promotes the pending version to live and marks its changelog entry approved.
A rejection keeps the old version live. Nothing a buyer already has changes. The rejection reason is shown on the item; fix it and request approval again.
A re-list of an item that was approved before and then unpublished by you goes live without another review, as long as the version did not change.
Unpublish and removal
You can unpublish at any time; the item returns to draft and stops appearing in the market. Installed copies keep working. A moderator can remove an item for a rule breach; removed items cannot be re-listed.
Disputes
A buyer who thinks a paid script does not do what its page says opens a dispute from their purchase. A moderator reads both sides and either closes the dispute or refunds: the buyer is credited, the author is debited, and the buyer’s installed copy is revoked. Refunds happen only through a dispute.