> 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/shou-ye.md).

# 首頁

歡迎來到 **OASIS**. 從這裡開始探索, 找到屬於你的冒險節奏.

***

## <mark style="color:$primary;">開始冒險</mark>

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:$primary;"><strong>加入 OASIS</strong></mark></td><td>下載整合包, 完成安裝與正版帳號登入.</td><td><a href="/kai-shi.md">開始</a></td></tr><tr><td><mark style="color:$primary;"><strong>特色玩法</strong></mark></td><td>查看捕捉, 繁殖, 探索加成, Hunt, 團戰與排位規則.</td><td><a href="/features.md">特色玩法</a></td></tr></tbody></table>

***

## <mark style="color:$primary;">遊玩與對戰</mark>

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:$primary;"><strong>連續捕捉</strong></mark></td><td>專注捕捉同一種寶可夢, 累積你的連續紀錄.</td><td><a href="/features/catch-combos.md">連續捕捉</a></td></tr><tr><td><mark style="color:$primary;"><strong>PokéStop 補給站</strong></mark></td><td>在探索途中停下腳步, 領取可用補給.</td><td><a href="/features/pokestops.md">PokéStop 補給站</a></td></tr><tr><td><mark style="color:$primary;"><strong>繁殖</strong></mark></td><td>查看配對條件, 遺傳規則, 繁殖道具與孵化領取.</td><td><a href="/features/breeding.md">繁殖</a></td></tr><tr><td><mark style="color:$primary;"><strong>排位對戰</strong></mark></td><td>加入排位配對, 查看場次獎勵, 積分衰減與賽季規則.</td><td><a href="/features/ranked.md">排位對戰</a></td></tr><tr><td><mark style="color:$primary;"><strong>Hunt 狩獵任務</strong></mark></td><td>使用指定球種完成每日捕捉目標, 領取狩獵獎金.</td><td><a href="/features/hunt.md">Hunt 狩獵任務</a></td></tr><tr><td><mark style="color:$primary;"><strong>肩部效果</strong></mark></td><td>查看肩上寶可夢提供的移動, 戰鬥與探索加成.</td><td><a href="/features/shoulder-effects.md">肩部效果</a></td></tr><tr><td><mark style="color:$primary;"><strong>Raids 團戰</strong></mark></td><td>組隊挑戰 Boss, 查看捕捉機率與各難度獎勵.</td><td><a href="/features/raids.md">Raids 團戰</a></td></tr><tr><td><mark style="color:$primary;"><strong>探寶與騎乘掉落</strong></mark></td><td>跟隨探測提示尋寶, 查看各區域探寶器與騎乘掉落.</td><td><a href="/features/dowsing.md">探寶與騎乘掉落</a></td></tr></tbody></table>

***

## <mark style="color:$primary;">規則與條例</mark>

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:$primary;"><strong>客戶端條例</strong></mark></td><td>查看客戶端修改與模組使用規範.</td><td><a href="/rule/ke-hu-duan-tiao-li.md">客戶端條例</a></td></tr><tr><td><mark style="color:$primary;"><strong>社區條例</strong></mark></td><td>了解交流, 互動與共同遊玩的規則.</td><td><a href="/rule/she-qu-tiao-li.md">社區條例</a></td></tr><tr><td><mark style="color:$primary;"><strong>用戶條例</strong></mark></td><td>查閱服務說明, 帳號與資產相關約定.</td><td><a href="/rule/yong-hu-tiao-li.md">用戶條例</a></td></tr></tbody></table>


---

# 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/shou-ye.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.