---
title: Publishing
description: An Overview of available distribution options for developers to make their plugins available to the end users
published: true
date: 2025-07-07T15:59:40.689Z
tags: 
editor: markdown
dateCreated: 2025-07-07T15:59:38.892Z
---

# Publishing Options Overview

Once your plugin is complete and tested, the next step is to **publish it** so that other players can install and use it. SE Launcher supports **two main publishing methods**, each with its own advantages and trade-offs.

---

## 1. Publishing to the Official PluginHub

This is the **recommended and most accessible** way to distribute your plugin to the community.

### Advantages:
- Your plugin becomes **immediately available** to all users via the launcher's built-in plugin browser.
- No infrastructure or server setup required.
- Users benefit from automatic updates and trust in the official source.

### Limitations:
- Your plugin must comply with a set of **publishing guidelines**, including naming, versioning, stability, and content restrictions.
- Submissions are subject to **manual approval** and review.

For more information, see the full guide:  
**[Publishing Guidelines for Official PluginHub](./publishing/guidelines)**

---

## 2. Publishing via Self-Hosted NuGet Source

Advanced users and organizations may choose to host their plugin on a **custom NuGet feed**.

### Requirements:
- A **publicly accessible domain**.
- Knowledge of **server administration** and setting up a NuGet-compatible feed.
- Responsibility for **serving, updating, and maintaining** plugin packages.

### Advantages:
- Full **control** over publishing, updates, and access.
- Ideal for **private distributions**, development builds, or alternative plugin ecosystems.

For a step-by-step guide, refer to:  
**[Distributing via Your Own Source](./publishing/custom-source)**

---

Choose the method that best suits your project goals and technical capabilities.