Short pitch: Easily manage and restrict Elytra on your server. Disable flight in specific worlds (or everywhere except a whitelist), give temporary bypasses to players, and control behavior via simple commands and a clear config.

Key features

• Disable Elytra per world (two modes: disable only in listed worlds, or disable everywhere except listed worlds).
• Admin commands for adding/removing worlds, listing worlds, forcing flight stop, reloading config, toggling the plugin, and checking status.
• Temporary bypass support (ued.bypass) to allow individual players to fly.
• Actionbar or chat notifications with per-world custom messages and {world} placeholder.
• Prevent players from re-enabling flight in restricted worlds.
• Message anti-spam (cooldown) and optional logging of flight attempts in server logs.

Commands

ultimateelytradisable (alias: ued). Permission: ued.admin.

/ued addworld <world>        - Add a world to the target list
/ued removeworld <world>     - Remove a world from the target list
/ued listworlds              - Show configured target worlds
/ued purge                   - Force-stop flight for all players
/ued reload                  - Reload plugin config
/ued enable|disable          - Enable or disable the plugin
/ued status                  - Show plugin status
/ued bypass <player> [on|off]- Grant or revoke temporary flight bypass for a player
/ued help                    - Show command list

Important config options

• enabled — master on/off switch.
• disable-in-listed — true = disable in listed worlds only; false = disable in all worlds except the listed ones.
• target-worlds — list of world folder names (e.g. world_the_end).
• bypass-permission — permission node for permanent bypass (default: ued.bypass).
• admin-permission — permission node to run admin commands (default: ued.admin).
• use-actionbar — if true, messages appear in the actionbar; otherwise they go to chat.
• prevent-reenable — prevent players from re-enabling flight inside restricted worlds.
• message-cooldown-ms — minimum interval (ms) between messages to avoid spam.
• log-attempts — whether to log flight attempts to the server console.
• actionbar-message / per-world-messages — customizable messages; use {world} in messages.

Default example:

enabled: true
disable-in-listed: true
target-worlds:
  - world_the_end
bypass-permission: "ued.bypass"
admin-permission: "ued.admin"
use-actionbar: true
prevent-reenable: true
message-cooldown-ms: 2500
log-attempts: true
actionbar-message: "&c✈ Flight is disabled in world {world}!"
per-world-messages:
  world_the_end: "&4✈ Flight is disabled in The End!"
  world_nether: "&4✈ Flight is disabled in The Nether!"
  default: "&c✈ Flight is disabled in this world!"

Quick start

1. Drop the JAR into plugins/.
2. Start the server to generate the config.
3. Edit target-worlds, disable-in-listed, and messages to suit your server.
4. Use /ued reload after changes or restart the server.
5. Grant ued.admin to staff and ued.bypass to any player who should always be able to fly.

Tips

• For typical use, set disable-in-listed: true and list only the worlds where flight should be blocked (e.g. world_the_end).
• Enable log-attempts while testing to monitor player behavior and permission issues.
• Use per-world messages to clearly inform players why flight is disabled in a given world.