A flight plugin that deducts fees based on the server's economy system, relying on Vault to interfac
FlyPlugin
Simple Pay-As-You-Fly Economy Flight for Paper 26.2 Language notice: The SpigotMC resource page, documentation and support channel are English-only. Chinese-language support is not provided on SpigotMC. The plugin's in-game messages and default configuration comments are currently written in Chinese.
About FlyPlugin
FlyPlugin is a lightweight economy-based flight plugin for Paper 26.2. A player pays the configured amount when flight starts and is charged again every 60 seconds while the paid flight session remains active. Vault connects FlyPlugin to the server's economy provider. The plugin is intentionally focused on a small workflow: start paid flight, continue periodic billing, stop flight manually, or stop it automatically when the balance is insufficient or the player disconnects.
Compatibility
- Server software: Paper 26.2 only
- Java: 25 or newer
- Required dependency: Vault
- Required service: A Vault-compatible economy plugin
- Plugin version: 1.1.2
- Build API: Paper API 26.2.build.56-alpha
- Spigot and Paper versions other than 26.2 have not been tested for this release and are not claimed as supported
Free Resource
FlyPlugin should be published as a free resource with a price of 0.00. It is a small, single-purpose, open-source plugin released under the MIT License, with no paid service, premium integration or gated feature set. Its current permission and configuration limits also make a free listing more appropriate than a paid resource.
Main Features
- Start paid flight with one player command
- Immediate first charge when a flight session starts
- Automatic repeated charge every 60 seconds
- Automatic flight shutdown when the player cannot afford the next charge
- Manual flight shutdown
- Disconnect cleanup and flight-state reset on the next join
- Configurable price and console transaction logging
- Configuration reload command
- No database or external storage service
Economy Transaction Flow
When a player runs /flystart, FlyPlugin checks whether the Vault economy reports a sufficient balance, requests the first withdrawal, enables flight and starts a repeating billing task. Every 60 seconds, it checks the balance again and requests another withdrawal. If the balance is insufficient, paid flight is disabled. Charges are prepaid for each period. Stopping early does not produce a partial refund. FlyPlugin relies on the configured Vault economy provider and does not bundle an economy implementation.
Flight State and Data
Active billing tasks and pending join resets are stored in memory only. FlyPlugin does not create a player-data database or save balances itself. Economy balances remain the responsibility of the Vault economy provider. When a player disconnects during paid flight, the billing task is cancelled and the plugin resets flight permission when that player next joins.
Security and Permissions
Version 1.1.2 does not declare or check permission nodes. This means /flystart, /flystop and /flyreload are not protected by built-in permissions. Server owners should restrict commands externally if necessary, especially /flyreload. This limitation is disclosed here and in the full documentation.
Dependencies
- Vault is required and is not bundled
- A separate Vault-compatible economy plugin is required and is not bundled
- Paper API and Vault API are compile-time provided dependencies and are not shaded into the release jar
Links
Important Notes
- The actual billing interval in version 1.1.2 is fixed at 60 seconds. The charge-interval configuration value is currently not applied.
- The auto-save-interval configuration value is currently unused because FlyPlugin stores no plugin-owned persistent player data.
- Existing active sessions keep the price captured when flight started, even after a configuration reload. Restart the session to use the new price.
- Stopping paid flight sets the player's flight permission to false. Test interaction with creative mode or other flight-management plugins before production use.
- Version 1.1.2 has no automated test suite. The release is compile-verified; no new live-server test was performed for this documentation update.