> 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-cn/shen-mo-shi-mei-zhou-jiang-li.md).

# 什麽是每週奖励？

### 谁可以获得每週奖励？

所有从铜级及以上等级的 VIP 玩家皆有资格获得每週奖励。

### 每週奖励何时发放？

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

### 每週奖励在哪裡公布，以及如何领取？

请前往 VIP 页面，点击“每周奖励”以领取您的专属回馈。

### 每週奖励是如何计算的？

以下是计算每週奖励时考虑的一些条件：

* 您的 VIP 等级。
* 您在过去 7 天的投注金额&#x20;

### 每週奖励连结什麽时候失效？&#x20;

从公佈每週奖励连结那一刻起计算，有效期为 4 週。


---

# 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-cn/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.
