Before you start
- A signed-in account with a claimed
@handle. The listing’s identity is@handle/<name>. - The Rebind app running and signed in.
rebind publishuploads through the app’s session.
marketplace_publish). Source protection additionally
requires an activated Rebind Link owned by the account.
Publishing without source protection does not require hardware.
Workflow
rebind init <name>scaffolds a package with a commented-out[marketplace]block. Fill insummary,category, andmedia, addtitleif the storefront name should differ from the package name, and add[marketplace.price]for a paid listing.rebind checkvalidates the package offline, the listing block included.rebind previewopens a local HTML approximation of the listing. No sign-in needed.rebind publishruns check and lint, builds the package (or bundles a DRM listing into one sealed file), uploads the media, and submits the version for review.
Review
Every publish creates a version that waits for review. A listing is invisible to buyers until its first version is approved, and one version per listing can be in review at a time; publishing again before the decision is refused. Review covers every readable.lua and .luau file in the submitted version
without running it. The decision is bound to that exact submission. If its
contents change, it must be reviewed again. Encrypted executable content that
cannot be inspected remains pending unless an administrator explicitly accepts
that limitation.
Publish in the app’s Marketplace rail is where a listing is managed after
publish: its Listings section shows each listing with its status, the live
version, the version in review, the reviewer’s note, and the actions below. The
outcome also arrives by email:
- Approved. The version goes live. Buyers who already installed it see an update.
- Rejected. The reviewer’s note is in the email and on the listing’s row. Fix it and publish again; the refused version string can be reused. A rejected version never touches what buyers already have.
Republishing
A live listing is never edited in place. Publishing again stages everything the new version proposes, the code and every listing field including the price, and it goes live only when that version is approved. The version string must be one you have not published before. A price change reaches new buyers only; the rule for existing subscribers is in Package format. Other changes land like this once the version is approved:- Free to paid. Everyone who took the script while it was free keeps it. Guest downloads keep the local file, not account access to later paid updates.
- Dropping the subscription. Making a listing free, or lifetime only, ends every subscription to it. Subscribers are told, keep access to the end of the period they paid for, and are not charged again.
- Renaming.
title, summary, media, and README change with the version. The listing’sslugnever changes. - Turning DRM on or off. Buyers who already installed keep the file they have. Their next update replaces the tracked listing after checking access and hardware requirements. Older name-based installs are left untouched.
Unlisting
Use Make private on the listing’s row under Publish. The flag applies immediately and skips review. What a private listing is and is not is in the field table. Existing buyers keep their access and updates. Make public reverses it. Aprivate key
stated in rebind.toml wins at every publish; leave it out to manage the flag
from the app.
Share a private listing with Copy link on its page in the app. The link
opens the listing in the recipient’s Rebind.