UploadedJan 22, 2015
Supported Bukkit Versions
Recent Major Changes
- PvP worlds reset - Version 10.4 and higher. This area of the config file has been frustrating for many for a long time. I've rewritten it to be more readable, much easier to edit, and now you can have an empty PvP worlds list on a PvP server, if that's what you want. When you update to this version, you will have to customize this part of the config file again (if you ever customized it at all).
- Finding offline players by name - Version 9.0 and higher. For sake of performance (not producing lag), players and admins can only target offline players who've recently logged in with Grief Prevention slash commands like /trust, /transferclaim, /claimslist, and so on. I plan to keep working on this to make all players targettable without causing a lag problem. This limit on who can be targetted is a temporary solution to work around a problem introduced by the CraftBukkit team when they made the switch to support player UUIDs.
- UUID Conversion - Version 8.1 and higher. During boot, an often very slow, one-time conversion process will replace player names in your data with player UUIDs. This process can take as long as one second for each player who has EVER played on your server. Make a backup before you upgrade, and please be patient. If this process is interrupted, you'll have to restore from backup and start over. This change will ensure players who change their names will not lose claim blocks or access to their land claims. If there's a problem, I need to know whether you're online/offline/bungee, whether in database or flat file mode, I need your boot logs from the conversion attempt, and if possible, a snapshot of your data from before the update.
- Disabled worlds in config - Version 8.5 and higher. If a world is "disabled" for land claims, then no land claims which already exist in that world (including administrative land claims) will be protected. For those upgrading from an earlier version ONLY, to ensure all existing land claims are protected, GP has defaulted worlds which were disabled to allow claims again, including player-made land claims. If this isn't what you want, update your config.yml.
- Piston limiting - Version 8.1.7 and higher. Pistons won't move blocks outside of land claims. This is a huge performance win, but if you want the old rules back, there's a new config option to disable this rule. Yes, players do get an explanation/warning when they place pistons outside of land claims, to avoid confusion for newly-placed pistons.
- /DeathBlow Removed - Version 9.3 and higher. It's no longer necessary, since the items players drop on death are now protected. This protection is on by default in non-PvP worlds, and off by default in PvP worlds. You may customize it in the config file. You can still use /kill to kill a player, although /kill will not send the player's inventory to another player as /deathblow did.
All Recent Changes
- Fixed players trampling crops (broke it last version, my mistake!).
- Performance boost for player interact event.
- Fixed claims expiring too fast on new creative mode servers.
- Fixed data migration rolling back claim blocks for some players with uppercase letters in their names.
- Fixed a minor protection bug stemming from a Vanilla bug.
- Fixed "someone" instead of player name for players in their first session on your server.
- Fixed an admin chat message having an unclickable link in creative mode worlds.
- Fixed a database migration bug.
- Fixed a UUID migration bug.
- When creatures tramping crops is allowed, player-controlled mounts will no longer damage crops.
- When players log in, they have to move at least one block before they can chat (this is an anti-botting strategy). Players who've earned the trivial "got wood" achievement on your server are exempt from this rule.
- Attacking a villager in a land claim now requires build trust, since villagers are potentially a major investment. Interaction (right click) is still container level trust.
- Because item frames and armor stands are decorative, they're part of your build's aesthetic and now require build trust to destroy. Interaction (right click) is still container level trust.
- Fixed visualizations showing at most one subclaim. Now they show them all again.
- No more log spam about grass. This was a debug message related to sheep eating grass that I accidentally left in. :\
- Added a 10-minute cooldown period for being warned about building outside of your land claims.
- Greatly improved the performance of the "claim block delivery" task.
- Interacting/trading with a villager now requires container trust (same as animals other inventory).
- Inverting a daylight sensor (right click) now requires build permission.
- /rnf now works better in grassy areas.
- No more sign notifications for signs which contain only spaces.
- Negative effect potions (weakness, poison, hunger, etc) now follow PvP immunity rules - they will not effect players in a no-PvP area except for the thrower, and will not effect ANY players if thrown from a no-PvP area.
- The PvP rules worlds part of the config file has been RESET and redesigned. If you customized that part of the config file, you'll have to do it again using the new settings (sorry!). The new design is MUCH easier to understand and edit.
- Added a config option to disable the WorldGuard compatibility feature.
- API changes (for developers)
- * Added datastore.getClaim(id).
- * Added datastore.getClaims().
- * Added ClaimDeletedEvent.
- Admin claim visualization style updated to ask clients to do less lighting updates.
- Nearby claim search now tells you how many claims were found.
- When resizing a players' claim, his remaining claim block allowance is now shown instead of yours.
- Fixed log spam when players walk into portals that don't go anywhere (e.g. end portals when the end world is disabled).
- Made UUID migration more reliable.
- The world guard compatibility feature to require WG build permission before a GP land claim can overlap a WG region is back with much better performance.
- Claimed vehicles (e.g. minecarts) will now take environmental damage like lava, fire, and cactus. TNT and Creepers still won't damage them because griefers could potentially be in control if those damage sources.
- Added some command aliases to make commands easier for players to remember and/or guess.
- The "no lava buckets near players" rule now ignores creative mode players, and won't give away the nearby player's name (in case of invisibility).
- Tweaked the IP address spam filter to be less aggressive.
- Fixed the "claim blocks are scattered along the horizon" bug. Side effects: some CPU time savings and visualizations only make marks within 100 blocks of the player receiving the visualization.
- Now wholly preventing nether portals from being created without a claim owner's permission, instead of redirecting them to an unclaimed area.
- Improved performance for nether portal related code.
- Probably fixed the rare but persistent "some of my players suddenly have negative claim blocks" problem.
- Temporarily disabled new world guard compat feature until the WG staff/community can help me find a more efficient implementation.
- Now preventing nether portal traps (found a workaround for the spigot bug blocking this feature).
- Now preventing players from creating nether portals in a land claim by building a nether portal in another dimension and walking through it (those portals are now redirected so that they're built where the player does have permission).
- Creating a land claim which overlaps a world guard region now requires the claim creator to have build permission in the world guard region.
- Fix: Teleporting into a land claim using an ender pearl now requires access trust (you can disable this in the config file).
- Fixed /acb [permission.node] not working for database mode servers.
- Sand/gravel cannons won't place blocks in land claims anymore.
- Fixed overly sensitive similar message filter and CAPS filter.
- Fluids may now flow into subdivisions from the parent claim, but not vice-versa.
- Fixed nether portal traps (needs a Spigot bug fix to start working).
- Added a config option to limit total land claims per player.
- Improved readability of /ClaimsList output.
- Fixed claim visualizations missing some visualization blocks.
- Made new player help harder to miss and easier to understand.
- Made an effort to educate players about claim subdivision when they make very large claims.
- Added /GPBlockInfo to help modded server owners edit the config file correctly.
- Players may now give away pets with /GivePet.
- Pets are now protected from many build-based attacks, for example flint/steel, lava buckets, and sand/gravel (suffocation), keeping them safe when you take them with you outside your land claims.
- Admins may now damage other players' pets using /IgnoreClaims, and can use /IgnoreClaims to transfer another player's pet with /GivePet.
- Added pet protections.
- * The original tamer of a pet has access to that pet at all times, even in another player's land claim.
- * Only the original tamer of a pet may interact with or damage it, even when it's in another player's land claim.
- * Protections are on by default in non-pvp worlds and off by default in the rest. You can customize this in the config file.
- * "Wild" untamed pet ownership is determined by the land claim the pet is in, if any.
- * I plan to allow for administrative overrides (/ignoreClaims) with pets, and to allow players to give away their pets in the near future. If players have "traded" pets, your best option for resolving it in the short term is either turning off pet protections for now, or killing the pet and spawning a new one in its place (so it can be retamed). I also plan to protect pets from damage by simple build, for example fire and lava.
- Fixed overzealous item protections preventing players from picking up items that shouldn't have been protected.
- Fixed unwanted log entries related to sending messages about commands used in console mode (like /acb from the console).
- Fixed armor stand protection again (the Spigot team broke it).
- Fixed log entries related to chat slash command usage.
- Water will no longer flow from top level claim into a subdivision, or vice-versa.