> For the complete documentation index, see [llms.txt](https://casefun.gitbook.io/casefun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://casefun.gitbook.io/casefun/mechanics-no-code-case-creator.md).

# Mechanics: No-Code Case Creator

## 🛠 Mechanics: No-Code Case Creator

The **CaseFun Creator Module** ([casefun.net/create](https://casefun.net/create)) is a permissionless No-Code SaaS tool that allows project leads, community managers, and creators to design, configure, and deploy custom gamified cases in minutes.

***

### ⚙️ Case Parameter Configuration

When creating a new case, the creator configures the following operational parameters:

| Parameter                | Type / Format          | Function & Strategic Value                                                                                                             |
| ------------------------ | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Case Name**            | Text String            | Public title displayed across the Web interface and Telegram Mini App (TMA).                                                           |
| **Token Ticker**         | Symbol / Text          | Ticker symbol of the underlying token reward distributed through the case.                                                             |
| **Open Price**           | Numeric (USD / Native) | Cost required for a user to execute a single case opening or enter PvP battles.                                                        |
| **Token Price**          | Numeric (USD)          | Fixed valuation of an individual token, used to compute drop values.                                                                   |
| **Liquidity Percentage** | Percentage (10%–98%)   | **Automated DEX Liquidity Allocation.** Portion of gross revenue automatically injected into DEX liquidity pools upon campaign expiry. |
| **Case Duration**        | Time Limit             | Operational window during which users can open cases or challenge in PvP battles.                                                      |
| **Token Logo**           | Image / Emoji          | Visual identity of the case (custom uploaded graphics or preset emoji sets).                                                           |
| **Drops Count**          | Range (2 to 10)        | Sets the total number of distinct reward tiers available inside the case.                                                              |

***

### 🎯 Individual Drop Tier Architecture

Every case contains between **2 and 10 individual drop tiers**. Each tier is customized independently:

1. **Value (Token Quantity):** The exact number of tokens awarded to the user if this specific drop tier is triggered.
2. **Probability of Occurring (%):** The exact statistical chance of this outcome occurring, governed by CaseFun's **Provably Fair protocol**.

***

### 🌐 Supported Networks & Deployment Fees

* **Deployment Fee:** **$1.50** per case creation.
* **Currently Supported Networks:**
  * Ethereum Sepolia (`Sepolia ETH`)
  * TON Testnet (`TON`)
  * BOT Chain Testnet (`BOT`)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://casefun.gitbook.io/casefun/mechanics-no-code-case-creator.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.