Direct answer

On Java servers, allow-flight=true in server.properties prevents the vanilla flying-movement check from rejecting movement. It does not grant creative mode or permission to fly.

Recommended procedure

  1. Stop the Java server and set allow-flight=true when a supported mod or plugin legitimately enables player flight.
  2. Restart and test using a player account that can actually fly under the mod/plugin.
  3. If players still get movement kicks, inspect anti-cheat or proxy rules and logs for the specific kick message.
  4. Do not grant Creative mode merely to test a player’s flight permission.

Why this matters

Vanilla flight checks, an anti-cheat plugin and a flight-permission plugin are separate systems. Changing allow-flight cannot correct every movement or rubber-banding problem.

How to verify the result

Have an authorized player fly briefly and reconnect; inspect console for kicks or bypass messages. Also confirm a survival player without permission cannot fly.

Version and compatibility notes

This setting affects enforcement, not a creative-flying ability. Check the current server release and installed anti-cheat before weakening movement checks.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000