Manage and share plugins
Roles
The owner controls metadata, source uploads, visibility, invitations, and deletion. An invited member first appears as pending. After accepting, that member can load the compiled plugin in Mint Client, but cannot edit ownership settings or invite other people.
Invite someone in Plugin Studio
- Open Plugins and find a plugin you own.
- Open its member/invite action.
- Enter the other OriginMint user’s UUID and a display name.
- Send the invite.
The plugin immediately appears in the invited user’s list as Invited. They must select Accept before Mint Client will load it. They can also decline, which removes them from the member list.
Remove someone
Open the owned plugin’s member list and choose Remove beside the user. Removal works for both a pending invite and an accepted member. It prevents future loads; if the plugin is already running on another machine, allow that client session to stop and refresh before treating removal as complete.
Members can choose Leave Plugin themselves. Owners cannot leave their own plugin; they must transfer the work manually to a new plugin or delete it.
Public, unlisted, and private
| Setting | Discovery | Source/template | Who can load at runtime |
|---|---|---|---|
| Public, not private | Marketplace | Any authenticated Mint Client owner | Owner and accepted members |
| Unlisted, not private | Hidden from marketplace | Anyone with the ID | Owner and accepted members |
| Private | Public only if Public is also enabled | Owner only | Owner and accepted members |
Public does not make someone a member, and private does not prevent an accepted member from loading the compiled result. Use invitations to control runtime access; use private to protect source.
Refreshing data
Plugin Studio does not need to be restarted after another person accepts or after marketplace data changes. Use Refresh Plugins on your plugin list or Refresh Marketplace on the marketplace screen.