> For the complete documentation index, see [llms.txt](https://metafluence.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metafluence.gitbook.io/docs/game-fi-elements/mini-games.md).
# Mini games
## **"Dancing" Mini-game Overview**
“Dancing” is a short mini-game in the **Events Room** (metahut). Users can approach the **dance pole** and initiate the mini-game by pressing & holding **the “G” key** on the keyboard.
* Only 4 users can play at a time. Each player occupies one of 4 slots on the dancing pole.
AIM of the Feature
* More interactions & retention.
* Add dynamic activities in metahuts.
* New sources of AP income.
* Just fun 
### **Gameplay**
When the game starts, the player starts dancing (animation), the camera is locked in a fixed position. Players must **press the key (some Quick Time Event)** shown on the screen **in time** (challenge = timing mechanic) to continue dancing. Each \[successfully] pressed key changes the dancing animation of the player.
* **REWARD:** Each correct move gives the player **+10** **ES\*(combo count)** (engagement score) reward (can be changed). Max. The reward per session is 200 ES.
* **RISK (COST):** 10 Energy\* *(Energy is not integrated yet).*
* **SCORING:** Consequent successful key presses (animation transitions) are recorded as a **combo score.**
* User score is recorded & visible to all players as a leaderboard. **Each metahut keeps its leaderboard (local).**
* The combo score is displayed on the screen (right-down corner).
{% hint style="success" %}
**Notes**
* All users within the metahut can see playing users on the dance pole (the camera angle is locked only for playing users).
* When users initiate the game, a text notification is shown in text chat (*“@user started “Dance” mini-game in Event Room!”* ).
* In future updates, players can enter dance duels against other users (competition).
{% endhint %}
### **Conditions**
A player must **press the required key in time** (when the **colored circle** is in the white circle) in order to perform successful “transitions” of the dance moves.
**The game does not end until the player stops it manually.**
* **The goal** is to get as high a reward as possible (max. move count is 20).
* **Fail condition:** when a player fails, the speed of the circle and the player’s combo score resets.
Game Loop Diagram
{% hint style="success" %}
* Pressing **any key** outside the circle **is not** a **fail condition.**
* Pressing **the wrong key** while within the white circle **is** a **fail condition.**
* Not pressing **the correct key** within the white circle **is** a **fail condition.**
{% endhint %}
### **Progression**
**Time for a key press (QTE) decreases as the player plays longer, making succeeding harder.**
With default speed, at the start, the colored circle reaches the center in 2.5 sec. The speed of the circle increases by 5% with each successful move (starting from 3rd successful move). **Max. The speed gain** is +100% (200% in total).
### **Controls**
* **Start game:** press & hold **“G”** key on dance pole when “party mode” is active (Events Room).
* **Dance moves:** press **the “W, A, S, D”** keys.
* **Exit game:** press & hold the “**Esc**” key.
### **Mini-game UI**
* Circles change colors based on success & failure.
* After each successful key pressing, a motivating animated text is displayed:
* **2nd press - “Combo”,**
* **4th press- “Cool”,**
* **7th press - “Great”,**
* **10th press - “Super!”,**
* **15th press - “Awesome!”**
{% hint style="info" %}
The same text continues to appear **until the combo is broken** or the **next text appears.**
{% endhint %}
### **Visual Effects**
* Visual “burst” effect on every successful animation change.
* *Glowing of avatar (tbd).*
---
# 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:
```
GET https://metafluence.gitbook.io/docs/game-fi-elements/mini-games.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.