Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/joshuaKnauber/serpens_addon_market/llms.txt

Use this file to discover all available pages before exploring further.

The update command lets you modify an existing marketplace submission without removing it manually first. After you identify the entry you want to change, the bot shows your current values for each field and guides you through replacing them one at a time — including any file attachments. Under the hood, the update flow removes your old entry and appends the new one to the marketplace’s JSON store, then commits and pushes the changes to GitHub automatically.

Update Steps

1

Start the conversation

Type update in #addon-market or #commands. The bot asks what type of content you want to update.
2

Select the Addon type

Reply with Addon or A. The bot looks up all addons associated with your Discord user ID and lists them by name.
3

Type the name of the addon to update

Type the name of the addon you want to update (matching is case-insensitive). The bot confirms: “Got it! Next send me the new message you copied in serpens!”If no addons are found under your account, the bot ends the conversation and lets you know.
4

Paste the new Serpens JSON export string

Copy the updated export string from within Serpens and paste it into the channel. The bot validates the JSON and reads the external and blend flags to determine the next steps.
5

Provide updated file attachments (if required)

The same file attachment logic as upload applies:
  • external: true and blend: false — No file needed. The old entry is removed, the new entry is saved, and the bot confirms: “Thanks for uploading your addon! It might take a few minutes to show up on the marketplace!”
  • external: true and blend: true — No zip file needed. The bot asks you to attach a .blend file directly. Once received, the old entry is removed, the new entry is saved, and the bot confirms: “Thanks for uploading your addon and blend file! It might take a few minutes to show up on the marketplace!”
  • external: false and blend: false — Attach your updated .zip file. Once uploaded, the entry is saved and the bot confirms: “Thanks for uploading your addon!”
  • external: false and blend: true — Attach your updated .zip file first. After the zip is accepted, attach the updated .blend example file. Once both files are received, the entry is saved and the bot confirms: “Thanks for uploading your addon and blend file! It might take a few minutes to show up on the marketplace!”
Only the original submitter can update an entry. The bot filters all addon, snippet, and package lookups by your Discord user ID — you will only see and be able to update entries you personally submitted.
You can type cancel at any point during the update conversation to abort the operation. The bot discards all pending changes and your existing marketplace entry remains untouched.
The bot automatically deletes your messages after processing each reply. This keeps the marketplace channels tidy and prevents sensitive information (such as your JSON export string) from lingering in the channel history.
Internally, update is implemented as a remove-then-add operation. The bot deletes your original entry from the JSON store and appends the new version. After the update is complete, the bot automatically runs git add, git commit, and git push — so your changes are committed to GitHub immediately, though the marketplace itself may take a few minutes to reflect them.

Build docs developers (and LLMs) love