> For the complete documentation index, see [llms.txt](https://doc.d1ce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.d1ce.com/blog-zh-tw/shen-mo-shi-mei-zhou-jiang-li.md).

# 什麼是每週獎勵？

### 誰可以獲得每週獎勵？

所有從銅級及以上等級的 VIP 玩家皆有資格獲得每週獎勵。

### 每週獎勵何時發放？

每周六 00:00 (GMT+8)發放。

### 每週獎勵在哪裡公布，以及如何領取？

請打開 VIP 頁面，並點選 「每週獎勵」 以領取您的專屬回饋。

### 每週獎勵是如何計算的？

以下是計算每週獎勵時考慮的一些條件：

* 您的 VIP 等級。
* 您在過去 7 天的投注金額。

### 每週獎勵連結什麼時候失效？

從公佈每週獎勵連結那一刻起計算，有效期為 4 週。

\ <br>


---

# 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://doc.d1ce.com/blog-zh-tw/shen-mo-shi-mei-zhou-jiang-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.
