> For the complete documentation index, see [llms.txt](https://mossuh.gitbook.io/projects/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mossuh.gitbook.io/projects/plugins/moboosters.md). # MoBoosters > A fully configurable booster plugin for Spigot/Paper servers. MoBoosters allows server owners to create custom boosters with configurable boost values, durations, identifiers, items, requirements, actions and rewards. Boosters can be temporary or permanent and can be applied individually or globally. The plugin is designed to be extensible and can support additional applicator integrations. ## Features * Unlimited custom boosters * Personal, Global and SuperiorSkyblock2 booster types * Temporary and permanent boosters * Configurable boost values and durations * Custom booster items * Requirements, actions and rewards * PlaceholderAPI support * Variables and local variables * Command arguments * Public API and Events * Extensible integrations > **Applicator Compatibility:** Additional plugin integrations can be added when requested. ### Supported Versions * Tested Versions: 1.13 to 26.1 > This plugin may be compatible with 1.12 and lower versions, It hasn't been tested, but you can give it a try --- # 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://mossuh.gitbook.io/projects/plugins/moboosters.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 `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.