All versions
1.0.1
Release
Skyport 1.0.12 months ago 38
Compatibility
Minecraft: Java Edition
26.2
Platform
Paper
Required content
Any compatible version
Changes
Changelog
All notable changes to SkyPort are documented here.
[1.0.1] - 2026-08-27
Added
- Added Paper 26.2 support.
- Added Java 25 compilation target.
- Added airport administration GUI.
- Added airport creation, deletion, renaming, and status overview.
- Added terminal, arrival, aircraft seat, and gate location management from the GUI.
- Added gate creation and deletion from the GUI.
- Added route creation and deletion from the GUI.
- Added route and airport pagination in the admin panels.
- Added confirmation screens for destructive GUI actions.
- Added
/airport admin delairport <id>. - Added
/airport admin delgate <airport_id> <gate_id>. - Added
/airport cancelfor cancelling scheduled flights. - Added boarding pass right-click cancellation and refunds.
- Added optional PlaceholderAPI support:
%skyport_flight_status%%skyport_flight_route%%skyport_flight_id%
- Added Turkish and English localization for GUI, boarding passes, and player messages.
- Added configurable boarding, countdown, travel, and arrival durations.
Changed
- Airport names are stored as plain text instead of serialized Adventure components.
/airportopens the nearest airport terminal in the player's world when available./airport <airport_id>opens a specific airport menu.- Tab completion now includes registered airport IDs and admin actions.
- Admin route creation validates airports, gates, duplicate endpoints, and prices.
- Flight status placeholders display airport names instead of only IDs.
- Airport and route data are saved when the server shuts down.
- Reloading clears old in-memory airport and route data before loading fresh data.
Fixed
- Fixed missing
FlightSessionsource discovery. - Fixed scheduler task type handling in flight sequences.
- Fixed missing
AirportManagerandStorageManagerintegrations. - Fixed missing storage resource files on first startup.
- Fixed stale
TextComponentImplairport names in menus and YAML data. - Fixed duplicate plugin JAR ambiguity by publishing version
1.0.1. - Fixed unused imports and related Problems panel diagnostics.
Dependencies
- Vault: required
- PlaceholderAPI: optional
Optional dependencies
Any compatible version
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:kDYjrNWc:bTdiQAxX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kDYjrNWc:bTdiQAxX"
}

