> For the complete documentation index, see [llms.txt](https://otters-developments.gitbook.io/otters-developments/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://otters-developments.gitbook.io/otters-developments/paid-resources/airdrop/screenshots.md).
# Screenshots
Below are the main screenshot sections for Otters Airdrop.
## Airdrop Panel
Show the staff panel used to create a new supply drop and configure its location, loot tier, unlock timing and KOS options.
## Active Airdrop Manager
Show live active drops, statuses and countdowns.
## Aircraft Incoming & Parachuting Crate
Show the configured aircraft approaching the selected drop location. Show the supply crate descending after being released by the aircraft.
## Locked Crate
Show the landed crate while it is still locked, including its status/countdown where applicable.
## Ready / Loot Crate
Show the crate once it is available for players to loot.
## KOS Zone
Show the configured KOS radius around an active airdrop.
## Discord Logging
Show an example Discord webhook for airdrop activity.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://otters-developments.gitbook.io/otters-developments/paid-resources/airdrop/screenshots.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
