Tags
Creators
Details
1.2.5
Compatibility
Required content
Changes
GPExpansion v1.2.5
This release draws every claim on Dynmap and BlueMap, lets /claim color take any hex colour, and
adds a permission for claim flight that never runs out inside claims. Flight granted by other
plugins is now left alone across relogs.
The Maven project version is now 1.2.5. New configuration entries and permissions are added to
existing installs automatically.
Claims on Dynmap and BlueMap
When Dynmap or BlueMap is installed, GPExpansion adds a GriefPrevention layer that outlines
every claim. Shaped GriefPrevention3D claims are drawn with their real outline. Clicking a claim
shows its owner and, with show-trust-list, its managers, builders, containers and accessors.
- Both integrations are on by default and do nothing until their map plugin is present. Turn either
off with
integrations.dynmap.enabledorintegrations.bluemap.enabled. - GPExpansion hooks in even when the map plugin starts after it, and
/gpx reloadapplies changes to these settings straight away. - Markers refresh every
update-interval-seconds(300 by default, never less than 15). - On BlueMap, 2D claims are drawn flat at
render-height(63, just above sea level) whenflat-view-onlyis on, so outlines sit on the ground. They show through terrain unlessdepth-testis set totrue. Shaped claims always keep their real height.
Colours
Each claim uses its own /claim color, or else integrations.colors.main-claim (#FFD700) or
integrations.colors.admin-claim (#FF8C00). With fill-opacity at 0, the fill is a
translucent shade of the outline colour.
Hex Claim Colours
/claim color now accepts a hex value (#RGB, #RRGGBB or #RRGGBBAA) as well as the 16 named
colours. The colour you set is used for both the locator bar waypoint and the map marker.
claimdata.yml stores it as a colour name or #rrggbb.
Unlimited Claim Flight
griefprevention.claimfly.unlimited (default op) lets a player use claim flight without any
banked flight time. While they fly inside a claim they can fly in, no time is spent. Flight
outside claims, with claim-flight.disable-on-leaving-claim turned off, still costs time.
/claimflytells holders that flight is unlimited inside claims, instead of showing a balance./claimfly check <player>reportsunlimitedfor holders, so a balance of 0 is not read as being unable to fly.%gpx_claim_flight%reportsyesfor online holders. Offline players are still judged on their banked time.
Flight From Other Plugins
Flight that another plugin granted, such as Essentials /fly or a gamemode permission, is now
remembered across relogs. GPExpansion no longer revokes it when the player leaves a claim, and no
longer spends their claim flight time on it. If that flight is taken away while the player is
inside a claim, GPExpansion stops treating it as external.
Configuration and Language
New config.yml entries under integrations, added to existing configs automatically:
integrations:
colors:
main-claim: "#FFD700"
admin-claim: "#FF8C00"
dynmap:
enabled: true
layer-name: GriefPrevention
update-interval-seconds: 300
show-trust-list: true
colors:
stroke-weight: 3
stroke-opacity: 1.0
fill-opacity: 0.0
bluemap:
enabled: true
marker-set-id: gpexpansion.claims
layer-name: GriefPrevention
update-interval-seconds: 300
flat-view-only: true
render-height: 63
depth-test: false
show-trust-list: true
colors:
line-width: 2
fill-opacity: 0.0
- New permission:
griefprevention.claimfly.unlimited(defaultop). claim.color-usageandclaim.color-invalidmention hex values. Alang.ymlthat already has these keys keeps its current text.- Dynmap and BlueMap are optional dependencies in
paper-plugin.yml.
Compatibility
Built against GriefPrevention3D 18.2.7 and Paper 26.2, with BlueMap API 2.8.0 and Dynmap API
3.8. No storage migration is required.
Verification
mvn clean packagecompleted successfully and producedtarget/GPExpansion.jarfor version1.2.5.- GriefPrevention3D's addon compatibility check compiles this release against GriefPrevention3D
19.0.1. - The existing 10 unit tests pass. None of them cover the changes in this release.
- Still to check on a live server: markers on Dynmap and on BlueMap (including shaped claims and
the trust list), hex
/claim colorvalues on the map and the locator bar, flight withgriefprevention.claimfly.unlimitedinside and outside claims, and Essentials/flyacross a relog.
Optional dependencies
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:7IRb19K2:PoONseHT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7IRb19K2:PoONseHT"
}

