Addon Guidelines

These guidelines are designed to ensure a fair, consistent, and high-quality addon ecosystem for Plex Development products. Adherence to these guidelines is mandatory for all addon developers. Failure to comply may result in the removal of your addon.

1. Originality and Uniqueness

• Addons must be original and not substantially similar to existing addons, especially those sold or officially distributed through the Plex Development store.

• This includes, but is not limited to:

  • Clones

  • Near-identical copies

  • Addons that replicate core functionality with only minor changes

• Addons that replicate functionality of free addons in the Plex Development store may be allowed, but only if they introduce significant improvements, enhancements, or unique features.

2. Content and Functionality

• Addons must not contain malicious code, malware, spyware, or any harmful functionality.

• Addons must not infringe on copyrights, trademarks, or intellectual property rights.

• Addons must not collect, store, or transmit user data without explicit user consent and clear disclosure.

• Addons must function as advertised.

  • Misleading descriptions, exaggerated claims, or broken functionality may result in immediate removal.

3. Points and Rewards System

Points awarded for publishing addons are based on multiple factors, including but not limited to:

• Complexity and feature depth More advanced and feature-rich addons typically receive more points.

• Quality of presentation A clear, well-written addon description, including screenshots and/or videos, significantly affects point allocation. Descriptions should clearly explain:

  • What the addon does

  • Key features

  • How to install and use it

• Overall effort and quality Very low-effort or low-quality addons may receive very few points or none at all.

4. Maintenance and Compatibility

• Addons must remain compatible with current versions of Plex Development products.

• Addons that become severely outdated or non-functional may be removed.

• If a developer is unable or unwilling to maintain an addon, it may be removed to prevent confusion or support issues.

5. Support, Promotion, and Community Safety

To protect users and maintain a centralized, safe support environment:

• Addon developers are NOT allowed to require users to join or use their own Discord server for support if the addon is:

  • Published in,

  • Advertised in, or

  • Distributed through the Plex Development Discord server or platform.

• This includes:

  • Linking personal Discord servers for mandatory support

  • Gating support behind external communities

  • Redirecting users away from Plex Development for primary addon support

Allowed Exception

• This rule does NOT apply if:

  • The addon is not published or advertised within Plex Development, and

  • The addon is fully promoted and distributed through the developer’s own website or platform.

6. Code Obfuscation, Encryption & Licensing Systems

• Addons are allowed to be obfuscated or encrypted to protect intellectual property.

• Addons may include a license key system, authentication system, or external verification service provided by the addon creator.

Approval Requirement for Obfuscated Addons

• Any addon that is obfuscated or encrypted must receive prior approval from Plex Development staff before being published.

• Approval must be requested through a support ticket, where staff will review the addon to ensure it does not contain:

  • Malicious or harmful code

  • Unauthorized data collection

  • Hidden or misleading functionality

• Publishing an obfuscated addon without prior approval may result in immediate removal.

Reliability & Uptime Requirements

• If an addon includes a license key system, authentication service, or external dependency:

  • The system must be reliable, stable, and have good uptime.

  • It must not frequently go offline, block legitimate users, or cause repeated functionality issues.

• If a licensing or authentication system:

  • Regularly goes down,

  • Prevents users from using the addon,

  • Or causes significant support issues,

  Plex Development reserves the right to remove the addon to protect user experience and platform reliability.

Transparency Requirement

• Addons using obfuscation, encryption, or licensing systems must clearly disclose this in their addon description.

• Users should be informed if the addon depends on:

  • External servers

  • License validation

  • Online authentication to function

We're building an ecosystem of innovation, learning, and quality. Whether you're creating a simple utility or a complex solution, we welcome your contributions!

By following these guidelines and utilizing the provided documentation, you can create addons that enhance the Plex Development ecosystem and benefit our users. We look forward to seeing your innovative creations!