Troubleshooting, Compatibility, and Live Admin Patterns

This page covers the real public-server problems people tend to hit first.

If /kits is empty

Usually this is a permission issue.

Check:

• does the player have the right mcwar.kits.use.<id> node or a custom node that matches the kit
• did the kit permission get changed in the editor
• are you only testing as op instead of with a real player account

If a player cannot open a crate

Check the full access chain, not only the crate item itself:

• the crate permission node
• whether a custom permission was set
• whether a key is required
• whether a preview or block interaction rule is being confused with the open rule
• whether the player is testing with a real non-op account

If chat-prompt editing seems broken on a forked server

The first thing to verify is whether the server fork is changing normal chat or inventory event behavior.

That is especially important on unusual Paper-style forks or heavily modded hybrids.

Before blaming the plugin, test:

• vanilla Spigot or Paper
• the same plugin build
• the same editor action
• one isolated prompt flow such as display name or permission editing

If example kits or crates keep coming back

Check config.yml:

• examples.bootstrapOnFirstRun
• examples.regenerateMissingOnStartup

If you want deleted examples to stay deleted, keep regenerateMissingOnStartup: false.

If MiniMessage formatting looks wrong on a server

Check the text-formatting mode in config.yml.

The plugin supports a fallback lane where MiniMessage can be disabled and legacy color behavior can still be used.

If crate previews seem unavailable

Check all three layers:

• global preview setting
• per-crate preview setting
• per-kit preview override when previewing kit content through the crate surface

If commands or effect rewards look wrong in preview or spin

Make sure the action entry has a meaningful display item configured.

That is the cleanest way to stop non-item rewards from looking ambiguous to players.

Best live-admin habits

Keep one non-op test account

If you only test as op, you will miss the real permission and key path problems.

Prove one kit and one crate before scaling up

Do not build thirty rewards before the first one is healthy.

Keep the file ownership clear

• messages.yml for global chat
• data/kit-menu.yml for per-kit presentation and receive-message overrides
• kits/*.yml for kit logic
• crates/*.yml for crate logic

Test forks with the editor surface, not only startup

A fork can load the plugin successfully and still behave differently during prompts or GUI interaction.

Best next pages

• commands, Permissions, and Access
• install and First Boot
• crate Editor, Preview, Keys, and Placed Blocks