> 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/chang-jian-wen-ti/d1ce-you-xiao-tou-zhu-jinegui-ze-shuo-ming.md).

# D1CE有效投注金額規則說明

為了確保每位參與者能夠清楚理解活動規則，特此說明有效投注金額的計算方式。本規則旨在確定投注金額在不同結果下的具體處理方式，從而保障公平公正的參與環境。無論投注結果如何，參與者都需依照以下規範進行計算，確保透明且一致的處理過程。

以下是有效投注金額的具體計算規則，請仔細閱讀並理解：

1. **輸掉的情況**

若投注結果為虧損（即輸掉），則有效投注金額將等於實際虧損的金額。

2. **贏得金額少於或等於投注本金的情況**

若投注結果為勝出，但贏得金額小於或等於投注本金，則有效投注金額將等於實際贏得金額。

3. **贏得金額超過投注本金的情況**

若投注結果為勝出，且贏得金額超過投注本金，則有效投注金額將等於原投注金額。

***

#### 範例說明

{% hint style="info" %}
為了幫助參與者更好理解上述規則，以下是幾個常見情況的具體範例：
{% endhint %}

| 投注結果      | 範例              | 有效投注金額計算         |
| --------- | --------------- | ---------------- |
| 輸掉        | 投注 $100，輸掉 $100 | 有效投注 = 輸掉金額 $100 |
| 贏得少於或等於本金 | 投注 $100，贏得 $50  | 有效投注 = 贏得金額 $50  |
| 贏得超過本金    | 投注 $100，贏得 $300 | 有效投注 = 投注金額 $100 |


---

# 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/chang-jian-wen-ti/d1ce-you-xiao-tou-zhu-jinegui-ze-shuo-ming.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.