Tags
Creators
Details
17
Compatibility
Changes
Hohoho Guys, some funky updates for the advent season!
Migrating from previous versions
Theoretically there should be no problems migrating from lower versions to ElytraFly 17, but if there are any, please Join the discord
Zone enabling/disabling
Server Admins can enable/disable specific zones via the Zone GUI
Zone restriction
Admins can now restrict usage of specific zones to Players/Permission groups!
- Every Zone has a unique Permission attached to it specifying what players are allowed to use the zone
- The permission is constructed from
elytrafly.zone.and the unique name of the zone, lowercase and with whitespaces replaced with-- Example: Zone
Test Zonehas the permissionelytrafly.zone.test-zone
- Example: Zone
Luckperms Integration
Admins can now define custom max boosts and delays via Luckperms Meta Variables
This allows admins to customize the elytra experience for different roles or users
| Variable name | Description |
|---|---|
elytrafly.max-boosts |
How many boosts a Player/Group can use per Flight |
elytrafly.boost-delay |
How long the delay between boosts is for the Player/Group |
PlaceholderAPI Integration
ElytraFly now offers first-class support for PlaceholderAPI to display additional Information to Players!
| Placeholder | Description |
|---|---|
zones_count |
The total of zones set on the server |
current_zone |
The name of the zone in which the Player is standing (null if not standing in a zone) |
allow_boosts |
If the Player is allowed to boost himself |
max_boosts |
The maximum boosts the Player is allowed to use |
delay |
The delay that is set for the Player between boosts |
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:pZ3yeFfg:sN933PCQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pZ3yeFfg:sN933PCQ"
}

