Real in-game output from FlyCommand 1.0.0 on a local throwaway Paper 1.21.11 test server: the commands were typed by a scripted bot client, and the chat it received is drawn as Minecraft-style chat (typed commands appear in the input bars; grey lines say what happened between commands).
FlyCommand is a Spigot plugin that lets permitted players toggle flight mode on and off with a single command. It adds one command, /fly, and nothing else — there is no configuration file and no persistent data.
This plugin is supported on the Minecraft versions listed in minecraft-versions.json: currently 1.19.4, 1.21.11, 26.2 and 26.3 (Spigot and its forks). Every stable release is booted on a real server of each of these versions before it is published, and every build checks that the plugin only uses Bukkit API that exists on all of them. Other versions from 1.19.4 onwards are expected to work but are not tested. To support another version, add it to the file: both checks pick it up.
- Download the latest FlyCommand jar from the releases page.
- Place the jar in the
pluginsfolder of your server. - Restart your server.
The plugin targets Spigot / Paper with api-version 1.13.
Type /fly to toggle your flight on or off. The plugin confirms the new state in chat.
- User Guide – Installation, usage and permissions
- Commands Reference – Every command the plugin handles
- Configuration Guide – Configuration options
- Changelog – Notable changes by release
You can find the Dans Plugins Community Discord server here.
Please open a bug report here.
mvn clean package compiles the plugin and runs its test suite. The suite checks the plugin.yml packed into the jar: that main names the plugin class, that the build filled in the version, and that the Fly command and the FlyCommand.fly permission are declared. It also runs the /fly handler against stand-in senders, checking the toggle and its confirmations (including when the command is typed as /flycommand:fly), the permission-denied alert, and the console alert. The Build workflow runs the same command on every push and pull request.
The tests do not start a server, so the plugin loading and /fly being registered are still verified by hand on a Spigot or Paper server, as described under Manual Validation.
The plugin is a single class, built with Maven.
src/main/java/me/Daniel/FlyCommand/Main.java– the whole pluginsrc/main/resources/plugin.yml– the plugin manifest, whosemainvalue must stay equal to the package and class name of that file; itsversionis filled in frompom.xmlat build timesrc/test/java/– tests of the packaged manifest and of the/flyhandler
mvn clean packageThe jar is written to target/FlyCommand-<version>.jar. It is compiled for Java 8 (maven.compiler.release in pom.xml) so that it loads on the oldest servers its api-version: 1.13 admits.
Every push to main that changes more than documentation republishes the rolling dev prerelease (Dev Release). Stable releases are published from a verified dev build; a release published without a jar has one built and attached by Release.
- Build the jar as above.
- Copy it into a Spigot or Paper server's
pluginsfolder and start the server. - Confirm the plugin loads and
/flyis registered. - Join as an operator and run
/flytwice, confirming that flight toggles each time and that the chat confirmation readsFlight enabled.when flight is turned on andFlight disabled.when it is turned off. - Run
/flycommand:fly, confirming that it toggles flight exactly as/flydoes. - Join with an account that is neither an operator nor a holder of
FlyCommand.flyand run/fly, confirming thatAlert: Permission 'FlyCommand.fly' required.is shown and flight is unchanged. - Run
/flyfrom the server console, confirming thatAlert: Can't be used by console.is shown and that no error is logged.
| Name | Main Contributions |
|---|---|
| Daniel Stephenson | Creator and primary developer |
This project is licensed under the GNU General Public License v3.0 (GPL-3.0).
You are free to use, modify, and distribute this software, provided that:
- Source code is made available under the same license when distributed.
- Changes are documented and attributed.
- No additional restrictions are applied.
See the LICENSE file for the full text of the GPL-3.0 license.
The latest stable release is 1.0.0; the version under development is set in pom.xml, and changes are recorded in CHANGELOG.md. Open work is tracked on the issues page.