Modding
dzbot includes a creator marketplace where you can build, version, publish, and optionally monetize your own mods.
This guide covers the practical creator workflow from first draft to released mod.
Related guides:
Open the Creators Space
Navigation path:
Platform panel->Creators Space
Direct entry is available at https://dzbot.de/creators.
Use your dzbot account (Discord-linked account in normal workflows) to log in and manage your mods.
Mods overview
The overview is your creator dashboard for all mods you maintain.
What you can do there:
- create a new mod
- search your mods by name
- see verification status
- see whether a published (released) version exists
- see how many server installations exist
- open the latest version for editing
You can only permanently delete a mod when it is no longer installed on servers.
Mod details
The mod details page is organized into tabs:
InformationAccessFile changesConfigurationVersions
Important lifecycle rule:
- once a version is published, its file changes and configurations are locked
- further changes require creating a new version
- mod metadata (name, description, maps, public/private, price) can still be updated
Mod settings
Use the Information tab to define core metadata:
- mod name
- description
- supported maps
- public/private availability
- optional price (if payout setup is complete)
Practical note:
- for paid mods, dzbot uses Euro cents (
100 = 1 EUR) - positive prices below
100are automatically raised to100
Mod access
The Access tab shows where your mod is already present.
- for public mods: you can review installed/known server access state
- for private mods: you can explicitly allow additional servers
Private access flow:
- Open
Accesstab. - Search/add a server by name.
- Save to grant that server access.
Important behavior:
- effective install access is tied to the currently published version
- if no version is published yet, publish first
- server lookup is name-based and can match similarly named servers
Mod versions and publishing
Every mod is versioned.
Key behavior:
- a new mod starts with version 1
- only published versions are installable on servers
- creating a new version clones current files/configuration as a starting point
- old versions are viewable, but only the latest unpublished version is editable
- the next version can only be created after the current latest version is published
- servers that enabled auto-update for your mod switch to the newly released version automatically when you publish
Recommended release workflow:
- Build and test on latest editable version.
- Finalize file changes and configuration schema.
- Publish that version.
- For updates, create a new version and repeat.
Practical note:
- auto-update changes which released version a server points to, but admins still use their normal transfer/restart workflow to apply changes to the running server