> For the complete documentation index, see [llms.txt](https://docs.gigaverse.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gigaverse.io/zh/diao-yu/diao-yu-ji-neng.md).

# 钓鱼技能

要精通钓鱼，玩家需要不断提升钓鱼技能等级。通过出售鱼获得的海藻可用于升级技能。

当前共有8种技能类型：

* Stamana：增加起始法力值
* Hookery：提高抛竿的暴击几率
* Jebaitor：提高抛竿时不消耗鱼饵的几率
* Weed Dealer：提高鱼的出售价格
* Fish Snob：提高鱼的品质等级变高（+1）的几率
* Luck：提高鱼的稀有度变高（+1）的几率
* Rod Handling：提高揭示下一回合鱼行动的几率
* Doubler：提高一次抛竿捕获两条鱼的几率

{% hint style="danger" %}
目前无法洗点，请三思后再加点。
{% endhint %}

<figure><img src="https://2356007408-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ficab3JzUz7MddSO6Rfl1%2Fuploads%2FfL97MN99uBPviK97l1D6%2F16-1.gif?alt=media&#x26;token=c469740d-1552-4886-9e23-c252a83a4dc7" alt=""><figcaption><p>钓鱼技能</p></figcaption></figure>


---

# 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://docs.gigaverse.io/zh/diao-yu/diao-yu-ji-neng.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.
