Skip to main content

Guidelines

These are guidelines that all plugins are expected to abide by. Any plugin that violates these will not be added to the BetterDiscord website or marked as official or approved in any fashion. Existing plugins that push updates that violate these guidelines will have their updates denied.

General Guidelines​

  1. Addons must be in public GitHub repositories.
  2. Addons must not negatively affect users.
    • e.g., ban risk, disabling security features, accessing private information
  3. Addons must not discriminate whom can use it.
  4. Addons must not collect user data without opt-in consent.
  5. Addons must not include explicit sexual material or other adult content.

Scope​

  1. Plugins must clean up all changes/modification made by the plugin when it is disabled.
    • This includes UI changes, patches, intervals, timeouts, subscriptions, and listeners.
  2. Plugins and their corresponding libraries shall not operate outside of their intended functionality.
    • This includes but is not limited to: swapping out unrelated components, introducing unnecessary buttons or badges.
  3. Plugins must not modify the BetterDiscord UI.
    • This is to maintain a consistent UI/UX, prevent user confusion, and prevent errors.
  4. Plugins must not touch or use BetterDiscord's files.

Code​

  1. Plugins must set module.exports
  2. Plugins must not make use of the child_process node module.
    • Existing plugins are exempt, but no new plugins shall use this. This is due in part to the security risk, and in part due to an impending Discord update that will break this module.
  3. Plugins must not modify global variables, global objects, or existing prototypes.
  4. Plugins must not access BetterDiscord globals ouside of the official API.
  5. Plugins must not access webpack modules outside of the official API.
  6. Plugins must not waste hardware resources.
    • e.g., repeated webpack searching without caching, storing unnecessary data in memory.

Security & Privacy​

  1. Plugins must not remove security features.
  2. Plugins must not access user tokens, emails, or passwords.
  3. Plugins must not risk a user's account.
    • This includes but is not limited to: selfbotting, spamming API requests, using non-user APIs, bypassing nitro features, animated status, message logging.
  4. Plugins must not provide access to potentially sensitive information from other users of the platform which is not otherwise accessible.
    • This includes but is not limited to: hidden channels, deleted messages, invisible/offline status distinction.
  5. Plugins must not use remote libraries.
    • Necessary dependencies should be either bundled or a separate plugin.
  6. Plugins must not use closed source nor self-hosted binaries or libaries.
  7. Plugins must not be obfuscated, minified, include sourcemaps, or be otherwise deceitful.