Reproduce the problem before changing settings
Send the expected outcome, the actual result and the steps that produce it. A startup failure, a command error and a feature that fails only for one rank require different checks. Include the first relevant error and the surrounding context, with secrets removed.
Version and dependency information matters. Tell us what changed before the issue appeared: a server update, plugin addition, configuration edit or permissions change. Keep an unchanged backup so testing has a reliable reference.
Configuration tuning needs evidence
If the issue is lag, distinguish a slow server from a player connection or client rendering issue. Explain when it occurs, which actions trigger it and whether it affects everyone. Existing profiler output can help define a useful investigation.
The service can assess settings and plugin interactions within an agreed brief. It cannot promise a specific TPS, player count or hardware improvement without measurements and control over the relevant factors. Hardware limits and third-party plugin defects may need a host or plugin developer.
A fix has a verification step
Agree which files may change and what must stay working. Re-test the original reproduction after the change, then check adjacent behavior such as default permissions or menus affected by the same configuration.
Troubleshooting is scoped work, not an unrestricted support subscription. If a new issue or a larger redesign is found, the team explains the next step and agrees any extra charge before expanding the work.
What to include in your brief
- Expected result, actual result and reproduction steps
- Server/plugin versions and recent changes
- Redacted error excerpt or relevant diagnostic evidence
- Backup and test arrangements, plus affected player roles
Questions about this service
Can you guarantee 20 TPS?
No. Results depend on workload, hardware, plugins and the root cause. We agree a measurable investigation and scope without promising a universal performance result.
Should I paste my entire configuration publicly?
No. Remove credentials, tokens and personal information. Use the project channel to agree which limited diagnostic files are needed.
What if the plugin itself has a bug?
The findings may point to the plugin developer or hosting provider. A configuration service cannot guarantee a fix to third-party code.