Wiki
Kits Crates Plus Wiki
Public setup, commands, permissions, kit/crate authoring, previews, placed blocks, and troubleshooting for Kits Crates Plus.
Getting Started
Start here for install, generated files, commands, and the permission rules that decide whether the plugin actually works for players.
Reward Design
Use the shared reward engine intentionally instead of treating kits and crates like disconnected systems.
Runtime and Support
Check the real reasons a reward system looks broken on live servers before you blame the whole plugin.
Kits Crates Plus is Duq_'s shared reward stack for claimable kits, animated crates, nested containers, command rewards, physical crate blocks, per-kit menu presentation, and in-game editing.
This wiki is the public setup and operator guide for Kits Crates Plus. It focuses on the parts server owners and admin teams actually need:
- installing the plugin cleanly
- understanding the generated files and what each one owns
- setting commands, permissions, and access rules correctly
- building kits, crates, nested rewards, and effect-based rewards without guesswork
- using first-join kits, previews, keys, placed crates, and receive-message controls safely
- fixing common live-server issues quickly
Start here
If you are brand new to Kits Crates Plus, use this path:
1. Install and first boot
Start with install and First Boot so the example files generate cleanly and you know which folders matter.
2. Learn the file split before editing rewards
Read files, Config, Messages, and Generated Data before you start changing kits, crates, or menu presentation.
3. Set commands and permissions early
Use commands, Permissions, and Access before you hand the plugin to staff or hook it into ranks.
4. Understand the shared reward model
Read kits, Crates, and the Shared Reward Engine before you decide whether something belongs in a kit, a crate, or a nested pool.
5. Build the kit side first
Use kit Editor, Kit Menu, First Join, and Receive Messages when you want starter kits, timed kits, one-time kits, or custom receive messaging.
6. Build the crate side after one kit works
Use crate Editor, Preview, Keys, and Placed Blocks once you are ready for previews, keys, placed crates, and admin give flows.
7. Add deeper reward behavior last
Move into nested Containers, Effects, and Reveal Presentation after the basic claim and open loops already feel correct.
Documentation map
Getting Started
Reward Design
- kits, Crates, and the Shared Reward Engine
- kit Editor, Kit Menu, First Join, and Receive Messages
- crate Editor, Preview, Keys, and Placed Blocks
- nested Containers, Effects, and Reveal Presentation
Runtime and Support
What this wiki covers
Most servers will spend most of their time in these areas:
config.ymlfor runtime, first-join behavior, previews, reveals, and formatting modemessages.ymlfor the default chat output and prefix behaviordata/kit-menu.ymlfor per-kit menu presentation, receive-message overrides, and crate-style presentation overrides for kitstheme-packs.ymlfor/kitsmenu themingkits/*.ymlfor actual kit definitionscrates/*.ymlfor actual crate definitions/kit,/kits,/crate, and/kcpfor the day-to-day operator surface
Recommended order
If you are setting up a live server
- install and First Boot
- files, Config, Messages, and Generated Data
- commands, Permissions, and Access
- troubleshooting, Compatibility, and Live Admin Patterns
If you are building progression rewards
- kits, Crates, and the Shared Reward Engine
- kit Editor, Kit Menu, First Join, and Receive Messages
- crate Editor, Preview, Keys, and Placed Blocks
- nested Containers, Effects, and Reveal Presentation
If you mainly need staff access and permissions to behave correctly
- commands, Permissions, and Access
- crate Editor, Preview, Keys, and Placed Blocks
- troubleshooting, Compatibility, and Live Admin Patterns
Quick help
If /kits is empty, a player cannot open a crate, or the editor is saving data but staff still cannot use it, jump straight to commands, Permissions, and Access and troubleshooting, Compatibility, and Live Admin Patterns.