Kits, Crates, and the Shared Reward Engine

Kits Crates Plus is much easier to reason about if you stop thinking of kits and crates as two unrelated systems.

They are two presentation lanes over one reward engine.

What a kit is best for

Use a kit when the reward should feel direct and intentional.

Good fit:

• starter kits
• rank kits
• daily or timed kits
• one-time onboarding kits
• admin give flows
• menu-based player claims through /kits

What a crate is best for

Use a crate when the reward should feel like an event or a reveal moment.

Good fit:

• vote crates
• key-based crates
• placed world crates
• themed reward pools
• multi-reward reveal moments
• previewable reward collections

What they share

Both systems can use:

• items
• nested containers
• command rewards
• sound rewards
• particle rewards
• weighted chance logic
• shared reward design patterns

That is the main reason the plugin scales better than running one kit plugin and one crate plugin that do not understand each other.

Kit as crate presentation

The plugin can also present a kit through the crate-opening surface.

That matters when you want:

• one reward definition
• two different presentation lanes
• kit content that can still be opened with crate-style animation

Inventory kits versus container kits

Inventory kit

Use this when slot layout matters.

Good fit:

• fixed armor and hotbar loadouts
• exact starter kits
• clean PvP or RPG loadout grants

Container kit

Use this when chance and reward pooling matter more than slot position.

Good fit:

• rotating bonus kits
• random support bundles
• reward pools that feel closer to crates

A good production pattern

Use kits for the guaranteed progression lane and crates for the event lane.

Example:

• first join gives a starter kit
• /kits handles timed claimable rank kits
• crates handle vote rewards, donor crates, or event rewards
• nested containers handle the deeper weighted logic inside both sides

Good next pages

• kit Editor, Kit Menu, First Join, and Receive Messages
• crate Editor, Preview, Keys, and Placed Blocks
• nested Containers, Effects, and Reveal Presentation