Source Access Guide

Despical’s Plugin Hub keeps your premium plugin purchases, downloads, linked accounts, and eligible source repositories together. When source access is available for a plugin you own, the Hub grants your connected GitHub account access to its private repository.

Access depends on the plugin

A premium plugin purchase does not automatically guarantee a private repository. The Source Access page in the Hub is the current source of truth for eligibility and access status.

---

Getting access

1. Create your Plugin Hub account. Sign in with Discord to create or access your customer account.
2. Verify your purchase. Link the Spigot profile that purchased your plugins. For a premium plugin purchased on BuiltByBit, open a Hub support ticket so the purchase can be reviewed manually.
3. Connect your GitHub account. Choose the GitHub account that should receive private repository access.
4. Wait for the access review. Supported repositories will appear on your Hub Source Access page and become available through the connected GitHub account.

Manage source accessRead the Hub guide

---

What source access includes

Private GitHub Access

Eligible purchases give your connected GitHub account read access to the plugin's private repository. Follow commits, inspect changes, and pull available source updates without sharing credentials.

Early Updates & Documentation

Keep release information, source changes, and available project documentation close together, making it easier to review an update before deploying it to your server.

Verified Plugin Library

Keep recognized premium purchases in one account. The Hub Source Access page shows which plugins are eligible, which GitHub account is connected, and the current review status.

Marketplace Verification Support

Spigot purchases are checked through your linked account. If you purchased a premium plugin on BuiltByBit, open a Hub ticket so the purchase and source-access eligibility can be reviewed manually. Open a support ticket.

---

Before opening a repository

Source access does not transfer ownership of a plugin, its source code, branding, or documentation. Your premium license remains personal, revocable, non-exclusive, and non-transferable.

• Keep your Plugin Hub, marketplace, and GitHub credentials private.
• Do not redistribute, leak, mirror, upload, gift, rent, resell, or sublicense the plugin, its source, or compiled builds.
• Do not remove copyright notices, bypass licensing controls, or present modified copies as your own product.
• Keep proof of purchase and protect any private backups or files downloaded from a repository.
• Give employees or contractors access only when it is necessary to operate servers you own or directly manage, and remain responsible for that access.

The current EULA controls

This page is a practical access guide, not a replacement for the license agreement. Always review the current Premium Plugin EULA before using a private repository.

---

If access does not appear

Check the following before contacting support:

1. For a Spigot purchase, make sure the account linked in the Hub is the account that purchased the plugin.
2. For a BuiltByBit purchase, open a Hub ticket and include the plugin name and the information needed to locate the purchase.
3. Confirm that the GitHub username shown in Linked Accounts is the account you intend to use.
4. Check the Hub’s Source Access page for the plugin’s eligibility and review status.
5. Allow time for the review and GitHub access to be applied.

If everything is correct and access is still missing, contact support with the plugin name and the marketplace account used for the purchase. Never send passwords, recovery codes, or private credentials.