Commands, Permissions, and Access

This page is the most important public page for real server setup because Kits Crates Plus is permission-driven.

If permissions are wrong, the plugin will often look broken even when the install is healthy.

Core commands

Kit commands

/kits
/kit menu
/kit <id>
/kit <id> <player|all>
/kit create <id> [inventory|CONTAINER]
/kit edit <id>
/kit delete <id>
/kit reload

Crate commands

/crate open <id> [player]
/crate preview <id> [player]
/crate previewtoggle <id> <true|false>
/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>
/crate delete <id>
/crate reload

Plugin settings command

/kcp

/kcp opens the global Kits Crates Plus settings menu for admins.

Main admin permission nodes

The plugin registers these top-level admin nodes:

• mcwar.kits.admin
• mcwar.crates.admin

What they are for:

• mcwar.kits.admin controls kit create, edit, delete, reload, admin give, and bypass behavior
• mcwar.crates.admin controls crate create, edit, delete, reload, preview toggles, give flows, placed-crate admin interaction, and related bypass behavior

/kcp accepts either admin node.

Player kit permissions

Default kit permission pattern

If a kit does not use a custom permission, the normal pattern is:

mcwar.kits.use.<id>

Example:

mcwar.kits.use.starter
mcwar.kits.use.vip
mcwar.kits.use.daily

Wildcard:

mcwar.kits.use.*

Important /kits behavior

/kits is not the permission gate by itself.

The menu can open for any player, but it only shows kits that player can actually use. That means an empty /kits menu usually points to permissions, not a broken menu.

Player crate permissions

Default crate permission pattern

If a crate does not use a custom permission, the normal pattern is:

mcwar.crates.use.<id>

Example:

mcwar.crates.use.vote
mcwar.crates.use.tier1_example
mcwar.crates.use.legendary

Wildcard:

mcwar.crates.use.*

Real crate access rule

Crates can also use a custom permission string if you set one in the crate file or through the editor.

That means you can use either:

• the default mcwar.crates.use.<id> style
• your own rank/plugin permission node

The cleanest permission strategy

Kits

Use one pattern for normal player claims:

mcwar.kits.use.starter
mcwar.kits.use.daily
mcwar.kits.use.vip

Crates

Use one pattern for real crate access:

mcwar.crates.use.vote
mcwar.crates.use.monthly
mcwar.crates.use.legendary

Admins

Add:

mcwar.kits.admin
mcwar.crates.admin

That keeps the operator surface clear without giving every staff member wildcard player access to all reward content.

Recommended role split

Normal players

• specific mcwar.kits.use.<id> nodes
• specific mcwar.crates.use.<id> nodes

Moderators or helpers

Usually none, unless they need to test crate blocks or reward access.

Content staff

• mcwar.kits.admin
• optionally mcwar.crates.admin if they also build or test crates

Full admins

• mcwar.kits.admin
• mcwar.crates.admin

Common permission mistakes

/kits opens but shows nothing

The player does not have any kit-use node that matches the configured kits.

/kit <id> says no permission even though the kit exists

The kit permission is set to a custom node and the player only has the default mcwar.kits.use.<id> pattern.

A crate item was given but the player still cannot open it

The crate access permission is still enforced when opening unless an admin bypass path is being used.

Staff can edit kits but not crates

They only have mcwar.kits.admin, not mcwar.crates.admin.

/kcp says no permission

The player needs at least one of:

• mcwar.kits.admin
• mcwar.crates.admin

Good next pages

• install and First Boot
• kit Editor, Kit Menu, First Join, and Receive Messages
• crate Editor, Preview, Keys, and Placed Blocks
• troubleshooting, Compatibility, and Live Admin Patterns