Prepare a support report
Provide a reproducible issue while protecting server, customer, and player data.
Useful information
- Minecraft, Java, and Nusa release versions.
- OS/panel, CPU/memory allocation, container limit, and heap without private identity.
- Short reproduction steps, expected result, and actual result.
- Time and frequency of the issue.
- Relevant plugins/versions, dependencies, and staging isolation results.
- A small, reviewed, redacted configuration excerpt.
- Relevant redacted log lines including the original cause.
For performance, include the workload and a profile captured during the issue. Do not publish internal benchmark/test archives as general support material.
Redact before sharing
Remove license keys, bridge/Bearer tokens, webhook URLs, database credentials, private endpoint addresses, emails, network addresses, installation identity, and unnecessary player/account data. Do not upload whole license/bridge files, unreviewed configs, or raw log directories.
Use a clear placeholder such as <REDACTED_TOKEN>, preserving key names and value types where useful. Rotate an exposed secret through its service; deleting a message does not restore secrecy.
Report template
Server / Java version:
Environment and heap:
Issue and time:
Reproduction steps:
Expected result:
Actual result:
Relevant plugins / settings (redacted):
Staging test result:
Relevant error excerpt (redacted):Where to send it
Use the support channel supplied with your purchase. These public docs do not invent a support address, response deadline, or service policy. For a plugin-specific reproduction, contact its maintainer through the official channel with the same focused context.