Reporting problems

Before you report

1. Reproduce it once with the plugin set your server normally runs. Removing plugins to make the symptom disappear does not tell us anything yet.
2. Note the exact build: /venus version reports the build and licensee information in one line.
3. Consider whether another plugin injects into Netty — second injections are the most common cause of odd packet behaviour.

What to attach

• The relevant log lines. The console section from startup of the affected server, not the whole log.
• The verbose line, not the alert line. If the report is about a detection, the verbose line has the numbers; the alert only has the check name.
• What you changed. A report that says "movement flags are noisy" is only actionable once we can see which groups and values you run.

Common false alarms

• One player, every check. Look for a second anticheat, a movement-rewriting plugin or a client mod before assuming a check bug.
• Only high-ping players. The transaction timeout and the ping ceilings for specific paths exist to absorb exactly this; tune them before changing checks.
• Only Bedrock or only old clients. Check the Geyser exemption and the Via handling before changing any check.
• Only on one world. World-specific behaviour usually means a compat option, not a check.

What a good report contains

• The output of /venus version.
• Your platform and Java version.
• The full plugin list.
• Reproduction steps, including the player's client and ping.
• What you expected, what happened, and the verbose line.
• The groups and values you changed in your configuration.