Tags
Creators
Details
5.13
Compatibility
Changes
GPF 5.13 had two important changes that server owners might want to take action about:
-
With the addition of PermissionFly, I reworked a lot of how flying and when players are checked for their ability to fly. GPF has always expected that players who can use the /fly command through another plugin would also have gpflags.bypass.fly to prevent GPF from trying to turn off the player's flight when they left a claim where flight was enabled. With 5.13, this permission needed to be checked more often, and without giving it to the appropriate players, can result in them not being able to fly in places where they could previously.
-
GPF now uses minimessage. Config should have already been updated but flags.yml did not. If you had flags that use legacy formatting colors, you can use copy your flags.yml here to convert them to minimessage.
Full changelog below:
- Added compatibility for 1.20.6 and 1.21.
- Added the PermissionFly flag which can allow flight depending on the player's server permissions rather than the player's claim permissions.
- Added the ability to use PAPI Placeholders in GPFlags messages
- Added the ability to use AllowPvP flag as a world or server level flag
- Added bypass perms for PlayerGamemode flag
- Fixed actionbar flags not working on servers without Paper’s api (eg. Spigot)
- Fixed an issue where flags that deny mob spawning would also deny slime splitting
- Fixed an issue where NoCoralDeath wouldn't work on some types of coral
- Fixed SpleefArena not working below y=0
- Fixed an issue where ChangeBiome wouldn't apply below y=0 and above y=256
- Fixed a rare issue where the plugin could make the server stall on startup.
- Fixed AllowPvp flag allowing pvp on non-dog pets
- Changed the list of available flags to be sorted alphabetically
- Changed GPFlags to use MiniMessage chat formatting
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:Z0NVSlL6:eeSSsgiB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Z0NVSlL6:eeSSsgiB"
}
