Skip to main content

Action marketplace

The action marketplace separates action authorship from server-side usage.

Use this concept page to understand how marketplace actions, installed actions, and custom actions relate to each other across Creator Space and the server admin UI.

The three action types​

dzbot now distinguishes between three action states:

  • Marketplace actions: creator-owned action definitions maintained in Creator Space -> Actions
  • Installed actions: server-local copies of marketplace actions shown in Server Admin -> Actions -> Installed
  • Custom actions: server-owned actions created directly in Server Admin -> Actions -> Custom Actions

Creator workflow​

Creators can:

  • create a new action in Creator Space -> Actions
  • define the Lua script, trigger event, and configuration schema
  • decide whether the action is public and visible in the marketplace

Marketplace actions are the source of truth for the code that runs on installed marketplace actions.

Server admin workflow​

Server staff use three tabs in Server Admin -> Actions:

  • Marketplace: browse public creator actions and install them on the current server
  • Installed: manage marketplace actions already installed on the server
  • Custom Actions: create and maintain server-owned actions with local code

Installed marketplace actions do not expose the creator’s Lua code in the admin UI. Server staff configure the available fields and can enable or disable the action, but the script itself remains managed by the creator.

The permission split is:

  • actions.edit for server-local settings and the active toggle
  • actions.manage_marketplace for installing or removing marketplace actions
  • actions.edit_code for authoring custom server actions

Configuration behavior​

Marketplace action authors define the configuration schema once.

When a server installs that action:

  • the installed action inherits the creator-defined trigger event, script, and configuration schema
  • the server stores its own configuration values
  • runtime execution uses the server-local configuration together with the creator-defined code

This keeps creator-owned logic reusable while still allowing each server to configure it independently.

Custom actions​

Custom actions remain fully server-owned:

  • the server admin team writes and edits the Lua code locally
  • the action appears only on that server
  • actions.edit_code is still required to modify the script or schema

Operational note​

Installed marketplace actions currently follow the latest saved marketplace definition immediately. There is no separate action versioning layer yet, unlike the mod marketplace.