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

# LootPool

Weighted loot tables you build in-game from real items, then give, drop, spawn, or fill containers with from commands, menus, or your own plugin.

LootPool is a Paper plugin for building loot tables in-game. You put real items into a chest GUI, set a weight and an amount range for each one, and LootPool saves the result as a named **loot pool**. From then on any command, AbstractMenus menu, or other plugin can roll that pool: give the loot to a player, drop it on the ground, or fill a chest with it.

A pool isn't limited to a flat list of items. It can merge other pools, pick between them by weight, wrap a vanilla loot table, replay an exact chest layout, roll a random number of items each time, or — as a [complex pool](/wyne-docs/lootpool/complex-loot-pools.md) — hold a whole loot-table structure of rolls, item modifiers and conditions. See [Pool types](/wyne-docs/lootpool/pool-types.md).

## What it gives you

* **An in-game editor.** `/lootpool pool create <key>` opens a chest GUI: drop items in, then click to set each one's weight and minimum and maximum amount. No item stacks to write by hand. See [The loot editor](/wyne-docs/lootpool/the-loot-editor.md).
* **Eight pool types that build on each other.** Plain weighted lists, single named items, pools of pools (merged or weighted against each other), roll-count wrappers, container snapshots, vanilla loot tables, and complex pools. See [Pool types](/wyne-docs/lootpool/pool-types.md).
* **Loot-table structure when you need it.** Rolls with their own counts, item modifiers that enchant, wear, rename or smelt what was rolled, and conditions on the world, the biome, the time, the weather, a permission or a placeholder. See [Complex loot pools](/wyne-docs/lootpool/complex-loot-pools.md).
* **Reusable enchantment pools.** Named sets of weighted enchantments with level ranges, so one plain sword template becomes a spread of differently enchanted swords. See [Enchantment pools](/wyne-docs/lootpool/enchantment-pools.md).
* **A command for every way loot leaves a pool.** Into a player's inventory, onto the ground, into a container, or into a preview window, plus bulk edits of weights and amounts. See [Commands and permissions](/wyne-docs/lootpool/commands-and-permissions.md).
* **AbstractMenus integration.** A `lootPool` item property and a `LOOTPOOL` catalog for generated menus. See [AbstractMenus integration](/wyne-docs/lootpool/abstractmenus-integration.md).
* **A small API.** Other plugins compile against `io.github.wyne10:lootpool-api` from Maven Central, look pools up by key, and roll them or create new ones. See [Using it from your plugin](/wyne-docs/lootpool/using-it-from-your-plugin.md), and [Extending LootPool](/wyne-docs/lootpool/extending-lootpool.md) for adding types of your own.

## Requirements

|          |                                                                                        |
| -------- | -------------------------------------------------------------------------------------- |
| Server   | Paper 1.16.5 or later. Plain Spigot won't do: the plugin uses Paper's Adventure API.   |
| Java     | 16 or later                                                                            |
| Optional | [CommandAPI](https://commandapi.jorel.dev), for the `/lootpool` command                |
| Optional | [PlaceholderAPI](https://www.spigotmc.org/resources/6245/), for placeholder conditions |
| Optional | [AbstractMenus](https://abstractmenus.github.io/docs/en/), for the menu integration    |

All three are soft dependencies, but CommandAPI is the only way to manage pools in-game. Without it LootPool still loads the pools on disk and serves them to AbstractMenus and other plugins, but there is no `/lootpool` command at all.

## How it fits together

1. LootPool enables, reads its config and language files, and publishes its `LootPoolProvider` through the API and the Bukkit services manager.
2. It loads every pool in `plugins/LootPool/lootpool/` into memory, one pool per file, keyed by file name, and every enchantment pool in `plugins/LootPool/enchantment/` the same way.
3. You create and edit pools with commands and the editors. Each change is written to that pool's file straight away.
4. Commands, menus and other plugins roll pools by key. Pools that point at other pools look them up again on every roll, so an edit to a child pool shows up in every pool built on it at once.

## Where to start

| If you want to…                                    | Read                                                                          |
| -------------------------------------------------- | ----------------------------------------------------------------------------- |
| Understand what the types are for                  | [Pool types](/wyne-docs/lootpool/pool-types.md)                               |
| Build a chest with a stated composition            | [Complex loot pools](/wyne-docs/lootpool/complex-loot-pools.md)               |
| See how people actually put these together         | [Common setups](/wyne-docs/lootpool/common-setups.md)                         |
| Look a command up                                  | [Commands and permissions](/wyne-docs/lootpool/commands-and-permissions.md)   |
| Call it from code                                  | [Using it from your plugin](/wyne-docs/lootpool/using-it-from-your-plugin.md) |
| Add a pool type, modifier or condition of your own | [Extending LootPool](/wyne-docs/lootpool/extending-lootpool.md)               |

To compile the plugin yourself, see [Building from source](/wyne-docs/lootpool/building-from-source.md).


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wyne.gitbook.io/wyne-docs/lootpool/lootpool.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.