If your addon is already in a public GitHub repository, publishing takes about a minute. There’s no registration and no approval queue.
Your listing stays in sync with the repository’s default branch. When the file changes, DiscordAddons re-validates and re-scans it and updates the version automatically, so you never have to re-publish. Names and descriptions you edit on DiscordAddons are kept; everything else follows your source.
File name must end in .plugin.js. The metadata comment must be on the first line:
/**
* @name MyPlugin
* @author yourname
* @description What it does, in one sentence.
* @version 1.0.0
* @source https://github.com/you/my-plugin
*/
module.exports = class MyPlugin {
start() {}
stop() {}
};File name must end in .theme.css, with the same metadata header (@name, @author, @description, and ideally @version).
Vencord plugins are TypeScript modules compiled into Vencord. Publish either a single .ts/.tsx file, or a folder by selecting its index.ts/index.tsx. The whole folder, including helper modules, styles and native.ts, becomes the download. The entry must export a definePlugin call:
import definePlugin from "@utils/types";
export default definePlugin({
name: "MyPlugin",
description: "What it does, in one sentence.",
authors: [{ name: "yourname", id: 0n }],
start() {},
stop() {},
});If your name or description is computed (for example, from a constant in another file), you’ll be asked to type it in. Users install your plugin by placing it in src/userplugins of a Vencord source build, and your listing explains this.
Any CSS file works. A BetterDiscord-style metadata header is recommended so Vencord shows a proper name in its theme list.