Skip to main content
Kits Crates Plus background
First-party pluginPlugin directory
Kits Crates Plus icon

Kits Crates Plus

The Kits & Crates + download page with package access, setup docs, and permission guidance.

Build kits and animated crates from one in-game editor instead of splitting rewards across several systems.
Layer item rewards with commands, sounds, particles, keys, block crates, and reveal styling from the same reward stack.
Keep install, compatibility, permissions, and support close to the download so rollout stays manageable on live 1.21.x servers.

Runtime

Spigot and Paper 1.21.x

Tested range

1.21 through 1.21.11

Main surfaces

Kit editor, crate editor, keys, block crates

Focus

GUI-first kits and polished crate presentation

Latest release

Kits & Crates +

The Kits & Crates + download page with package access, setup docs, and permission guidance.

  • Build kits and animated crates from one in-game editor instead of splitting rewards across several systems.
  • Layer item rewards with commands, sounds, particles, keys, block crates, and reveal styling from the same reward stack.
  • Keep install, compatibility, permissions, and support close to the download so rollout stays manageable on live 1.21.x servers.
Kits & Crates +

You can browse the full site without an account, but downloads and purchases unlock after you sign in.

Overview

Kits & Crates + is a modern in-game editor for building kits and reward crates without living in config files. The Spigot listing frames it as a 1.21-first plugin built for quick iteration, clean menus, and polished player-side reward moments.

The public pitch is straightforward: GUI-first kits, animated crates, layered percentage pools, optional reward actions like commands, sounds, and particles, plus keys, reveal styling, and placeable block crates in the same product.

  • Native major MC version: 1.21.
  • Tested major versions on the Spigot listing: 1.21 through 1.21.11.
  • Built around in-game editing instead of forcing every admin back into raw config files.
  • Meant to cover both direct kit delivery and premium-feeling crate presentation from one shared reward stack.

At a glance

  • Build kits and animated crates from one in-game editor instead of splitting rewards across several systems.
  • Layer item rewards with commands, sounds, particles, keys, block crates, and reveal styling from the same reward stack.
  • Keep install, compatibility, permissions, and support close to the download so rollout stays manageable on live 1.21.x servers.

Compatibility and setup

Runtime

Spigot and Paper 1.21.x

Tested range

1.21 through 1.21.11

Main surfaces

Kit editor, crate editor, keys, block crates

Focus

GUI-first kits and polished crate presentation

Guide

Kits Crates Plus overview section banner

What It Is

A GUI-first kit and crate system, not just another reward chest

The Spigot release sells Kits & Crates + as a modern 1.21.x reward editor where kits, crates, reveal presentation, world blocks, and reward actions all belong to one clean in-game workflow.

The main pitch is that admins should be able to create loadouts, build reward pools, and control how rewards are delivered without getting trapped in file edits every time the reward design changes.

It also deliberately goes beyond a basic chest-opening loop. The resource calls out reveal styles, reveal effects, keys, placeable world crate blocks, visible counters, and polished crate-opening flow as part of the core identity of the plugin.

That makes the download page stronger when it explains both sides of the product: the editor workflow for staff and the premium-looking payout moment for players.

Overview

  • GUI-first kits plus animated crates in one plugin.
  • Chance-based rewards with layered containers and optional reward actions.
  • Block crates, keys, reveal styles, and effects as first-class features, not side notes.
Kits Crates Plus highlights section banner

Highlights

The reward system is built around presentation as much as payout

The Spigot post leans hard on the idea that rewards should feel premium when they are opened, not just functional once they are granted.

That emphasis shows up in the animated crate openings, protected opening sessions, reveal styles, reveal effects, and the push toward clearer editor indicators so admins can tell what a reward actually contains at a glance.

It also shows up in the breadth of the reward model. Items are only one lane. Commands, sounds, particles, keys, themeable kit menus, and layered containers are all presented as part of the same polished reward surface.

The highlight lane on Spigot

  • GUI-first workflow for creating and editing kits and crates in-game.
  • Animated crate openings with protected sessions during the reveal flow.
  • Percentage-based reward entries and layered container logic.
  • Optional reward actions like commands, sounds, and particles per reward entry.
  • Block crates with counters, keys, reveal styling, and themeable kit-menu presentation.
Kits Crates Plus core features section banner

Core Features

Kits, crates, keys, and block crates all share one authoring surface

The Spigot breakdown is clean: kits, crates, block crates plus keys, and editor polish are the four lanes that make the plugin feel complete.

On the kit side, the resource calls out items, display names, icons, permission gating, inventory-style kits, and layered or container-style kits, plus a themeable /kits menu.

On the crate side, it highlights percentage-based pools, animated opening flow, optional reward actions, nested containers, and reveal styling that makes the reward moment feel worth earning.

Then it extends that into world interaction with placeable block crates, optional counters, ambient effects, opening FX, optional key requirements, and a design that fits persistent crate locations.

The editor layer ties the whole thing together with better indicators, quick iteration, selected sound and particle pickers, and in-game theme packs for consistency.

What admins should immediately understand

  • You can build both slot-specific kits and layered container kits from the same plugin.
  • Crates can mix items with commands, sounds, particles, nested pools, keys, and reveal presentation.
  • Block crates are part of the feature story, not a bolted-on afterthought.
  • The in-game editor is supposed to be clear enough for fast staff iteration and testing.
Kits Crates Plus quick start section banner

Quick Start

The clean rollout mirrors the Spigot quick-start path

The best first pass is still simple: prove one healthy kit flow and one healthy crate flow before the server starts scaling reward content.

The Spigot page gives a very direct rollout order:

  1. Drop the jar into /plugins and restart.
  2. Open the editor menu.
  3. Create a kit with items, a name, and an icon.
  4. Create a crate with rewards, chances, and optional reward actions.
  5. Optionally pick a reveal style, reveal effect, or menu theme.
  6. Optionally enable keys and block crates for a world-based opening flow.
  7. Test-open a crate and verify animation, reveal, and payout behavior.

The generated file lanes still matter for server owners who want to inspect what was created: plugins/KitsCratesPlus/config.yml, plugins/KitsCratesPlus/messages.yml, plugins/KitsCratesPlus/data/kit-menu.yml, plugins/KitsCratesPlus/kits/, and plugins/KitsCratesPlus/crates/.

Setup checks

  • The plugin boots, generates its folders, and opens its editor surfaces cleanly.
  • One kit works end to end through the intended player path.
  • One crate works with chances, animation, reveal, and payout before more content is added.
Kits Crates Plus compatibility and support section banner

Compatibility

Keep the page grounded in modern 1.21.x rollout and clear support sections

The Spigot listing is explicit about where the compatibility story and support story should land: modern 1.21.x servers, docs for setup, and a support link that expects concrete reproduction details.

The listing currently frames the plugin as native to Minecraft 1.21 and tested across 1.21 through 1.21.11. That is the version positioning the Block Arsenal download page should reflect unless the public resource changes.

It also points users toward the documentation tab for command and permission details, and toward Discord for discussion and troubleshooting. When support is needed, the listing asks for server version and build, plugin version, reproduction steps, and console errors.

That keeps the download page honest: it is not only a feature wall, it is also a handoff into the right docs and support links.

What should be obvious before someone installs

  • Native major MC version on the listing: 1.21.
  • Tested range on the listing: 1.21 through 1.21.11.
  • Commands and permissions belong in the docs flow, not buried inside marketing copy.
  • Support requests should arrive with build info, plugin version, steps, and errors.
Kits Crates Plus showcase section banner

Showcase

The gallery should prove both the payoff and the operator workflow

The Spigot resource already hints at the right media mix: layered chance editing, open-effect polish, slot-specific kits, physical animated crates, and a themeable kit GUI.

That means the Block Arsenal page should not rely on only one glamour shot. It should show the reward moment, the editor clarity, and the world-facing crate or menu workflow in the same gallery plan.

If the media only shows items spinning, buyers miss the real value. The full point is that Kits & Crates + also gives admins a manageable authoring surface for long-term server use.

Gallery

  • Layered chance editing and nested reward authoring are understandable at a glance.
  • Reveal styles, open effects, and premium-feeling payout moments are visible.
  • Physical crates, themed menus, and admin-facing editor surfaces all look maintainable.

Gallery

Preview slot

Layered chance editor capture

Show the crate or reward editor view that proves layered percentages and nested reward logic are readable in-game.

Preview slot

Animated open or reveal moment

Use a real crate-opening screenshot or GIF that sells the reveal style, effect stack, and polished payout moment.

Preview slot

Kit menu or physical crate surface

Finish with either the themeable `/kits` menu or a placed world crate so buyers see the broader server-facing presentation.

Kits Crates Plus support routing section banner

Support

Give admins the next step before they need to ask for it

The Spigot page closes with a direct support rhythm: docs first, discussion when useful, and actionable bug reports when something actually breaks.

That is the same posture the Block Arsenal download page should take. Someone reading the page should know where to install from, where to learn the command and permission surface, where to troubleshoot version or fork issues, and where to ask questions with enough detail to get a real answer.

This is also the right place to route people toward the wiki pages for permissions, first boot, editor behavior, preview flow, first-join grants, and live-server troubleshooting instead of forcing the download page to carry every single setup detail itself.

The clean handoff

  • Use the wiki for setup, permissions, files, and editor walkthroughs.
  • Use support or discussion for public questions and version-specific troubleshooting.
  • Keep the live download, release history, and docs close together on the same page.

Releases

Release notes

0.3.4

MAJOR

3/21/2026

Downloads

Related download pages and add-ons

Kits & Crates + preview
FREENEW
Kits & Crates + icon

Kits & Crates +

Duq_

Highly Customizable Kits & Animated Crates

5.0(1)
1
Utilities