How to publish

1. Prepare the package

Upload one ZIP (max 100 MB) with the files laid out the way they go on the server:

my-mode/
├─ kmp.toml            ← recommended: name, version, permissions
├─ init.lua            ← or your mode's main file
├─ client/10-hud.lua   ← client half (max 64 files, 256 KB each, 2 MB total)
└─ ui/ui.toml          ← web UI, if any

No .exe, .bat, .ps1 or other executables. A .dll (C# mode) is allowed but always goes to manual review.

kmp.toml

[package]
name = "economy-core"
author = "your-name"
version = "1.0.0"
kind = "module"          # gamemode | module | client | ui | map | config | sounds | asset-pack | tool
license = "MIT"
kcdmp = ">=0.44"

[permissions]            # what the script needs on the server; undeclared use raises the risk score
luanet = ["System.Net.Http"]
os = ["getenv", "time"]

KCD:MP server scripts run without a sandbox: they can read files, reach the network and use .NET. Declaring permissions tells server owners what to expect and speeds up review.

2. Images

• 16:9, ideally 1920 × 1080 px, at least 640 px wide. Other ratios are centre-cropped on cards.
• JPG, PNG, WebP, GIF or AVIF, up to 8 MB each, 10 images. We convert to WebP and strip EXIF and location data.
• The first image is the cover. Use an in-game shot without text near the edges and without third-party logos. Reorder with ← → or "Cover".
• Show what the item does: the UI, the map, the action. No phone photos of a monitor.

3. Videos

Paste a YouTube link (youtube.com/watch?v=…, youtu.be/…, Shorts) or a Medal clip, up to 4 videos. YouTube plays right on the page and the trailer is shown first. An item with only a video uses its still as the cover.

4. Description

Markdown is supported: headings (##), lists, bold, code and code blocks, tables, links. A good description has:

1. What it does in two or three sentences.
2. Features as a list.
3. Installation: where to unpack, what to add to server.toml, dependencies.
4. Configuration and commands.
5. Known issues and a link to source code or support (Discord, GitHub).

Tips

Add a tip / donation link in the item details: Ko-fi, Patreon, PayPal (paypal.me or a donate button), Buy Me a Coffee, GitHub Sponsors, Liberapay, Open Collective or a Stripe payment link. Players see ♥ Support the author next to the download. Tips are always voluntary: the download, features and support must never depend on them (Warhorse / PLAION rules). My work shows how many people clicked the button.

5. Versions and compatibility

• Version numbers follow SemVer (1.2.0). Fixes bump the last number, new features the middle one.
• Set KCD:MP from / to for the releases you tested. KCD:MP ships every few days; after each release the item shows "not verified" until you confirm it in My work with Confirm it works.
• The beta channel doesn't replace the stable version shown to everyone.
• A broken version can be withdrawn in My work; the previous one becomes current.

6. Review

1. Upload the package as a .zip, or link a file of a GitHub release (it then takes no space here and downloads come from there). A scanner checks the archive (limits, executables, dangerous Lua and .NET calls, obfuscation, data exfiltration).
2. A moderator reviews new creators and anything risky, with a diff against your previous version. A rejection always comes with reasons.
3. Trust grows with your track record. As a new creator everything is reviewed. After 3 approved versions (and no rejection in 90 days) you are trusted: clean updates of your published items go live at once, new items are still reviewed. After 10 approved versions, 2 published items and 30 days you are verified: clean new items go live at once too. Risky scans are always reviewed, and a rejection or a malware report puts you back to full review.
4. Published files are signed (Ed25519). The SHA-256 and signature are on the Versions tab.

Publishing requires two-factor authentication (Settings → 2FA).