> For the complete documentation index, see [llms.txt](https://ersha.gitbook.io/code-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ersha.gitbook.io/code-new/xin-shou-quan-xi-tong.md).

# 新授权系统

## 新系统

* 无需手动绑定IP与端口 (授权码使用时自动绑定)
* 无需繁琐解绑，售后群快捷解绑操作 (批量解除、单个解除)
* 无需安装过多插件 (使用云端插件 **CloudPlugins** 进行加载)
* 支持 BungeeCord 安装BC云端插件 (安装后支持子服加载授权插件) / 未完成

## 页面

* [云端插件使用说明](/code-new/xin-shou-quan-xi-tong/yun-duan-cha-jian-shi-yong-shuo-ming.md) — 用于加载所购买的授权插件
* [授权时效说明](/code-new/xin-shou-quan-xi-tong/shou-quan-shi-xiao-shuo-ming.md) — 插件授权时效机制 (可永久使用)
* [授权数据迁移](/code-new/xin-shou-quan-xi-tong/shou-quan-shu-ju-qian-yi.md) — 用于老用户迁移授权数据的说明
* [授权摸鱼模式](/code-new/xin-shou-quan-xi-tong/shou-quan-mo-yu-mo-shi.md) — 适合服务器开发时期使用的模式<br>

新系统将比旧系统操作简便 **无需手动绑定IP即端口** 解除授权绑定也不需要使用太过繁琐的群命令,插件加载也就 **采取云端加载方式加载主体** 用户 **只需下载安装云端插件并通过配置用户令牌(user-token)即可通过云端加载指定插件即版本** 无需下载安装多个插件,同时将支持 **BungeeCord** 服,遗憾的是新系统将开始 **授权时效限制** 旧系统授权码迁移后也会有时效限制 <mark style="background-color:red;">**并不是有时效限制你就无法永久使用**</mark> 对应插件(详细见下文授权时效说明),同时授权码会有摸鱼模式避免授权码无使用时过度消耗时长(详细见下文摸鱼模式),同时续费时效也不一定需要通过付费 **未来将推出可以白嫖** 的机制,有一说一卖一年的插件可能还不如服务器一个月甚至半个月的收入高,疫情没法出去工作只能通过开发获取收入都是为了生活嗝


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ersha.gitbook.io/code-new/xin-shou-quan-xi-tong.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.