The steps
The list holds no add-on code, only a pointer to your repo and the exact version you sent. Your repo stays yours.
- Build and test itA script and one small
addon.json. Install it from your own repo and run it in the studio. The author guide covers every field. - Send it belowSign in with GitHub, then give us the repo link, the version and a picture. We take your name and profile link from your GitHub account.
- Checks run on their ownThey tell you in plain words what to fix.
- Passed? You are ListedIt shows up on the add-ons page with your picture and links. Nothing updates by itself: a new version is a new submission.
- Want Verified? AskTick the box. We read the code and run it on test inputs. Feel free to get in touch with us on Discord or X.
Send your add-on
Sign in with GitHub to submit. We only read your public profile and email, nothing else.
Sent. Thank you!
Checks are running on your submission. If they pass, you are listed. If not, the page tells you what to fix.
What we read from your addon.json
Nothing to copy or fill in twice. These fields decide how you appear:
idandname: the install name (./lab addon add your-id) and the card title. An id belongs to the first person who uses it.summary: the one line under the title.runs:local(the default) orcloud. Saycloudif it sends the user's models or pictures off their machine: users see a Cloud badge and a plain warning before they install.licence,toolsandschema: 1: required.
What the checks do
- The version is a full 40-character code, not a branch.
- Your
addon.jsonat that version is readable, names a licence and lists a tool. - The picture is a real, small PNG or JPG.
- Your add-on is installed and run on a clean test machine, and must make a real model. If we cannot run it there (it downloads models, or needs a file as input), it is listed as not run-checked.
- You own the repo, and the id is not someone else's.
The rules
- Only the owner, or a public member of the owning organisation, submits.
- No code that updates itself or downloads more code.
- Say what it does: network (including sending models off your machine), shell, files it writes, models and their licences.
- No compiled binaries we cannot read.
- Don't pass yourself off as AssetFurnace or someone else.
- Only we set Verified.
Paid add-ons and problems
Paid add-ons are a deal between you and the user. We only check that they work. If a listed add-on breaks, anyone can report it. Unanswered reports can get an add-on removed.