Skip to main content

Troubleshooting

Choose the symptom that matches your setup. Always start with the first related error in the console: later “command not found” messages often just mean the plugin did not finish starting.
Keep these details handy: Reverse build, Java/server version, installed roles, storage backend, and replay/session ID. They make a problem much easier to reproduce. Redact credentials and license-bearing data before sharing logs.

What are you seeing?

Click the symptom that matches.

Is the feature available?

Check the command guide and your release notes for the available features. There is no video-export, automatic storage-migration, or retention-scheduling command. Arena bounds and participant selection are available to game plugins through the Java API. Clips use /reverserecorder clip, with either a duration or --from/--to. No recording mode or rolling-buffer configuration is needed. For startup errors naming an unknown storage.backend or adapter, use the exact built-in ids in configuration; installing an extra plugin does not register a factory for those selectors.

Still stuck?

Use the support checklist to collect a reproducible case. Include the exact command, expected result, observed result, and first relevant stack trace.