> For the complete documentation index, see [llms.txt](https://wiki.cobblemonoasis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.cobblemonoasis.com/rule/ke-hu-duan-tiao-li.md).

# 客戶端條例

{% hint style="info" %}
本指南用于说明 **Cobblemon OASIS** 中允许与禁止使用的客户端模组.

由于模组数量众多, 我们无法逐一审核, 文中列出的模组仅作为参考. 请根据本页面规则自行判断所使用的模组是否合规.

部分模组虽然不属于作弊, 但可能破坏 OASIS 所希望提供的公平与原生游戏体验, 因此同样可能被禁止.

如无法确定某个模组是否允许使用, 请在使用前联系管理团队确认.
{% endhint %}

### 禁止使用

禁止那些提供不公平游戏优势且违背服务器核心体验的模组或功能

判断以实际功能及效果为准, 不以模组名称, 是否付费, 是否开源或其他服务器允许使用为依据. 改名, 拆分功能或换用同类工具不改变适用规则.

\
**示例:**&#x20;

* `任何形式的透視 X-Ray`
* `自由視角 Freecam`
* `洞穴探測/礦物追蹤`
* `非官方提供的的實體追蹤`

**功能组合与数据来源.** 限制同样适用于注入, 改包, 封包伪造, 绕过验证, 异常读取隐藏信息及多个工具配合实现的同等效果. 不得通过外部接口或非公开数据源恢复已被禁止的追踪与透视功能.

#### 滑鼠宏与脚本 <a href="#macros-et-automatisations" id="macros-et-automatisations"></a>

禁止使用脚本, 宏以及任何自动化游戏或玩家操作的修改.&#x20;

**示例:**&#x20;

* `Baritone 自动寻路 / 挖矿`
* `机器人 / 代替玩家进行游戏的功能`
* `自动点击`
* `自动钓鱼`
* `自动化脚本`
* `使用重物压住鼠标 / 按键`

上述限制同样适用于外部软件, 硬件宏, 远程控制或多个工具组合实现的自动操作. 用户应对自行安装及启用的功能负责.

#### 作弊客户端 <a href="#clients-hack" id="clients-hack"></a>

任何包含作弊修改的启动器或模组包都不被允许使用.&#x20;

* **示例:**&#x20;
  * `Wurst`
  * `Meteor`
  * `Kronos`

管理团队可要求停用相关功能, 调整配置或换用不含违规功能的客户端后再连接. 对相关行为的认定与处理, 适用社区条例及用户条例.

**版本与检查范围.** 管理团队可要求使用受支持的版本, 提供与连接或违规核查直接相关的版本和配置说明. 核查不要求交出账号密码, 支付凭证密钥或无关私人文件; 软件尚未被逐一列名不构成使用许可.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.cobblemonoasis.com/rule/ke-hu-duan-tiao-li.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
