> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/the-loot-economy/global-drop-caps-and-floor-rates.md).
# Global Drop Caps and Floor Rates
The availability of Tactical Gear is managed by a sophisticated scarcity engine that prevents oversupply and protects the value of rare items.
* **Dynamic Caps:** The total supply of high-tier gear scales based on total ecosystem participation. If the player base grows, the cap increases proportionally.
* **Floor Drop Rates:** To ensure fairness, every item has a defined minimum probability. No matter how many items are currently in circulation, the chance to find a specific piece of gear will never fall below this baseline.
* **Anti-Inflation:** This system ensures that Legendary and Mythic items remain prestigious and valuable over long-term cycles.
---
# 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://docs.micro.fun/the-loot-economy/global-drop-caps-and-floor-rates.md?ask=&goal=
```
`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.