Skip to content

Installation

  1. Make sure the server runs Paper 1.21.x on Java 21, with LuckPerms and PlaceholderAPI installed: without them the plugin disables itself on startup.

  2. Stop the server and copy CobaltiaEffets.jar into the plugins/ folder.

  3. Add the optional plugins you want to use (see the table below). None is mandatory: each feature that depends on one simply stays inactive.

  4. Start the server. The plugins/CobaltiaEffets/ folder is created with:

    • config.yml — ranks, effects, wardrobe, companions, banner, chat, RTP, AFK zone, tab, messages;
    • boutique.yml — shop categories and items (only created if it does not exist).
  5. Check the console: the plugin reports every configuration error (missing section, invalid color, unknown mob…) and missing integrations.

  6. Give the base permissions to your ranks (see Permissions), then try /effets, /garderobe and /boutique in game.

Installed plugin What gets enabled
(no optional plugin) Name effects, /effets menu, placeholders, mentions and @item, /money, /furnace, /nightvision, /rtp, banner, MOTD, join/quit messages, tab by world, tab sorting
PacketEvents Companion rendering around the player
HMCCosmetics Hats and backpacks wardrobe tabs, /hat and /sac
Nexo Nexo icons in menus, /give for Nexo items, job rewards on custom ores (with Jobs)
Jobs Reborn Job XP in the banner, level rank in chat, AFK fishing, player hunting
WorldGuard Paid AFK zone
BetterHud HUD shown/hidden preference applied on join
“Cobaltia” plugin Shop, titles in the wardrobe, leaderboards, boosters, clan in chat, AFK zone payouts

* /money reads balances through the “Cobaltia” plugin placeholders; /rtp teleports through CMI’s rt command. See Integrations.

[CobaltiaEffets] Enabling CobaltiaEffets v1.0.0
[CobaltiaEffets] PacketEvents absent : les compagnons ne seront pas affiches
[CobaltiaEffets] Boutique désactivée : plugin Cobaltia absent

Warning lines are not errors: they tell you an optional integration is missing.

  1. Stop the server and replace the .jar.
  2. Keep your config.yml and boutique.yml: messages missing from your config.yml are read from the default configuration inside the .jar, so you do not need to copy new message keys.
  3. Restart and check the console.