> 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/features/ranked.md).

# 排位對戰

使用 `/ranked` 開啟排位介面, 可以加入配對, 查看個人戰績與排行榜, 以及領取獎勵.

## 對戰流程

配對成功後, 可以先查看對手的隊伍並選擇首發寶可夢. 雙方完成選擇後, 對戰開始.

選擇招式時會計時; 若連續多個回合花費較長時間, 後續回合可用的時間會減少.

## 獎勵與賽季

隨著完成的排位場次增加, 可以取得對應獎勵. 完成 **300 場排位對戰**可獲得稀有寶可夢, 獎勵寶可夢會隨賽季更換.

賽季結束時, 排行榜名次較高的玩家可獲得更豐富的結算獎勵.

## 積分衰減

積分衰減只影響 **1200 ELO 以上**的玩家. 連續 **3 天**沒有進行排位對戰後, 會開始扣除積分; 未參賽時間越長, 每日扣分越多.

| 連續未進行排位的天數 | 每日扣除 ELO |
| ---------- | -------: |
| 3-5 天      |       10 |
| 6-7 天      |       15 |
| 8-14 天     |       20 |
| 15 天及以上    |       25 |

## 戰績與賽季資訊

{% tabs %}
{% tab title="定級資訊" %}
輸入 `/ranked`, 將滑鼠移至 **Stats** 按鈕, 即可查看排位定級資訊.
{% endtab %}

{% tab title="使用率統計" %}
使用率統計於賽季中期與季末公布, 約每月一次, 分為 **1000+, 1300+, 1500+ ELO** 三個區間.
{% endtab %}

{% tab title="平衡調整" %}
大型平衡調整於賽季中期與季末進行; 賽季期間則視需要進行較小幅度的調整.
{% endtab %}
{% endtabs %}


---

# 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, and the optional `goal` query parameter:

```
GET https://wiki.cobblemonoasis.com/features/ranked.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.