Crate Editor, Preview, Keys, and Placed Blocks

This page covers the crate side of Kits Crates Plus: the editor, preview flow, crate items, keys, and placed world crates.

Main crate commands

/crate open <id> [player]
/crate preview <id> [player]
/crate give <player|all> <id> [amount]
/crate givekey <player|all> <id> [amount]
/crate giveblock <player|all> <id> [amount] [persistent|consumable] [uses]
/crate block set <id> [persistent|consumable] [uses]
/crate block unset
/crate create <id>
/crate edit <id>

What the crate editor is for

The crate editor is the main authoring lane for:

• pool items
• chance values
• nested containers
• command, sound, and particle rewards
• crate settings
• preview behavior
• placed-crate settings
• key settings
• crate display name and page controls

Preview flow

Crate preview is meant to show possible rewards, not raw chance math.

Important points:

• previews can be controlled globally
• previews can be controlled per crate
• previews can also be overridden for kits when they are being treated like crate content
• preview is intended to be optional and can stay disabled where secrecy matters

Keys and physical crate items

The plugin supports more than one crate access path.

Crate item

Use:

/crate give <player|all> <id> [amount]

This gives the player a physical crate item that can be used to open that crate.

Key item

Use:

/crate givekey <player|all> <id> [amount]

This is useful when you want the crate object and the access token to be separate.

Placeable crate block

Use:

/crate giveblock <player|all> <id> [amount] [persistent|consumable] [uses]

This gives a world-placeable version of the crate.

Placed crate blocks

Placed crates matter when you want the reward system to feel like world content instead of a command-only feature.

The placed-crate path supports:

• persistent or consumable blocks
• use counters
• block protection
• admin interaction rules
• hologram text
• ambient effects
• deplete effects

You can also bind an existing world block to a crate with:

/crate block set <id> [persistent|consumable] [uses]

Permission and access behavior for crates

Do not treat a crate item, key, or placed block as the only access rule.

The actual crate permission still matters unless an admin bypass path is being used.

That means you should test:

• the permission node
• the key requirement
• the placed-block interaction rule
• preview settings

with a real non-op player account.

Good production pattern

A healthy production crate lane usually looks like this:

• one simple vote or daily crate first
• preview tested intentionally
• key requirement tested with a non-op account
• placed block mode added only after the basic open path works
• hologram and ambient effects added after the access logic is already stable

Good next pages

• commands, Permissions, and Access
• nested Containers, Effects, and Reveal Presentation
• troubleshooting, Compatibility, and Live Admin Patterns