Getting started

Welcome to the documentation of Popow’s Minecraft plugins. Every plugin documented here is a Paper plugin for Minecraft 1.21.x, compiled for Java 21, designed to work on its own as well as together with the others.

The collection

CobaltStaffModeration: sanctions, reports, staff mode, investigations and staff chat, in a single plugin.

CobaltiaEffetsCosmetics: animated name effects, wardrobe, companions, shop and a banner above the hotbar.

CobaltiaAnnoncesCommunication: JSON announcements, automatic rotations, per-world or per-region targeting, management menu.

How to read this documentation

Each plugin has its own group in the sidebar, always organised the same way:

Page	Content
Overview	What the plugin does and its main features.
Installation	Requirements, dependencies and first start.
Commands	Full list of commands, with syntax and permission.
Permissions	Every permission node and its default value.
Configuration	Configuration files, key by key.
Placeholders	PlaceholderAPI placeholders provided by the plugin.
Messages & languages	Customising the texts shown to players.
API & events	Integration points for developers.
FAQ	Answers to the most common questions.

A page that does not apply to a plugin is simply absent from its group. Reference tables (commands, permissions, placeholders, configuration) include a search box and a module filter.

Conventions:

• <argument>: required argument; [argument]: optional argument.
• A permission’s op / true / false value is its default value in Paper.

Typical installation

1. Check the requirements: a Paper 1.21.x server running Java 21, plus the plugin’s required dependencies (see Compatibility).
2. Stop the server.
3. Copy the plugin’s .jar file into the server’s plugins/ folder.
4. Start the server: default configuration files are created in plugins/<PluginName>/.
5. Adjust the configuration, then apply it with the plugin’s reload command or restart the server.
6. Grant the permissions to your groups (for example with LuckPerms).

Tip

Install optional dependencies before the plugin’s first start: the matching integrations are detected when it loads.

For the version history, see the Changelog.