> For the complete documentation index, see [llms.txt](https://radialbog9.gitbook.io/minecraft-manhunt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://radialbog9.gitbook.io/minecraft-manhunt/usage/scenarios.md).

# Scenarios

Scenarios are twists you can add to your game, to make it more interesting.

There are different types of scenarios:

* All-game: These are always active for the entirety of the game.
* Periodically: These happen every so often, and have one-time effects (e.g. dropping items or spawning mobs)
* Brief periodically: These have effects which last for a short amount of time and happens every so often (e.g. potion effects, disabling player abilities, etc).
* Change periodically: The effects are always active but change every so often (e.g. changing disguises).

These types are not visible in-game other than in the scenario description.

## Scenarios List

Similar scenarios have been grouped together in this list (e.g. Runners/hunters take no fall damage is two scenarios, one for hunters and one for runners, which can be applied separately or both at once).

| Scenario Name                                 | Type                | Requirements (if any) |
| --------------------------------------------- | ------------------- | --------------------- |
| Runners/hunters take no fall damage           | All-game            |                       |
| Runners/hunters get creative mode             | Brief periodically  |                       |
| Runners/hunters get disguised as a random mob | Change periodically | LibsDisguises         |
| Runners get disguised as a random hunter      | Change periodically | LibsDisguises         |
| Potatoes drop OP loot                         | Periodically        |                       |
| Random lucky drops at every player            | Periodically        |                       |
| Random projectile items drop at every player  | Periodically        |                       |
| Random mobs spawn at hunters                  | Periodically        |                       |
| Air is poisonous                              | All-game            |                       |
| Sneaking is disabled for all players          | Brief periodically  |                       |
| Runners/hunters get a random potion effect    | Brief periodically  |                       |
| Runners get invisibility                      | Brief periodically  |                       |
| Runners become ghosts                         | Brief periodically  |                       |
| Swaps hunters for runners                     | Change periodically |                       |

## API

If you want to add some scenarios and think they should be in the main plugin, then make a fork, add your scenario, then create a pull request!

If you want to create your own plugin with your own scenario, use the API as outlined [here](/minecraft-manhunt/developers/api.md#scenarios).


---

# 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://radialbog9.gitbook.io/minecraft-manhunt/usage/scenarios.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.